Where to fix fsck UUID error (stalling every boot if two Ubuntu installations)

Aaron Whitehouse lists at whitehouse.org.nz
Tue Dec 25 10:36:43 UTC 2007

Hello all,

I have a stable set of partitions (/, /home and swap) running Gutsy.
Up until last night this booted correctly. Last night I installed
Hardy Alpha 2 on my testing partition. From that point onwards, my
Gutsy install can no longer complete the boot process; fsck tries to
check the partition with the testing partition's old UUID but, because
the UUID of the testing partition has changed, fsck exits with an
error, the boot process is stalled and the user ends up at a
maintenance prompt.

This happened with my feisty/gutsy installs as well. The other effect
of this problem is that the testing partition is no longer displayed
on the desktop (it is still in the "Computer" screen).

My question is, where is the best place to fix this?

Is it to try and fix the installers so that the UUIDs of partitions do
not change if at all possible?

or to try and fix fsck so that it doesn't error?

or to try and fix upstart so that this type of error does not stop the
boot process?



FSF Associate Member: 5632

More information about the Ubuntu-devel-discuss mailing list