![]() Is there something I can do about this from the Ubuntu side? Or does anyone happen to know more about this from the Virtualbox angle? Here's the fstab line, just for completeness: Documents /home/benme/Documents vboxsf uid=benme,gid=benme,dmode=774,fmode=664 0 0 This suggests to me that it's some sort of timing issue, where Virtualbox isn't "ready" to provide the shared file mounts at the point /etc/fstab mounts are run during bootup. Note that when I mount manually I'm letting mount take all the options from /etc/fstab, and it works. sbin/mount.vboxsf: mounting failed with the error: No such deviceīut if I instead skip mounting during boot, wait for Unity to start and then mount manually in a shell, everything works fine: benme-vb ~ % ls Documents Pressing M for manual recovery and then trying to mount manually also fails: cd mount Documents Keys:Press S to skip mounting or M for manual recovery I get the following error during boot: An error occurred while mounting /home/benme/Documents. Until recently this setup worked just fine, but after upgrading from Ubuntu 13.04 and Virtualbox 4.2 (at essentially the same time) the fstab mounting stopped working. I have a couple of Virtualbox shared folders being mounted by /etc/fstab. ![]() ![]() I've got Ubuntu 13.10 installed in Virtualbox 4.3. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |