kb6673
(kb6673)
1
After some recent messing around with some new hardware, I think I’ve managed to corrupt the emonPi filesystem.
I’ve tried entering into a recovery mode however I’ve been unsuccessful. Is there a way I can get into a recovery mode? Shorting some jumpers? Bashing the Shift key whilst standing on one leg?
EXT4-fs error (device mmcbIk0p2): ext_lookup: 1705: inode #2: comm swapper/0: deleted inode referenced: 48290
Vster
(Lee)
2
I’ve never done it on a Pi but the standard Linux force off-line fsck is -
sudo touch /forcefsck
sudo reboot
Give that a try?
kb6673
(kb6673)
3
Yep, trying that… However I can’t get into rescue/emergency/single user mode
Vster
(Lee)
4
Why? What happens at the end of the boot screen?