Judging by fstab in Feisty (old) OS, the swap (/dev/sda6) id was: # /dev/sda6 UUID=e971928e-487d-469b-823a-062cf5b39738 none swap sw 0 0
whereas, "sudo vol_id -u /dev/sda6" now gives: 4b7543af-65a7-4e9f-a52b-8868e82914cf But actually, the problem may be different or larger. Even though I changed my fstab so that it doens't use the id, but rather the name /dev/sda6, Feisty still doesn't boot. It points me to /var/log/checkfs, which says: ---------------- Log of fsck -C -R -A -a Tue Jun 19 08:01:55 2007 fsck 1.40-WIP (14-Nov-2006) dosfsck 2.11, 12 Mar 2005, FAT32, LFN /dev/sda1: 22771 files, 1026487/1278924 clusters fsck.ext3: Unable to resolve 'UUID=b32eafa9-1b4e-4031-b0fd-0180c473c710' /dev/sda7: clean, 85377/1632000 files, 3124450/3259179 blocks fsck died with exit status 8 Tue Jun 19 08:02:08 2007 ---------------- (end of log) Oh, I see. that's the root partition of Gutsy(beta). So that was also reformatted, and its UID also apparently changed, and so now Feisty cannot mount it. So, in case it helps, the old UUID for /dev/sda8, which is not Gutsy's root, is above in the log, but it was changed during install to: sudo vol_id -u /dev/sda8 07e81610-3fc0-4918-8ce3-836eb78c3c89 Summary: both the swap and the new / partition were formatted during Gutsy install and had their UUIDs changed, which seems undesirable. -- Installing new version (Gutsy) next to old reformats swap; makes swap fail on boot in other OSs https://bugs.launchpad.net/bugs/121124 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
