Crash recovery.
Hi Everyone,
Had a fun experience today. Debian hung and refused any input. The only option I had was to power it down. The reboot failed dropping me at the command prompt to run fsck manually. This fixed this and that and place a number of things in to /lost+found. Rebooting again and this time we get stuck starting syslogd. Recreating the dir /var/run got me past that but there are obviously still issues from the problem. What I need to know is a way to either work out what was crunched and placed in /lost+found, whether or not knowing this is good enough, and some way of checking the current status of the system to repair what is now broken.
Any input is appreciated.
--
-Paul de Kievit
Reply to: