Ext3 corruption on a drive

Hello, I have recently upgraded from dapper to edgy and currently experiencing severe problems with one of my drives. I am using the 32-bit ubuntu version. This is my current setup:

Motherboard: ASUS K8V-SE Deluxe
CPU: 3200+ Athlon64 s754 newcastle
Ram: 1GB
HDDs: 320gb SATA /dev/sda, 80gb PATA /dev/hda, 200gb PATA /dev/hdb

My /etc/mtab:
/dev/sda3 / reiserfs rw,notail 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
/sys /sys sysfs rw,noexec,nosuid,nodev 0 0
varrun /var/run tmpfs rw,noexec,nosuid,nodev,mode=0755 0 0
varlock /var/lock tmpfs rw,noexec,nosuid,nodev,mode=1777 0 0
procbususb /proc/bus/usb usbfs rw 0 0
udev /dev tmpfs rw,mode=0755 0 0
devshm /dev/shm tmpfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
lrm /lib/modules/2.6.17-10-386/volatile tmpfs rw 0 0
/dev/sda5 /home ext3 rw 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
/dev/hdb1 /media/hdb1 ext3 rw 0 0

My /etc/fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda3 -- converted during upgrade to edgy
UUID=561dcfca-dca7-48e6-bd5a-489e143c770f / reiserfs notail 0 1
# /dev/sda5 -- converted during upgrade to edgy
UUID=764d80be-9f65-44cb-9e61-edf1abee9832 /home ext3 defaults 0 2
# /dev/hdb1 -- converted during upgrade to edgy
/dev/hdb1 /media/hdb1 ext3 defaults 0 2
# /dev/sda2 -- converted during upgrade to edgy
UUID=7d544689-ac59-4436-bbea-32a3f3286f1b none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/hdd /media/cdrom1 udf,iso9660 user,noauto 0 0
#/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

/dev/hda is windows and I am currently not mounting it with ubuntu
I modified the UUID for /media/hdb1 to /dev/hdb because when mounting it couldn't find the drive half the time. (Sorry but I foolishly took it out instead of just commenting out the UUID string, not sure how to get it back now).

Now the problem I am having is /dev/hdb1 is currently having errors here and there. Some days I can boot up and it would mount fine. Sometimes it would only mount as read-only, and other days it would display my filesystem all over the place in an inconsistent manner. When fsck.ext3 is run, it keeps picking up inode errors all the time, and I don't know why. The superblock is also getting corrupted on a regular basis and I am using block 32768 all the time to fsck.ext3 the drive. I used some SMART tools to check if the drive is dying but it seems to be all fine.

Sorry if udev is the wrong package to post this, it's either udev, ext3 or something else. Maybe teardown is not unmounting it properly? It's odd how it only seems to affect one drive. Once the drive is clean and it mounts, it works perfectly until the next time it happens when I boot up. Dapper handled the drive fine, so I doubt the hard drive is at fault.