Was the software title installed freshly or updated/migrated?
Can this issue be replicated on a fresh installation of DietPi?
← If you sent a “dietpi-bugreport”, please paste the ID here →
Bug report ID | echo $G_HW_UUID
0330f21b-1974-425a-a21f-e1e4107cf434
Steps to reproduce
Have DietPi before 8.20, it prompts to update to latest version so I do “dietpi -update”.
Once update happens to latest 8.21.1, although it says all processes are restarted but nothing actually is restarted.
Rebooting the RPi4 doesn’t help either. everything stays in sleeping and only dietpi dashboard is running. Even “htop” confirms this. Attaching screenshots too.
Expected behaviour
All processes should start like sonarr, radarr, jellyfin etc.
Actual behaviour
every process is sleeping, nothing starts even when manually done.
Don’t think so. I am trying to access the various services like sonarr, radarr, jellyfin etc but nothing opens at all.
Also htop says “1 running” which is what is true and dashboard confirms too.
I tried systemctl status for say “sonarr” and such it says active but after a reboot, i did “journalctl -r --system” and i am attaching that here too as i can it stopping services after starting them.
There are some other interesting messages in the journal, e.g.:
Sep 19 09:38:41 DietPi kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
Sep 19 09:38:33 DietPi kernel: I/O error, dev mmcblk0, sector 5503720 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 19 09:38:33 DietPi kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
Sep 19 09:38:27 DietPi kernel: hwmon hwmon1: Voltage normalised
Sep 19 09:38:24 DietPi kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
Sep 19 09:38:23 DietPi kernel: hwmon hwmon1: Undervoltage detected!
Sep 19 09:38:16 DietPi kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
Sep 19 09:38:13 DietPi kernel: hwmon hwmon1: Voltage normalised
Sep 19 09:38:09 DietPi kernel: hwmon hwmon1: Undervoltage detected!
Sep 19 09:38:07 DietPi kernel: I/O error, dev mmcblk0, sector 5503720 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 19 09:38:07 DietPi kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
Sep 19 09:37:58 DietPi kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
Sep 19 09:37:50 DietPi kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
Sep 19 09:37:46 DietPi kernel: hwmon hwmon1: Voltage normalised
Sep 19 09:37:42 DietPi kernel: hwmon hwmon1: Undervoltage detected!
Sep 19 09:37:42 DietPi kernel: I/O error, dev mmcblk0, sector 5503720 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Sep 19 09:37:42 DietPi kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
Sep 19 09:37:38 DietPi kernel: hwmon hwmon1: Voltage normalised
Sep 19 09:37:34 DietPi kernel: hwmon hwmon1: Undervoltage detected!
Sep 19 09:37:33 DietPi kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
You have some undervoltage messages (do you use an external USB drive or something like this?) and also I/O errors from your SD card. The card got probably corrupted due to power loss / undervoltage.
You can run a filesystem check with dietpi-drive_manager, but probably the card is dying and you need to replace it
Dietpi runs off a MicroSD card (since last 2 years) and additionally i have 2 more microsd cards connected so I will try to unmount those 2 and restart raspberry pi and see if it makes any difference.
I have never bothered to do the “journalctl” command as never faced this kind of issue so no clue if undervoltage is an old problem or new.
No external hdd connected at all.
Edit: But yes one thing i have noticed lately (even before this update) is that logging into dietpi was very slow and then running htop would also take take for it to show all stats. This does lead me to believe that the primary boot Microsd card is possibly dying.
I guess not the card is dying, but the regular undervoltage leads to those I/O errors and hence also possibly filesystem corruption.
That htop shows only 1 or 2 processes as “running” is btw normal. 1 is AFAIK itself the that more than 1 other process is using CPU time in just this very same moment is unlikely.
The “process” list of the DietPi-Dashboard does not equal the “service” list. The services are all active, but the main processes they host may be currently sleeping, which equals to not being “running” in htop. It uses the psutil crate to obtain process statuses, hence it should equal what you get from:
ps -o comm,state --ppid 2 -N
The second field shows the status, and “S” means it’s sleeping.
