Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • I understand that my post is long, but it states explicitly that sharing is not an issue. Also, that the drive does not contain important data. So there is no operating system on it. Do you happen to know how to "unmount" the disk in Windows if you think this is the problem here?
    – phobic
    Commented Nov 23, 2013 at 21:57
  • Sorry, I have overlooked the sharing part. To "unmount" the disk, I think unassigning all drive letters or mount points from the partitions on that drive should be enough. You can do that in the Computer Management window (right-click Computer in the Start menu and click Manage). If that doesn't work, try with individual partitions instead of entire drive (a partition spanning over entire drive should work too). VBox manual covers this topic. Note that disks are indexed from 0, but partitions start from 1.
    – gronostaj
    Commented Nov 23, 2013 at 22:14
  • After unmounting the disk in Windows I can still reproduce the error with the above script.
    – phobic
    Commented Nov 23, 2013 at 23:41
  • Try rebooting. Reinstalling the same or updated version of VirtualBox may help too, there are some known issues with VMDK that are solved by VBox reinstallation.
    – gronostaj
    Commented Nov 23, 2013 at 23:45
  • After "repair" installation of the newest VB and reboot of the host and guest, I can still reliably reproduce the error.
    – phobic
    Commented Nov 25, 2013 at 11:59