Comment 13 for bug 106209

The bug: Gutsy Tribe 5 Just hit this "fsck.ext3 unable to resolve UUID= 4a60babf.......
"fsck.ext3 unable to resolve UUID = 15251c65 ....
then boot stops.

This is a triple boot system.
Installed Gutsy Tribe 5 Ubuntu on sda1. Was Ubuntu Tribe 1.
Then Installed Gutsy Tribe 5 Kubuntu on sda5. Was Kubuntu Tribe 1.
Kubuntu's fstab shows sda5 UUID now e804340d... not 15251c65...
Then Installed Gutsy Tribe 5 Xubuntu on sda3. Was Xubuntu Tribe 2.
Xubuntu's fstab shows sda3 UUID now b66fd82.... not 4a60babf.....

Now, booting Ubuntu sda1, boot stops because the UUID's in Ubuntu's /etc/fstab do not match what Kubuntu and Xubuntu installs did to the UUID's.

The screen said to do Control D. That didn't work.
Just guessing I typed in:
exit
and boot continues.
My fix was to do sudo gedit /etc/fstab and comment out the offending UUID's.

Could it be that the programmer(s) that wrote the UUID code to keep changing the UUID's did not provide for installing more than one Ubuntu Linux on a system, and did not provide for installing later releases fixing up previous releases fstab when UUID was changed?

A year ago I didn't have this problem since fstab used hda1, hda3, hda5.

Thanks, Jerry Amos