If you remember, I mentioned a hard drive replacement a while ago. I haven’t tried to revive it yet with a tool like Spinright yet, but I may still be able to get something out of it. That was a hard drive failure. It doesn’t boot or recognize at all at the moment.
I thought that I was going through that with another one as well. The hard drive in Frankenputer seemed to have gone on me after another update of Hardy Heron. I had split the drive up into three partitions, one as the root partition “/”, swap, and a third one as “/home”. The root partition was formatted as EXT3 and the /home was partitioned as ReiserFS. After yet another update (development software after all), I rebooted into a corrupted first partition and E2FSCK didn’t help, dropping me to a single user recovery shell. I ran FSCK manually and was able to get the partition reorganized. I carried on but this was not the end of my troubles.
One more update killed it for good, I thought. My drive was not even recognized on boot. Its the second hard drive and I actually have GRUB, my bootloader on the first drive. I’ve been letting whichever operating system that does the latest update handle GRUB, which meant that the config file with the instructions for GRUB “/boot/grub/menu.list”, was on the second drive on the corrupted partition. no problem, I just popped in a Linux install CD (Ubuntu of some version, I recall), and chose the option to boot from the first hard drive to get into Arch Linux o that I could do some online digging about this problem.
Somehow, the corruption of the first partition seemed to have affected the boot sector of the second drive as well, which was causing the problem with the BIOS picking up the drive. I was able to “see” and mount the “/home” partition, so I figured that the drive just couldn’t be dead, as I had thought. I immediately attempted to back up as much data as I could access onto DVD, which was quite successful, albeit a tad slow, as the OS and the DVD burner were on the same IDE cable. On a lark, I reformatted the first partition with ReiserFS, which in my opinion, has a far superior recovery on unexpected shutdown. Suddenly, the whole drive was once again visible to the BIOS.
I reinstalled Gutsy Gibbon and used my existing “/home” and restored my user and each of the kids. The only difference was that a few programs were missing, which can be recovered, and some theme-related files which were in “/usr/share” were not available.
So, the take away from this story is that your hard drive may not actually be bad. It might just be that your hardware is not perfectly suited to go together and a file system corruption may be the cause of your troubles.
That made my head hurt. LOL
I understand what you mean, DL. I feel the same way every time anyone gets into DB talk
(but I still try to understand it, usually unsuccessfully)
Been there, done that and boy does it ever hurt!
Yikes!
It reminds me of my hdd that died on me end of last year. It happened all of the sudden, boot up the machine and I was brought to the grub prompt. I just had Ubuntu on my system, so I find it weird for grub to have such issues. Anyways, I did what I think am supposed to do, and reboot again, and still failed. After a while my hdd produced something like a ‘clunking’ sound and at that point I could feel that am already sweating. Checked on bios and it seemed that the hdd was not recognized anymore. I set the hdd as slave and plugged it on another machine, hoping that I could access it. Nope, didn’t work. LiveCD didn’t work too. After putting so much effort on it, I thought I ought to take a break. The hdd is still under warranty, but for the love of all my data inside, I still keep it and will try to check on it again. Sorry for the rant, but I still can’t get over it. It hurts so bad
Just as a thought, whenever you think a hard drive may be going, run a SMART scan on it. Do a search for it, you’ll find programs for all sorts of operating systems. I usually just use the SMART tab of SpeedFan. It’ll usually accurately catch a dying hard drive.
I’ve enabled S.M.A.R.T. on my drives now in the BIOS. I hadn’t before, but this incident caused me to think. The drive is fine, though. It was a filesystem problem, rather than a hardware issue. I still have the other drive that has failed for sure, though. Thanks for the tip, Brandon, as others might need it too.