VirtualBox error after deleting snapshot

6

I have a Windows 7 Professional 64-bit virtual machine running on a Ubuntu 14.04LTS. I deleted an old snapshot of this VM. It took over 30 minutes to delete and exactly at the end of the process the laptop unexpectedly shut down. After restarting the laptop, I tried to start the virtual machine and got the error:

Failed to open a session for the virtual machine Main.
Could not open the medium '/home/user/VirtualBox VMs/Main/Snapshots/{eeeeeeeee-ffff-4144-b555-bbbbbb}.vmdk'.
VD: error VERR_FILE_NOT_FOUND opening image file '/home/user/VirtualBox VMs/Main/Snapshots/{eeeeeeeee-ffff-4144-b555-bbbbbb}.vmdk' (VERR_FILE_NOT_FOUND).


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: Medium
Interface: IMedium {555bbb-a3a6-4b9b9-4949-acacacac}

Any idea on how to recover it?

windows-7
ubuntu
virtualbox
asked on Super User Nov 28, 2014 by MazarD • edited Dec 7, 2014 by Twisty Impersonator

3 Answers

7

Problem is that once a snapshot file is missing, Virtualbox will not allow you to delete the snapshot from the GUI. To "force-delete" the snapshot you will have to let Virtualbox believe the file is not missing. So just copy an existing one and rename it to the missing file's name. Then u need to set for each new file its correct UUID and its parent UUID. For example:

VBoxManage.exe internalcommands sethduuid "path\{c87e9357-5d1a-4d00-84d8-7b43293ab92e}.vmdk" c87e9357-5d1a-4d00-84d8-7b43293ab92e
VBoxManage.exe internalcommands sethdparentuuid "path\{c87e9357-5d1a-4d00-84d8-7b43293ab92e}.vmdk" c9e9b5a8-fb3f-42f8-aeb7-4458bf92f625

All the missing filenames and their UUIDs you can find in the Virtual Media Manager.

answered on Super User Aug 8, 2015 by Davor Josipovic
1

Ok, I found a solution!

I cloned the corrupted virtual machine with virtualbox manager and the clone started without problems, after it, one of the disks was unreadable, and running a chkdisk /f corrected it.

answered on Super User Nov 29, 2014 by MazarD
0

I tried following this, by copying one of the vdi files and renamed it. I opened the vbox file to find the parent and then followed the instructions. However I’m not seeing the “fake” snapshot. Nor can I update to any of my newer snapshots. For instance when I try to update to my newest snapshot, I’m getting the following. Any ideas? I’m desperate to get back to normal.

Failed to restore the snapshot Update of the virtual machine docker.

Parent UUID {36f02634-2f4f-45c7-bddd-ca66d64365b8} of the medium 'D:\VirtualBox VMs\docker\Snapshots/{ae8246bc-a77d-45bd-b063-a87377224254}.vdi' does not match UUID {fb67d9fb-5795-4e71-afc1-c38ab09004eb} of its parent medium stored in the media registry ('C:\Users\vamic\.VirtualBox\VirtualBox.xml').

Result Code: E_FAIL (0x80004005)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}


answered on Super User Sep 14, 2019 by WhiskerBiscuit

User contributions licensed under CC BY-SA 3.0