[SOLVED] Added 2nd Hard Drive, Killed my Ubuntu

[FreedomFries]

So I tried adding a new, 2nd hard drive to my Ubuntu 9.04 desktop for some additional storage and only managed to kill my system so that it won't boot up anymore (I just get a blinking cursor after the BIOS does its thing).

I could sure use a little help getting back to a functioning system, and then adding the second drive. I tried following the instructions from this link to add the 2nd drive:

(So the forum rules won't let me post the link, neato. Here it is with spaces added):
h t t p s : / / h e l p . u b u n t u . c o m / c o m m u n i t y / I n s t a l l i n g A N e w H a r d D r i v e

Here is what I did:

1) used Gnome partition editor to format (as ext4, maybe a mistake not to use ext3?) as a single primary partition of the full 500 gb drive (same size as my main drive). My main (#1) drive is ext3 I think.

2) sudo mkdir /media/hd2

3) gksu gedit /etc/fstab
to add this to the end of fstab:
/dev/sdb1 /media/hd2 ext4 defaults 0 2
4) entered the following 3 commands so it would mount and be usable automatically:
sudo chgrp plugdev /media/hd2
sudo chmod g+w /media/hd2
sudo chmod +t /media/hd2

5) verified new drive was available to me and that I could read and write from it, created a new folder on it, etc.

6) rebooted

7) got blank screen with blinking cursor after bios, and that is as far as it will go

booted using ubuntu live cd, mounted main drive and played around with fstab trying a couple things to get it to boot again with no luck. Here are the things I tried:
a) change the new line in my fstab to
/dev/shd2 /media/hd2 ext4 defaults 0 0
b) remove the new line in fstab, again no luck with reboot

9) So, here I sit with an inoperative Ubuntu system, and I am kindly asking help to get it to boot again. I'm guessing those three lines I executed in Step 4 above modified something that needs to be switched back, but I have no idea what.

10) Here is the current fstab contents. I've removed the line at the end that I added in step 3, and blanked out the actual UUID:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=00XX0000-0X00-000X-00XX-0XX000X00XX / ext3 relatime,errors=remount-ro 0 1
# /dev/sda5
UUID=ZZZZZZZZ-0X00-000X-00XX-0XX000X00XX none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

[FreedomFries]

Okay, a little help from another forum pointed me to the fact that my BIOS had placed the new hard drive in a higher boot order. So, not a linux problem but a dumb operator problem instead.