*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
** This bug has been marked a duplicate of bug 571444
Boot hangs and unable to continue when automount disk in fstab is not
available (Off or Disconnected)
--
cgroup in fstab prevents boot after upgrade
Ah hah!
I have managed to reproduce this on a relatively-fresh Lucid install now!
The key part of this was that there was a typo in the fstab, however
this locks up the entire boot process, and didn't under Karmic.
To reproduce:
* Install ubuntu 10.04 desktop amd64 (at least in my case,
I tried adding the --debug flag as requested -- boot.log just contains
this though:
# cat boot.log
fsck from util-linux-ng 2.17.2
/dev/vda1: clean, 146641/247504 files, 734980/988160 blocks
* Starting AppArmor profiles
Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
I didn't want to trash my work desktop, so tried creating a virtual machine
running a fresh Lucid Desktop install in order to try and recreate the bug.
However that fresh install doesn't exhibit the bug.
My real machine has more services that start up (mysql, postgresql, apache,
mt-daapd,
Please put that line back into your /etc/fstab, and then try the
following:
edit /etc/init/mountall.conf and add --debug - capture the boot output
(if you have a splash screen, it will be captured in /var/log/boot.log
for you)
** Package changed: upstart (Ubuntu) = mountall (Ubuntu)
** Changed
Right.. I seem to have found the problem, looks like a clear bug!
My /etc/fstab contained a line as follows - once I removed it, my system
was able to boot successfully:
cgroup /mnt/cgroup cgroup defaults 0 0
** Summary changed:
- Boot failure after upgrade - nothing started except mounts
+
