Another Opinion Among Many

I got a motherboard and processor from my brother that would be a great upgrade to my old P-III. I quickly secured a cheap stick of RAM and hooked everything up. The problem is that I couldn’t seem to get anything to install on the drives. It was always coming up with errors, causing a total failure. So, I bought a replacement motherboard, thinking that I might be having problems with the IDE connectors. I really wanted to use the board my bro gave me, though, as it had better capabilities.

I had the same issues with the new board, although the operating systems that were currently on the hard drives in the machine recognized the board and booted. I still received compression errors and files weren’t saving properly. Even after installing brand new IDE cables (the pretty round ones that glow under UV light), I still had these issues.

Programs that are memory intensive, like Firefox (yes, it is, all you naysayers - its the browser that I use, and likely a lot longer than you have, but its still got leaks), would crash for no apparent reason. Many games would just refuse to load. I began to suspect something else (which I should have checked before spending money).

It turns out that the cheap used memory module was priced so low for a reason. Its crap (to quote Fab from Linux Outlaws). A quick memory test with memtest86 indicated that there were errors on 5 of the tests in the thousands. Its a guarantee that I will have better luck with a good memory stick.

So, remember, if you’re getting I/O errors, check your memory first, as its pretty much the cheapest fix, and a likely suspect.

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.

Awesome! I just got my e-flyer from Dell today and I saw a new offering on the ad.  They’re now bringing the Ubuntu operating system to Canada on some of their models! This is great news, as I have been contemplating a laptop purchase and it was going to have Linux on it.  Now, since I like Ubuntu anyways, I won’t have to install it myself.  And all of the machine’s capabilities will be used under Linux, supported by Dell.  Woo hoo!

Check it out:  HERE

Its been reported here and here as well.

This is so good!