Comment 9 for bug 1339249
Revision history for this message
| Marshall Sorenson (marshall-sorenson) wrote | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I occasionally have this identical issue with Ubuntu when running it as a VirtualBox appliance. It happens when there is an fstab entry to mount a device on boot, but the device doesn't exist. I suppose there could be other possible issues, perhaps where the device name has changed for some reason, but essentially that is just as bad since mount is very picky.
In my case it happens when I have manually created an fstab entry to mount a shared folder (vboxfs), which has been removed from the virtual machine's settings or source folder deleted from the host machine.
To fix you must drop into recovery mode on boot, remount the root partition as read/write if necessary, edit fstab to fix or comment out the offending entry, save it and reboot.
I hope this helps you solve your problem guys, good luck!