[Bug 46189] Re: Dapper failed to mount disks after upgrade

[anonym]

I have the same problem. My fstab looks like this:

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/hda5       /               ext3    defaults,errors=remount-ro 0       1
/dev/hda7       /home           ext3    defaults        0       2
/dev/hda1       /media/win_c    vfat    defaults,utf8,umask=007,gid=46 0       1
/dev/hda2       /media/win_d    vfat    defaults,utf8,umask=007,gid=46 0       1
/dev/hda6       none            swap    sw              0       0
/dev/hdc        /media/cdrom0   udf,iso9660 user,noauto     0       0

I have always had hda5 and hda7. I boot to Windows and back to Dapper,
and it says at startup those same errors as above. I boot back to
Windows and check with explore2fs are these partitions ok. They are, but
now they are named hda3 and hda5. Pretty interesting how their names
could change without touching hardware or anything. And now I have to
find out how to fix it. :(

-- 
Dapper failed to mount disks after upgrade
https://launchpad.net/bugs/46189