unable to mount shared drive on "deepin", "Raspberry Pi" guests

[soliphant]

I am running VirtualBox 6.0.14 r133895 on Fedora 30. I have two linux clients:

• raspberry pi desktop and
• deepin

Both guests have the VBoxGuestAdditions_6.0.14 installed.

I have a shared drive:

• Folder path: /work
• Folder Name: work
• Auto-mount: on
• Mount point: /work.

The guest linux has a mount point /work with chmod 777 set. The user is a member of the vboxsf group. When the guest is started /work is not mounted (expected). I issue a:

Code: Select all

sudo mount -t vboxsf /work /work

I receive a:

shared folder /work was not found (check VM settings).

When I issue a:

Code: Select all

sudo mount -t vboxsf work /work

I receive a:

/sbin/mount.vboxsf: mounting failed with the error: Invalid argument.

What am I missing? I thought I had set everything up correctly. Note: my Windows 10 guest has no problems

[socratis]

Both guests have the VBoxGuestAdditions_6.0.14 installed.

How sure are you about this part? I'm not so sure about the 'Raspberry Pi' one (at all actually), and I have my doubts about the 'deepin' one.

Let's focus on the 'deepin' part first. I need to see the output of the Guest Additions (GAs) installation. If the installation worked as intended, and you have enabled "Shared Clipboard" in the VM Settings, you should be able to Copy that installation text and Paste it as text in your reply.

• Auto-mount: on
...
I issue a:

• sudo mount -t vboxsf /work /work

If you have Auto-mount on, you shouldn't need to issue a 'mount' command, it defeats the whole purpose of existence for the Auto-mount option.

my Windows 10 guest has no problems

Windows != Linux.

Again, focusing on the 'deepin' part first, we need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe or recreate the problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[soliphant]

The attached log is from a complete VM run.
line 1159:
Host path '/work', map name 'work', writable, automount=true, automntpnt=/, create_symlinks=false, missing=false

[soliphant]

I was asked to reinstall the guest additions:

sudo su
root@steve-deepin:/home/steve# cd /media/cdrom/
root@steve-deepin:/media/cdrom# ls
AUTORUN.INF  OS2		      VBoxDarwinAdditionsUninstall.tool  VBoxWindowsAdditions.exe
autorun.sh   runasroot.sh	      VBoxLinuxAdditions.run		 VBoxWindowsAdditions-x86.exe
cert	     TRANS.TBL		      VBoxSolarisAdditions.pkg
NT3x	     VBoxDarwinAdditions.pkg  VBoxWindowsAdditions-amd64.exe
root@steve-deepin:/media/cdrom# ./VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.0.14 Guest Additions for Linux........
VirtualBox Guest Additions installer
Removing installed version 6.0.14 of VirtualBox Guest Additions...
update-initramfs: Generating /boot/initrd.img-4.15.0-30deepin-generic
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel 
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel 
4.15.0-30deepin-generic.
update-initramfs: Generating /boot/initrd.img-4.15.0-30deepin-generic
WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is deprecated and will stop working in the future. Use /etc/cryptsetup-initramfs/conf-hook instead.
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
VirtualBox Guest Additions: Running kernel modules will not be replaced until 
the system is restarted
root@steve-deepin:/media/cdrom#

After a reboot - no change