I have just met this problem upon installing gutsy alongside my feisty install. As far as I understand it, the problem is caused by the installation process changing the UUID's of existing disk partitions, causing fsck to fail on the original system. Making any manual changes to the partition table without updating fstab also causes the boot sequence to drop into a maintenance shell. So in addition to the problem of the UUID changes, the fact that any inaccuracies in fstab halts the boot sequence is an issue in itself. There are many new users who would equate the absence of a X server with total system failure.
-- Feisty fsck Unable to resolve UUID https://bugs.launchpad.net/bugs/106209 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
