I have a small webserver running LM 8.2, latest updates, kernel
2.4.18-8.1mdk. Recently it crashed, and when I brought it home I
noticed fsck gave me a "unconnected directory inode" on the / partition.
I ended up having to run fsck several times to fix a series of inodes
like this (about 10) manually. The machine came up fine every time, the
files the inodes pointed to all seemed fine, only one of which was a
system file, in this case the kernel module pnpbiosmap. Running fsck
-c doesn't find any bad blocks; the hard drive is fairly new, it's not
overheading, I can't find any bad files, and file I/O seems fine. Is
this an error that I should take as a sign of immanent hard-drive
failure, or as an isolated glitch?
When I first opened up the box, the CPU cooling fan seemed a little
noisy, so I replaced it; is it possible the CPU overheated and caused
the crash and subsequent inode errors?
Any advice is most welcome.
Dan
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
