Opened 14 years ago
Last modified 14 years ago
#6696 closed defect
Shared folder mount fails during boot of Linux guest (using /etc/fstab) - Ubuntu 10.04LTS — at Initial Version
| Reported by: | Jim Avera | Owned by: | |
|---|---|---|---|
| Component: | shared folders | Version: | VirtualBox 3.1.8 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Linux |
Description
Errors occur when booting a linux guest if /etc/fstab tries to mount a shared folder. After boot-up the share is mounted in spite of the error, but only root can write files in it.
When the error is reported during booting, Ubuntu asks whether to 'Skip' the mount or 'Manually recover' via a root prompt. If Manual recovery is selected, then 'mount' does not show the share as being mounted, and "mount -t vboxsf sharename /mountpt" fails with "/sbin/mount.vboxsf: mounting failed with the error: No such device".
After boot completes (or after reboot and selecting 'Skip' when the error is reported), then the share IS mounted. I'm guessing that 'mountall' is run multiple times during the boot sequence, and it succeeds later on in the boot.
However, non-root users get 'Permission denied' when trying to create files in the shared folder. Reading works. The permission problem is not fixed by umount + new mount, and making the UID & GID in guest the same as the owner of the mounted directory in the host does not help.
Share definition: Name=hosttmp Path=/tmp Access=Full
Guest's /etc/fstab entry: hosttmp /hosttmp vboxsf nodev,noexec,nosuid 0 0
NOTE: The http://www.virtualbox.org/wiki/Changelog 3.1.8 Changelog reports that a bug preventing mounting shares via /etc/fstab was fixed. So this may be a different problem.
Both host and guest are running Ubuntu 10.04LTS on amd64, but the VM was created earlier while the host was running an older ubuntu release (9.10). '
