This is a 'pull it outa my rear' idea, but it is based in some common sense.
Many externally connected devices through USB and Firewire default (in Windoze -- and so far my Digital Camera has done the same under Fedora Core 5 Linux) in read-only mode.
So fstab ........... 'defaults' may be causing it to mount as read only.
'rw,suid,dev,exec,auto,nouser,async' is equivelant to a normal 'defaults'
'rw,suid,dev,exec,auto,user,async' will be what we will try instead
But I digress, try this in fstab...
/dev/sda5 /mnt/usb80hd ext2 rw,suid,dev,exec,auto,user,async 0 0
I also have no love for priortizing secondary drives with 0 0...
/dev/sda5 /mnt/usb80dh ext2 rw,suid,dev,exec,auto,user,async 2 1
If that doesn't work, then you may want to investigate whether you can successfully mount a device-drive itself, as opposed to a partition on that drive.
For example, /dev/hda is an PATA EIDE hard drive on one of my machines. (no, its not the boot drive, that's /dev/hde -- don't ask
) I have been unable (on that machine) to mount /dev/hda. However, once I partition /dev/hda into one or more paritions -- say /dev/hda1 /dev/hda2 and /dev/hda3 -- then I am able to mount all of them individually with simple commands like...
/dev/hda1 /mnt/my_drive_1 xfs defaults 2 1
/dev/hda2 /mnt/my_drive_2 xfs defaults 2 1
/dev/hda3 /mnt/my_drive_3 xfs defaults 2 1
... where xfs replaces ext2 -- as I use the xfs file system on most of my stuff.
The only exception to this "no-likey-mounting-actual-device-drives" deal is when I mount Linux-generated software-raid drives.
Then I am able to do something like...
/dev/md0 /mnt/raid_drive_1 xfs defaults 2 1
/dev/md0 /mnt/raid_drive_2 xfs defaults 2 1
... but only after I have used:
# mkfs.xfs /dev/md0
# mkfs.xfs /dev/md1
to format the drives manually to the xfs file system... similar can be done with ext2 as well as every other file system.
With raid drives I choose not to create a partition on them, and simply manually format the whole device.
Why? I honestly don't know. For all I know, I could be doing something horribly wrong, but it seems to work.
That is neither here nor there though.
I would suggest the previous /etc/fstab modifications, and then let me know what happens.