vboxsf: Error message after update

Papa Echo · 2018-08-21 04:42:23

Hello,
I am using Arch Linux from time to time in a VirtualBox VM. After I didn’t use the VM for a long time I made an update. First I updated VirtualBox to 5.2.18. Then I updated Arch Linux via pacman –Syu.
Every time I boot I get the following error message in front of the login prompt:
vboxsf: Old binary mount data not supported, remove obsolete mount.vboxsf and/or update your VBoxService.

My mount in .bashrc doesn’t work:
sudo mount -t vboxsf D_DRIVE /home/papa/d

I did a search and found the following link:
https://bugs.archlinux.org/task/58272

Unfortunately I don’t understand how to fix the problem. I hope someone can help me with step by step instructions.

jasonwryan · 2018-08-21 04:57:56

Not an Installation issue, moving to NC...

seth · 2018-08-21 06:38:00

Did you reboot after the update?

uname -r
file `which mount.vboxsf`

Try

sudo mount -cit vboxsf D_DRIVE /home/papa/d

but on an unrelated note: you probably don't want to handle that in your .bashrc at all.

Papa Echo · 2018-08-21 17:34:46

Yes, I rebooted.

The commands
uname -r
file `which mount.vboxsf`

didn’t show me the files, but I found mount.vboxsf in /usr/bin/ and /usr/lib/virtualbox/

I have tried the mount –cit and got these error messages:
Kobject_add_internal failed for vboxsf-D_DRIVE with –EEXIST, don’t try to register things with the same name in the same directory.
mount: d: mount(2) systemcall failed: the file already exists.

I found out that I could add something in /etc/fstab, but I don’t know how.
What can I do now?

seth · 2018-08-21 18:51:20

didn’t show me the files

I do not understand what you're suggesting to have expected from that output, but you are expected to post that output.

The following mount failure suggests that something has already been mounted into this path.

https://wiki.archlinux.org/index.php/Fstab

Papa Echo · 2018-08-21 19:26:08

This is the output from uname -r: 4.18.3-arch1-1-ARCH

file `which mount.vboxsf` gives me an error message:
which mount.vboxsf: cannot open 'which mount.vboxsf' (No such file or directory)

seth · 2018-08-21 19:37:19

Those are backticks....
Try "file $(which mount.vboxsf)"

Papa Echo · 2018-08-21 19:47:10

This is the output from file $(which mount.vboxsf):
/usr/bin/mount.vboxsf: Bourne-Again shell script, ASCII text executable

This is the content of the file:
#!/bin/bash

# Hopefully this works as intented, supporting both pre-4.16 and newer kernels
# https://bugs.archlinux.org/task/58272#comment168687

kver_major=$(uname -r | cut -d. -f1)
kver_minor=$(uname -r | cut -d. -f2)

if ((kver_major * 100 + kver_minor < 416)); then
exec /usr/lib/virtualbox/mount.vboxsf "$@"
fi

# mount(1) annoyingly prepends the current directory to the source
name=${1#$PWD/}; shift

# Mainline vboxsf accepts regular mount opts
exec /usr/bin/mount -cit vboxsf "$name" "$@"

seth · 2018-08-22 05:43:13

Please use code tags for posting scripts or shell output.

So the actual mount.vboxsf should not be invoked in the first place, did you replace the entry in your bashrc w/ "sudo mount -cit vboxsf D_DRIVE /home/papa/d" (and reboot) when you got the EEXIST or did you just try to run it after multiple attempts to mount the drive?

Papa Echo · 2018-08-22 06:07:00

I apologize for not knowing how to use this forum editor. I am going to learn it.

I had tried to mount in a terminal without reboot.
Now I have renamed both mount.vboxsf files. Then I have edited the .bashrc file and changed the mount command option to –cit. After a reboot I still get the error message that is in my post #1.
After logging in I don’t get an error message now, but if I look into the mounted directory, it is empty.

Papa Echo · 2018-11-23 23:38:06

Here is an update to my problem:
Kernel 4.18 obviously had some issues with the integration of VirtualBox Guest Editions.

The problem could be solved with a single change in the settings of Virtualox:
1. Click on “Shared folders”.
2. Mark the folder and then click on change
3. Remove the check for “Automatic mounting”

Arch Linux

#1 2018-08-21 04:42:23

vboxsf: Error message after update

#2 2018-08-21 04:57:56

Re: vboxsf: Error message after update

#3 2018-08-21 06:38:00

Re: vboxsf: Error message after update

#4 2018-08-21 17:34:46

Re: vboxsf: Error message after update

#5 2018-08-21 18:51:20

Re: vboxsf: Error message after update

#6 2018-08-21 19:26:08

Re: vboxsf: Error message after update

#7 2018-08-21 19:37:19

Re: vboxsf: Error message after update

#8 2018-08-21 19:47:10

Re: vboxsf: Error message after update

#9 2018-08-22 05:43:13

Re: vboxsf: Error message after update

#10 2018-08-22 06:07:00

Re: vboxsf: Error message after update

#11 2018-11-23 23:38:06

Re: vboxsf: Error message after update

Board footer