For Want Of A Google Search, The Kingdom Was Lost

When I set out to write this post I promised myself that I would try to keep my cynicism and negativity to a minimum. But the solution to what I have experienced over the past week has nearly driven me mad…

Our tale begins when I decided to finally utilize some spare computer components I had laying around to build a better PC to use at work. After receiving some parts from newegg that were still needed, the build itself went rather smoothly. My trouble began when I attempted an OS install (with my distro of choice Ubuntu 9.10 “Karmic Koala”) for some strange reason the hard drive would not show up in the damn partitioner.

Admittedly I did not devote a ton of time trying to figure out what was going on. Since I was using one of my older drives I figured that most likely it was the drive was bad, but I also considered that the SATA cable or controller was. With that to start on, I went through every iteration of the possible issues I had so far; different drive, different cable and different controller. This got me no where other than frustrated and annoyed. My suspicions then led me to the Ubuntu disk itself; did the iso download become corrupted somehow, is my CD-ROM bad, could there be an issue stemming from the fact that I was installing Ubuntu 64-bit? After about a week of working a few free minutes here and there…I was still where I started, I even installed Ubuntu Server 64-bit to try to figure out the issue.

After all this work, I was forced to swallow my pride and resort to trolling google to try and find the solution. After a few bumbling tries at getting the right search string, I finally found my answer on ubuntuforums.org:

Usually this happens when you have raid meta data settings on the hdd. 9.10 can detect them and is confused whether the hdd is part of raid array or not.

First make sure you don’t have any raid settings enabled in bios, because they can put raid info on the hdd even when it’s only one hdd. The SATA Type option should not be RAID.

Of course, all of this if you are NOT running raid. If you are, that’s another story.

Then boot the ubuntu live desktop, and in terminal do:

sudo dmraid -E -r /dev/sda
sudo apt-get remove dmraid

(if you have one hdd, for more you might need to use /dev/sdb, /dev/sdc, etc)

Restart the install process and it should be fine. Provided that was the problem.

After following the instructions, of course everything worked fine and the rest of the install went without a further issue.

I really want to continue on a tirade about how ridiculous an issue this is, but I will refrain since I am growing bored of writing this post. I will just leave with one last note:

Usually this happens when you have raid metadata settings on the hdd.

That, as far as I am concerned, is bullshit. After TWO hard drives (and disabling the RAID function before the second one I think) that was still an issue?!

I guess at least I got it working before I threw the computer out the window…

%d bloggers like this: