Comment 0 for bug 106209

fsck failures with unknown UUID's:

1. 4 boot system, Windows 98 hda1, Dapper hda2, Edgy hdb1, swap hdb2, Feisty hdb3
2. Last install 2 days ago was Edgy hdb1, Feisty hdb3 the one previously installed last week.
3. Feisty is all up to date
4. Booting hdb3 Feisty. Grub uses menu.lst entry from last install, the Edgy
5. fsck O.K. on hda, fsck fails on hdb on every boot. Where does fsck get the UUID's from?? They don't match the UUID's in the menu.lst's.
6. After fsck dies, boot stops at a command prompt, so I enter: halt
7. System goes on to boot GDM fine, I'm entering post from hdb3 Feisty:

fsck 1.40-WIP (14-Nov-2006)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/dev/hda1: 9588 files, 88593/261928 clusters
/dev/hda2: clean, 95147/1954560 files, 2415637/3905803 blocks
fsck.ext3: Unable to resolve 'UUID=fd3ea0b9-b41c-49dd-bdff-de5c2963d6cf'

fsck.ext3: Unable to resolve 'UUID=c97f1ce2-7b2d-4ac3-bc6d-04ed24b74b3b'

fsck died with exit status 8

From /boot/grub/menu.lst on currently running Feisty hdb3:

title Ubuntu, kernel 2.6.20-14-generic
root (hd1,2)
kernel /boot/vmlinuz-2.6.20-14-generic root=UUID=77c2f85d-7e8f-4a17-a85
e-815074292e27 ro quiet splash
initrd /boot/initrd.img-2.6.20-14-generic
quiet
savedefault

From /boot/grub/menu.lst on most recent install, Edgy Xubuntu hdb1:

title Ubuntu, kernel 2.6.20-14-generic (on /dev/hdb3) Ubuntu Feisty
root (hd1,2)
kernel /boot/vmlinuz-2.6.20-14-generic root=UUID=77c2f85d-7e8f-4a17-a85e-815074292e27 ro quiet splash
initrd /boot/initrd.img-2.6.20-14-generic
savedefault
boot