I updated from Karmic to Lucid about 12 hours ago and searching the cause for Lucid not booting took a lot of time. It turned out the problem was this very "usbfs" which I put into fstab to get USB working in VirtualBox. And unlike the description of this bug there was no error message hinting to USB; last thing i saw in recovery-mode was how my ext3 filesystems got mounted and then the booting process just stopped.
I'm pretty sure a large percentage of VirtualBox users edited fstab the same way and all these users will be left with a black screen after trying to boot their updated system, which might even cause some of them to do a complete reinstall of their system. I suggest that /etc/fstab is parsed during the update process and any lines containing "usbfs" as filesystem should be commented out. -- Lucid alpha 2 fails to start up unless you remove /proc/bus/usb from the fstab https://bugs.launchpad.net/bugs/507881 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
