Drive mount problems after gutsy upgrade

[lryer]

Upgrading an older (intel PIII) system. There have been several starts and stops and freeze-ups, but finally rebooted with new splash screens, but adept-updater says there are still 817 packages to upgrade. The immediate problem is that drives that look OK in fstab do not mount.

Here's my /etc/fstab:

# /etc/fstab: static file system information.
#
# <file system> <mount point>  <type> <options>    <dump> <pass>
proc      /proc      proc  defaults    0    0
# /dev/hda1 -- converted during upgrade to edgy
UUID=31d8656f-b367-40a5-a5d0-ce01dfbbd56f / ext3 defaults,errors=remount-ro 0 1
# /dev/hda5 -- converted during upgrade to edgy
UUID=c97f51cb-80ac-40d9-b6e1-ec3119ed6092 none swap sw 0 0
/dev/cdrom    /media/cdrom0  udf,iso9660 user,noauto   0    0
# /dev/hdb1 -- converted during upgrade to edgy
UUID=a7db18d1-bcd7-4a21-8f1b-7ed49c1e319d /home/lryer/download ext3 defaults,errors=remount-ro 0 1
# from ubuntu forum HowTo: NFS Server/Client
192.168.4.190:/home/lryer /hepzibah nfs rsize=8192,wsize=8192,timeo=14,intr

/dev/hda1 mounts fine (or the system wouldn't come up)
/dev/cdrom seems to work normally
but...
/dev/hdb1 (big hd that has all my media files) does not show up
and the remote nfs drive does not show (but it will mount manually)

anybody have a suggestion?

[juantovarm]

Re: Drive mount problems after gutsy upgrade

just a simple question, does /home/lryer/download exist? If it does exist, you could try changing your fstab to user, auto instead of defaults

[lryer]

Re: Drive mount problems after gutsy upgrade

The directory exist and the mount worked through edgy and feisty. I had finally completed all of a very bumpy upgrade that I had to frequently restart by running apt-get in a terminal. For the most part the only visible problem was the missing hard drive everything else seemed to be fine and pretty. I tried several things with fstab -- all the uuids were correct, and I got no farther mounting by label -- and was trying with no fstab when the machine started booting to a command line in a read-only state, preventing me from altering any files to attempt a fix.

At that point I tried to boot from a Kubuntu 7.10 cd I made just before starting the upgrade. I didn't manage to get it to boot from cd, but when I got into the bios only one hd was showing up. So... I'm thinking it's a hardware problem and have sidelined the machine, opened it and am checking the cables and connections.

First thing to do when I get it set up to work on it is try booting to an older kernal. One curious thing was that even when the drives didn't show up in the bios, they showed up in lsmod...

suggestions welcome.