possible HD errors, filecheck fails, what now 915

Aragorn ..

Ah, sorry. I jumped the gun. Yeah, it did the file check attempt at boot up before it got to the runlevel. My mistake.

Sorry, what I meant to say, is that it APPEARS to be running OK in that it's booting up, the services are starting, it's not throwing errors that I can see. I didn't mean to imply all was well, just that it got further into running the machine than stopping at either the POST or the pre-runlevel bootup. =)

Well, that makes perfect sense! I hadn't thought about that.

Well, it SEEMS important, but maybe not. I was kind of hoping it'd be somewhere in the log something like "Attempted to write todev-hda but it seems to no longer be visible to the system. It's the fault of the controller card and not me, so don't look at me like that. Replace the ribbon cable and all will be well, thank you. Attemped log in by root denied...."

You know, something like that. *grin*

..

Yeah, I agree. I wasn't really going through the proper logical steps of troubleshooting ("Is it plugged in?") I've been using Linux for about 5 years now, but I'm still a newbie beginner, really. So my first fear whenever something goes wrong is it has something to do with the hermetic arcane magic which Linux is built upon that is way beyond my meager ability to comprehend. In a way it's actually a relief to think abot that it's a hardware issue and not something in Linux that's a problem. But I was kind of hoping that something unbeknownst to me in Linux was able to kind of tell me helpful hardware information.

Based on another poster, I'm looking into tripwire to see if that can help me overcome possible data corruption, or at least detect it in the future.

Thanks for the reply and the advice! -Liam