Kein Mount eines Shared-Folders mehr möglich

Allgemeine Diskussionen über den Einsatz von VirtualBox.

Re: Kein Mount eines Shared-Folders mehr möglich

Postby rolfi » 5. Aug 2021, 16:43

Thanks to all answers. In the meantime I tried different things. First I upgraded to 6.1.26. Then I avoided a double mounting as you, fth0, mentioned. No difference. I cannot mount any shared folders within my Linux guests anymore for my hosts Mac OS and Windows 10 (both with latest updates). Exception is my Manjaro Linux guest, shared folders are working there, a mounting is possible. Today I installed a new openSuse Linux with the guest additions on my Mac (no issues or events during install, I can resize the guest window), but I have the the same error:
Code: Select all   Expand viewCollapse view
rolfi@localhost:~> sudo mount -t vboxsf transfer /home/rolfi/transfer
/sbin/mount.vboxsf: shared folder '/home/rolfi/transfer' was not found (check VM settings / spelling)

or
Code: Select all   Expand viewCollapse view
rolfi@localhost:~> sudo mount -t vboxsf -o uid=1000,gid=100 transfer ~/transfer
[sudo] Passwort für root:
/sbin/mount.vboxsf: shared folder '/home/rolfi/transfer' was not found (check VM settings / spelling)

The sub-directory in my openSuse guest exists of course. I did a "make transfer".
My shared folder settings in VirtualBox are:
  • Transient Folders
  • Folder Path: /Users/rolfi/transfer (this is the path on my Mac-Host)
  • Folder Name: transfer
  • _ Read only (not set)
  • _ Auto mount (not set)
  • Mount Point (not set, empty)
  • _ Make Permanent (not set)
Where is my mistake?

fth0 wrote:Because the VirtualBox Shared Folders are not a full-fledged folder sharing functionality, in contrast to network shared folders. For example, I don't know if and how VirtualBox handles file locking on the host OS side. In consequence, there could be a reason to prevent double mounting of a host folder on some host OSs. Another possibility would be that macOS changed its interface to folder sharing, and VirtualBox didn't adapt to it.
rolfi
 
Posts: 11
Joined: 14. Apr 2013, 20:29

Re: Kein Mount eines Shared-Folders mehr möglich

Postby rolfi » 5. Aug 2021, 16:51

Here is my log.
Attachments
vblog.zip
(33.12 KiB) Downloaded 2 times
rolfi
 
Posts: 11
Joined: 14. Apr 2013, 20:29

Re: Kein Mount eines Shared-Folders mehr möglich

Postby fth0 » 5. Aug 2021, 22:47

I tried it now myself, ran into the same problem, and found the background reason and two solutions:

If automatic mounting is configured, and no Mount point is configured, the folder is mounted as /mnt/sf_Folder Name.

If manual mounting is configured, and no Mount point is configured, the guest folder must be named sf_Folder Name.

In consequence, you can either configure Mount point to some dummy name, or name your guest folder sf_transfer.
fth0
Volunteer
 
Posts: 2470
Joined: 14. Feb 2019, 03:06
Location: Germany
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...

Re: Kein Mount eines Shared-Folders mehr möglich

Postby arQon » 20. Sep 2021, 10:57

fth0 wrote:If manual mounting is configured, and no Mount point is configured, the guest folder must be named sf_Folder Name.


per my comment in the 6.1.26 thread, this isn't *quite* correct (IME, at least) : you can still mount a folder with any name you like, but only once the guest has made it through some "intermediate" stage - i.e. there's some bug in a piece of deferred/lazy/etc GA code that causes NON-"sf_*" folder names to fail for a while until the GAs finish getting themselves sorted out.
arQon
 
Posts: 152
Joined: 1. Jan 2017, 09:16
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Ubuntu 16.04 x64, W7

Previous

Return to Allgemeine Diskussionen

Who is online

Users browsing this forum: No registered users and 7 guests