fail to install extension pack because of VERR_NOT_SAME_DEVICE

[leif walsh]

When trying to install a new version of the Oracle VM Virtualbox Extension Pack, I get the following error:

Progress state: NS_ERROR_FAILURE VBoxManage: error: Failed to uninstall "Oracle VM VirtualBox Extension Pack": The installer failed with exit code 1: VBoxExtPackHelperApp: error: Failed to rename the extension pack directory: VERR_NOT_SAME_DEVICE VBoxManage: error: rcExit=1 Progress state: NS_ERROR_FAILURE VBoxManage: error: Failed to install "/usr/share/virtualbox/extensions/Oracle_VM_VirtualBox_Extension_Pack-4.0.10.vbox-extpack": Extension pack 'Oracle VM VirtualBox Extension Pack' is already installed. In case of a reinstallation, please uninstall it first

I have /usr on a different partition than the rest of my system, I assume it is calling a rename() and getting errno = EXDEV. This should be handled properly instead of crashing.

[Frank Mehnert]

I've removed your last comment to save you from SPAM. The reporter of a ticket as well as everyone whoo posted at least one comment will automatically notified if a correct e-mail address was specified in the account settings.

[briang]

This appears to still be a problem in 4.2.

Is there a work around?

I am using Slax Linux (2.6.27.27).

root@slax:~/Downloads# VBoxManage extpack install --replace Oracle_VM_VirtualBox_Extension_Pack-4.2.0-80737.vbox-extpack
0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to install "/root/Downloads/Oracle_VM_VirtualBox_Extension_Pack-4.2.0-80737.vbox-extpack"
VBoxManage: error: The installer failed with exit code 1: VBoxExtPackHelperApp: error: Failed to rename the extension pack directory: VERR_NOT_SAME_DEVICE
VBoxManage: error: rcExit=1
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ExtPackManager, interface IExtPackManager
VBoxManage: error: Context: "int handleExtPack(HandlerArg*)" at line 1112 of file VBoxManageMisc.cpp
root@slax:~/Downloads#    

I tried chmod'ing the ExtensionPack directories to rwxrwxrwx, but that had no effect. I imagine the problem is related to what adlaiff6 reported.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.