mybike
Grumblin at Garmin on the Granny Gear
- Location
- Not 'emel 'empstead
I just had to use a fix I hoped to never have to use: emergency file system repair via bootup. For some reason, my Linux desktop PC found some filesystem corruption, and as a preventive measure it remounts the root filesystem (i.e. the one mounted on the '/' directory) as read-only.
So I had to
Once I'd done all that, after Linux was running again, everything seemed normal, so it seems to be all good again.
- reboot.
- hold down Shift key at the BIOS splash screen to show the grub menu.
- select Advanced.
- select Recovery mode.
- select "Drop to root shell".
- run the following to repair filesystem errors: fsck -A
- run the following to remount '/' as read-write: mount -o remount,rw /
- run the following to continue booting: reboot
Sorry, I omitted step 0: before doing ANY of the above, while Linux was still running with '/' mounted read-only, I backed up about 2GB of essential directories to an external disk, because backup ALWAYS comes before any corrective action, ALWAYS!
Anyway, just thought I'd post the above, in case any of you ever need to use it. Fortunately, having '/' mounted read-only isn't quite as bad as it seems, because it's the filesystem mounted on '/home' that contains most or all of your working files. So I was still able to read emails, run Firefox, etc. But I was getting odd errors when starting up Dolphin file manager, and running the 'sudo' command for any reason just didn't work properly.
Regards,
--- Victor (the ex-birthday 'boy').
Thanks, that looks really useful. Presumably the odd errors would be down to failure to log events.