Comment 9 for bug 66032

I recently updated a Dapper installation to Edgy using the recommended "gksu update-manager -c" procedure. On booting into Edgy, it failed to the "enter root password to repair" prompt, obviously a bad message for Ubuntu to show a newbie since root isn't supposed to have a password. Above that the error message was that fsck.ext3 could not resolve a UUID. This computer had 3 old IDE fixed disks as /dev/hd{a,b,d} and a CD-RW drive as /dev/hdc. I entered the root password (I'm old fashioned in some ways) and saw in /etc/fstab that the unresolved UUID was supposed to refer to /dev/hdd1. I also saw that there was an /etc/fstab.pre-uuid file that looked like it would work, so I renamed /etc/fstab to fstab.bad, copied fstab.pre-uuid to fstab, and rebooted, successfully this time.

It looks like this is only one of several ways that Ubuntu can become confused when it tries to use UUIDs in the fstab. Maybe a little more testing and debugging should have been done before dropping this change on unsuspecting users.