Hello everyone. I'm new to the Pi world, I picked up my first Raspberry Pi 4B 8GB about 2 weeks ago. I purchased this kit https://www.amazon.com/GeeekPi-Raspberr ... B09LYP7QH3
I initially purchased it to run pi-hole. It ran well for a couple of days but randomly one day when I tried to access the pi-hole UI I was greeted with a 500 Internal Server Error. I attempted to SSH and would get connection refused by peer. I decided to plug in the Pi via HDMI to a monitor and saw these errors going down the screen.
I'm not sure what to do next. Below are my notes, screenshots and code outputs
Steps I have taken to remediate to no avail![Image]()
I initially purchased it to run pi-hole. It ran well for a couple of days but randomly one day when I tried to access the pi-hole UI I was greeted with a 500 Internal Server Error. I attempted to SSH and would get connection refused by peer. I decided to plug in the Pi via HDMI to a monitor and saw these errors going down the screen.
I'm not sure what to do next. Below are my notes, screenshots and code outputs
Steps I have taken to remediate to no avail
- Purchased a new SD Card - SanDisk Extreme Pro SDXC UHS-I U3 A2 V30 128GB
- Purchased a new power supply - CanaKit 3.5A Raspberry Pi 4 Power Supply with PiSwitch (USB-C)
- Formatted the SD Card using Raspberry Pi Imager with Raspberry Pi OS Lite (64-bit) on a Windows 10 pc
- SDCard is inserted into the Pi's on-board slot
- I only see a red light on the Raspberry PI, no green light. The red light is stable, no blinking.
Code:
EXT4-fs error (device mmcblk0p2): ext4_journal_check_start:83: comm systemd-journal: Detected aborted journaleEXT4-fs (mmcblk0p2): Remounting filesystem read-onlyEXT4-fs error (device mmcblk0p2): __ext4_find_entry_1682: inode #17042: comm service: reading directory lblock 0EXT4-fs error (device mmcblk0p2): __ext4_get_inode_loc_noinmem:4617: inode #1010: block 227: comm service: unable to read itable blockEXT4-fs error (device mmcblk0p2): __ext4_find_entry_1682: inode #17042: comm service: reading directory lblock 0EXT4-fs error (device mmcblk0p2): __ext4_find_entry_1682: inode #33: comm gmain: reading directory lblockEXT4-fs error (device mmcblk0p2): __ext4_find_entry_1682: inode #86: comm gmain: reading directory lblockEXT4-fs error (device mmcblk0p2): __ext4_find_entry_1682: inode #22: comm gmain: reading directory lblock 0EXT4-fs error (device mmcblk0p2): __ext4_find_entry_1682: inode #17472: comm service: reading directory lblock 0Code:
robsteriam@rp4:~ $ journalctl -p 3-- Boot 3bd3ed65ed624f499643740f228cfa21 --Mar 04 11:30:56 rp4 bluetoothd[700]: src/plugin.c:plugin_init() Failed to init vcp pluginMar 04 11:30:56 rp4 bluetoothd[700]: src/plugin.c:plugin_init() Failed to init mcp pluginMar 04 11:30:56 rp4 bluetoothd[700]: src/plugin.c:plugin_init() Failed to init bap pluginMar 04 11:30:56 rp4 bluetoothd[700]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.Mar 04 11:30:56 rp4 bluetoothd[700]: sap-server: Operation not permitted (1)Mar 04 11:30:56 rp4 bluetoothd[700]: Failed to set privacy: Rejected (0x0b)Mar 04 11:31:00 rp4 bluetoothd[700]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_mana>Code:
robsteriam@rp4:~ $ sudo journalctl -p 3 -x -b -0Mar 04 15:23:54 rp4 bluetoothd[666]: src/plugin.c:plugin_init() Failed to init vcp pluginMar 04 15:23:54 rp4 bluetoothd[666]: src/plugin.c:plugin_init() Failed to init mcp pluginMar 04 15:23:54 rp4 bluetoothd[666]: src/plugin.c:plugin_init() Failed to init bap pluginMar 04 15:23:54 rp4 bluetoothd[666]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.Mar 04 15:23:54 rp4 bluetoothd[666]: sap-server: Operation not permitted (1)Mar 04 15:23:54 rp4 bluetoothd[666]: Failed to set privacy: Rejected (0x0b)Mar 04 15:23:59 rp4 bluetoothd[666]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power downCode:
robsteriam@rp4:~ $ sudo fsck.ext4 -n /dev/mmcblk0p2e2fsck 1.47.0 (5-Feb-2023)Warning! /dev/mmcblk0p2 is mounted.Warning: skipping journal recovery because doing a read-only filesystem check.rootfs: clean, 79795/7500896 files, 998206/31085056 blocksrobsteriam@rp4:~ $ sudo fsck /dev/mmcblk0p2fsck from util-linux 2.38.1e2fsck 1.47.0 (5-Feb-2023)/dev/mmcblk0p2 is mounted.e2fsck: Cannot continue, aborting.Code:
robsteriam@rp4:~ $ vcgencmd get_throttledthrottled=0x0Statistics: Posted by robsteriam — Tue Mar 05, 2024 8:39 pm