Comment 33 for bug 106209

Colin, thanks for looking at this broken situation.

For whatever reason, when I install another Ubuntu into an existing triple boot system, swap UUID's have not been a problem to fsck. The new Ubuntu happily uses whatever swap(s) it can find.

Booting one of the existing partitons fails because the UUID's don't match since fsck insists on looking for a superceded UUID it doesn't need. My reaction is "What the ??" then fumble around to get the system booted, remember what the problem is, and then do some tedious editing and copying. If I've been doing a bunch of installs like in the later stages of Gutsy, I may remember to do the tedious editing and copying on the other partitions while the latest install is booted up. And again the next install a few days later.

It would be a whole lot less trouble for me if boot didn't automatically do that; if I happen to want to access the new partition when booted on the older, I can just sudo mkdir /media/x, then sudo mount /dev/hda1 (or sda1) /media/x. If I remember the syntax right.

No long winded UUID's required. I think I could explain this to a newbie easier than explaining how to edit UUID's in /etc/fstab and /boot/grub/menu.lst without screwing up these system files. Easist for me is gedit. Under Xubuntu, remembering vim commands is a contest. What is it under Kubuntu, Kate?

For the next bunch of Ubuntu tribes or eggs or flights whatever they are, maybe I'll remember to go into the existing /etc/fstab's and comment out the test partition.

Is there anything in the Installation & Upgrades" stickies that has a preferred solution for newbie's?
Jerry