possible HD errors, filecheck fails, what now 912

the following words to the mbuttes incomp.os.linux.misc...:

Sounds like a hardware problem then. The CMOS battery gone bad, perhaps?

Hmm... On the other hand, that would not cause the system to lock up. Perhaps there's something wrong with your hard disk or the controller it is connected to.

The system won't do a filesystem check by itself if it's really in runlevel 5. It does that while it's still in the boot process, normally.

False buttumption. What happened before is likely to happen again.

Of course not. It is quite possible and presumable that the check happened before any filesystems were mounted. As *-var* can be split off onto another parbreastion, such a check would normally not write to *-var,* because of the chance that *-var* isn't mounted yet when this check occurs.

Nowhere, I'm afraid.

Is that really important? Your BIOS didn't recognize your hard disk before you bootstrapped, and you wonder about a software cause for errors you receive?

Try "my hard disk (controller) is broken" or something similar for information...

You're missing the obvious. Your machine froze, and upon reboot your hard disk wasn't found. That should tell you something about your system before you begin scouting around for logfiles that don't even exist.

Hope this helps... ;-)

-- With kind regards,

*Aragorn* (Registered GNU-Linux user #223157)