Comment 4 for bug 106209

I am experiencing this bug with Kubuntu i386 20070417.

Prior to starting an install test this system had sda1 = swap, sda2 = boot, sda4 = /home, sda5 = edgy, sda6 = feisty, fully up to date. All working just fine and /home happily shared between edgy and feisty. Decided to test manual partitioning by replacing edgy with todays Kubuntu desktop daily build on sda5. Started ubiquity from the desktop icon, chose manual partitioning. Set sda5 as the new '/' partition set the other mount points accordingly, checked the boxes for sda5, swap and boot to be reformatted and proceeded with the install. The install completes without any obvious errors.

The new feisty install on sda5 boots and runs just fine. /home is still intact on sda4 and all my settings seem to be installed. The pre-existing feisty install on sda6 now fails to boot with the error:
Log of fsck -C -R -A -a
Tue Apr 17 19:22:39 2007

fsck 1.40-WIP (14-Nov-2006)
/dev/sda4: clean, 8344/7031360 files, 4488072/14058883 blocks
fsck.ext3: Unable to resolve 'UUID=c46aa308-75ca-435e-a036-8452cc09f867'
fsck.ext3: Unable to resolve 'UUID=c0a3d2d5-f4fb-434f-855d-c76adf08357c'
fsck died with exit status 8

Tue Apr 17 19:22:39 2007
----------------
That's the entire contents of /var/log/fsck/checkfs. Then I get dropped to a command prompt. Typing reboot takes me to the graphical login screen for sda6. If I try to login I get a blank desktop with a grey dialog box reading 'Could not start kstartupconfig. check your installation. I will attach the fstabs for both installs and the logs from todays installation, just in case they are useful