> Recently SuSE decided not to boot into full run level 5 for me. It would
> boot into single user mode only. I was able to get it booted again by
> running Knoppix and doing a fsck --rebuild-tree on the / partition.
>
> In single user mode, I could find NOTHING in the logs to determine which
> repair route to take. I had no idea where it was hanging up.
> I was flying blind.
>
> How does other list members proceed in diagnosing a linux system that
> refuses to boot??
If you have access to the RPM tools you can run a verify against the RPM database:
rpm -Va
This will tell you if any files have been trashed or corrupted.
It's also a good idea to check the lost+found directories on all your partitions. If
any files are in there it means something is missing in your filesystem.
Often systems will drop into single user when it can't find filesystems to mount so
running fsck is a good first step. You may also want to check the kernel log.
Depending on how your logging is set up it may be actually going to a log so try
checking the other consoles to see if anything is put on screen.
-- * The Digital Hermit http://www.digitalhermit.com * Unix and Linux Solutions kwan@digitalhermit.com ----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:09:17 EDT