I see this at a Xen DomU running a custom pv_ops Kernel. This DomU didn't start after the upgrade. Here's the output:
Begin: Running /scripts/local-premount ... done. [ 1.325687] kjournald starting. Commit interval 5 seconds [ 1.325719] EXT3-fs: mounted filesystem with writeback data mode. Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. mount: mount point /sys/fs/fuse/connections does not exist mountall: mount /sys/fs/fuse/connections [696] terminated with status 32 mountall: Filesystem could not be mounted: /sys/fs/fuse/connections mount: mount point /sys/fs/fuse/connections does not exist mountall: mount /sys/fs/fuse/connections [704] terminated with status 32 mountall: Filesystem could not be mounted: /sys/fs/fuse/connections init: mountall main process (692) terminated with status 3 rm: cannot remove `/forcefsck': Read-only file system init: mountall post-stop process (705) terminated with status 1 Mount of filesystem failed. A maintenance shell will now be started. CONTROL-D will terminate this shell and re-try. Give root password for maintenance (or type Control-D to continue): -- After update from 0.1.8 to 0.2.0, custom-compiled kernel without initramfs fails to boot https://bugs.launchpad.net/bugs/447525 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
