Discard snapshot failed - disk not accessible

otto.behrens · Post by **otto.behrens** » 25. Sep 2008, 06:51

Hi,

I am desperately begging for help now. Please just point me in a direction to search on.

I tried to discard a snapshot (I have discarded quite a few before; I'm running out of disk space). I started this last night (around 10 pm) and to my surprise it was still running this morning. Since having done this before, I realised that something is not well and killed it. The last timestamp on any of my vdi files is 22:12, so it appears as if the process was broken. I downloaded 1.6.6 (virtualbox_1.6.6-35336_Ubuntu_hardy_amd64.deb), installed it.

Trying to start up again, I'm getting that the disk is not accessible because of a UUID mismatch (details below). Is there a way to fix the Snapshot? I'm using differencing disks.

I've been using VirtualBox OSE 1.5.6 on Ubuntu 8.04, got into trouble (described below) and decided to upgrade to 1.6.6 (non-OSE). This is in the log: VirtualBox 1.5.6 r28266 linux.amd64 (Feb 20 2008 16:30:37).

Thanks a lot
Otto

"VM cannot start because the hard disk '/home/otto/.VirtualBox/Machines/Vista/Snapshots/{34157b2c-9bae-413f-37b9-2c3d645083b3}.vdi' is not accessible (UUID {deb633db-419d-4b9f-84bc-5ef65f536cee} of the parent image '/home/otto/.VirtualBox/Machines/Vista/Snapshots/{a0af212d-96bd-4a4b-29a7-1f0dc9006fb4}.vdi' stored in the hard disk image file '/home/otto/.VirtualBox/Machines/Vista/Snapshots/{3a0df3da-9bc9-4b3d-2384-a2f8722ecfd8}.vdi' doesn't match UUID {a0af212d-96bd-4a4b-29a7-1f0dc9006fb4} stored in the registry).

Result Code: 0x80004005
Component: Console
Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}"

otto.behrens · Post by **otto.behrens** » 25. Sep 2008, 06:57

I got the following in the logs after shutting down my Vista machine (before the snapshot was discarded):

"34:19:32.822 Changing the VM state from 'RUNNING' to 'OFF'.
34:19:32.823 ERROR [COM]: aRC=0x80004005 aIID={12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d} aComponent={Session} aText={Assertion failed: [SUCCEEDED (rc)] at '/home/vbox/vbox-1.5.6/src/VBox/Main/SessionImpl.cpp' (194) in virtual nsresult Session::GetMachine(IMachine**).
34:19:32.823 COM RC = 0x80004005
34:19:32.823 .
34:19:32.823 Please contact the product vendor!} aPreserve=false
34:19:32.823 ERROR [COM]: aRC=0x80004005 aIID={12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d} aComponent={Session} aText={Assertion failed: [SUCCEEDED (rc)] at '/home/vbox/vbox-1.5.6/src/VBox/Main/SessionImpl.cpp' (194) in virtual nsresult Session::GetMachine(IMachine**).
34:19:32.824 COM RC = 0x80004005
34:19:32.824 .
34:19:32.824 Please contact the product vendor!} aPreserve=false
34:19:32.879 Console::powerDown(): a request to power off the VM has been issued (mMachineState=8, InUninit=0)
34:19:32.879 Changing the VM state from 'OFF' to 'DESTROYING'."

And this when discarding the snapshot:

"34:19:33.667 Changing the VM state from 'DESTROYING' to 'TERMINATED'.
34:19:33.676 ERROR [COM]: aRC=0x80004005 aIID={12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d} aComponent={Session} aText={Assertion failed: [SUCCEEDED (rc)] at '/home/vbox/vbox-1.5.6/src/VBox/Main/SessionImpl.cpp' (194) in virtual nsresult Session::GetMachine(IMachine**).
34:19:33.676 COM RC = 0x80004005
34:19:33.676 .
34:19:33.676 Please contact the product vendor!} aPreserve=false
34:19:33.677 ERROR [COM]: aRC=0x80004005 aIID={12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d} aComponent={Session} aText={Assertion failed: [SUCCEEDED (rc)] at '/home/vbox/vbox-1.5.6/src/VBox/Main/SessionImpl.cpp' (194) in virtual nsresult Session::GetMachine(IMachine**).
34:19:33.677 COM RC = 0x80004005
34:19:33.677 .
34:19:33.677 Please contact the product vendor!} aPreserve=false
34:19:33.804 ERROR [COM]: aRC=0x80004005 aIID={12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d} aComponent={Session} aText={Assertion failed: [SUCCEEDED (rc)] at '/home/vbox/vbox-1.5.6/src/VBox/Main/SessionImpl.cpp' (194) in virtual nsresult Session::GetMachine(IMachine**).
34:19:33.804 COM RC = 0x80004005"

Thanks, Otto

otto.behrens · Post by **otto.behrens** » 25. Sep 2008, 12:56

At this point I can tell you that I am desperate for help. I've scanned a number of posts and googled quite a bit and could not find a resolution for this problem; I am solidly stuck. I am running my payroll system on this installation and need to do payroll today (worst case is tomorrow). It will cost me at least a day to get back where I was (I've probably lost a bit as well), which means *a lot* to me at this point. Please help!

Thanks
Otto

Post by **Sasquatch** » 26. Sep 2008, 22:17

For more in-dept info about VDIs, snapshots and their structure, please see the Tutorial: All about VDIs. It should provide you with enough information to solve this. You can also use the search, as some users have had it before that one shapshot was unreadable (they removed/moved it using a file manager) and was fixed later with some help.

otto.behrens · Post by **otto.behrens** » 27. Sep 2008, 08:26

Thanks, the tutorial was very helpful. I did some of the fixing in there, but missed that there was another .xml file <VM>.xml that also contained the snapshot uuid.

I must have searched on the wrong things then because I could not find a fix.

I fixed the <VM>.xml file up and got it booted now, thanks a lot.