How can I figure-out the actual cause of the kernel panic that's preventing a successful boot -- I'm hoping it's something I can fix, but concerned I may really need to buy a new hard-drive.
I'm running Debian Etch /Stable
According to dmesg :Linux version 2.6.18-5-686 (Debian 2.6.18.dfsg.1-13etch4) (dannf@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21))
Lately this box has sometimes had trouble booting, and might just freeze up, even while not in active use. At least once it seemed to turn itself off. I first really noticed this after a recent power-fluctuation about a week or two ago. (Attempts to CTRL-ALT-Fx did not succeed, so brute-force power-off was required.
Sometimes restarting would take two or three tries, and I think I saw messages about initrd or initrd-img or something like that flash by, but the automatic fsck and ext3 seemed to deal with this -- so I put it down to "bad" shutdowns.
After the last lock-up though, I have had to resort to Knoppix. Before booting into Knoppix though, I hand-copied this from the monitor.
Code:
Begin: Mounting root file system ... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Running /scripts/local/premount ...
kinit: name_to_dev (dev/hdb2) = hdb2(3,66)
kinit: trying to resume from /dev/hdb2
Attempting manual resume
kinit: no resume image, doing normal boot...
Done.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Done.
/bin/init: error while loading shared libraries: /lib/tls/i686/cmov/libc.so.6:
cannot read file data: Invalid argument
Kernel panic - not syncing: Attempted to kill init!
Trying to follow up on this, I have no idea why it would look for a "resume image" -- this is not a lap-top. Trying to verify in /etc/fstab my recollection that hdb2 is my swap partition, I discovered that my /etc file has apparently been replaced with a supposed (broken) link to 'librt-2.3.6.so'.
I am suspecting that my hard drive was damaged in the power fluctuation that I mentioned, which was sharp and brief enough that it shutdown my computer though nothing else was greatly affected. Previous incidents either rebooted (rather than shutdown) the computer, or also reset VCR's, clocks, etc.
But as I may be jumping to conclusions, I thought I'd seek informed
opinions and advice on what I can/should try or do about figuring this out.