Failed to load DietPi-Globals

Troubleshooting
21 
e2fsck: 
root@DietPi:~# e2fsck -f /dev/mmcblk0p2
e2fsck 1.44.5 (15-Dec-2018)
e2fsck: No such file or directory while trying to open /dev/mmcblk0p2
Possibly non-existent device?




root@DietPi:~# mount -o remount, rw /
root@DietPi:~#

That runs without error, there’s no output and it just goes to the next prompt

22

do you use SD card or was RootFS transferred to an USB device?

23

Looks like a USB drive when /dev/mmcblk0p2 does not exist. Okay when remounting in R/W mode worked, then you should be able to force fsck on reboot now. I mean strangely it was already present before, but let’s retry:

findmnt -no SOURCE / # just to verify SD card vs USB drive
> /forcefsck
reboot
journalctl -t systemd-fsck
24 
root@DietPi:~# findmnt -no SOURCE
/dev/sda2
devtmpfs
tmpfs
devpts
mqueue
sysfs
securityfs
tmpfs
cgroup2
cgroup
cgroup
cgroup
cgroup
cgroup
cgroup
cgroup
cgroup
cgroup
none
debugfs
configfs
proc
systemd-1
tmpfs
tmpfs




root@DietPi:~# > /forcefsck
-bash: /forcefsck: Read-only file system
25

Please do the remount first again:

mount -o remount,rw /
> /forcefsck
reboot
journalctl -t systemd-fsck

If that does not work, you need to plug that drive into a different Linux system to run fsck from.

26

Didn’t work, I’ll try another system

27

Ok, I plugged the drive into an RPi2 running dietpi. Used dietpi-drive_manager, chose to scan and fix- it found and corrected some errors. Moved it back, but nothing’s changed. What’s next- do I have to run fsck?

28

Did you run fsck multiple times? Sometimes is needs more than one loop to fix everything. But probably it’s better to format the file system or the whole drive freshly, when if keeps causing issues like that. I.e. you could copy all content outside, re-create the partition table and partitions from scratch and copy content back in. Let me know if this is an option and I’ll instruct you. As two partitions are required, it cannot be done with dietpi-drive_manager.