Page 1 of 2

VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:03
by ajjdkrnasnl93m
Suddenly getting an error on a virtual machine that was running fine. Looks like the problem may be with the snapshots associated with the VM rather than the vm itself.

"Could not get the storage format of the medium"

Important I get this vm restored. Anyone got ideas or can you lead me to a post which addresses these errors. When I searched, couldn't find anything. Not really sure what the error means.

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:06
by Perryg
What version of VirtualBox are you using and what version was the guest created with?
How many snapshots do you have?

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:24
by ajjdkrnasnl93m
Virtualbox 4.1.6 r74713 with 4.1.6 guest additions
5 snapshots
I have tried a couple of hosts: Windows XP, Ubuntu 11.04
Guest that is causing problem is: Windows XP

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:25
by ajjdkrnasnl93m
I think the original guest was created with Virtualbox 4.1.4

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:28
by ajjdkrnasnl93m
I saw this in another post....it looks like a vmdk might be repairable with this tool.

vmware-vdiskmanager -R broken-inconsistency.vmdk

I don't have this tool. Anyone ever tried this tool to successful repair a broken (corrupted) vm?

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:32
by Perryg
Have you tried to start the next to last snapshot? This should tell you if the last child is damaged.
Did the guest crash or anything that you remember that would have caused this?

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:37
by ajjdkrnasnl93m
I have tried all snapshots. Each give the same VERR_NOT_SUPPORTED error. That probably means I was wrong about it being a snapshot problem and instead it is probably a base vm problem.

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:39
by ajjdkrnasnl93m
VM was on an external hard drive and I remember seeing errors when it went down. Can't remember the errors. Seems like it was having write issues to the external hard drive.

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:41
by ajjdkrnasnl93m
I have copied the folder for the vm to another drive. Tried to run it there and get:

Failed to open a session for the virtual machine BLOCK 1

No error info.

Result Code: E_FAIL (0x80004005)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:44
by ajjdkrnasnl93m
In the copy I made, even though I am getting the error posted above, it is attempting to load, but it is loading in full screen mode. How do I change states so it is opening in normal window mode. Hitting HOST KEY+F doesn't work because the vm errors before I can get it out of full screen mode. Just want to get out of full screen mode to insure that full screen mode isn't part of the issue.

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:46
by Perryg
Post the guests log file (as an attachment) instead. You really want to stay out of the *.vbox file if at all possible.

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:50
by ajjdkrnasnl93m
Guest Log File:

VirtualBox 4.1.6 r74713 win.x86 (Nov 4 2011 13:40:24) release log
00:00:01.535 Log opened 2011-11-17T02:47:19.744375000Z
00:00:01.535 OS Product: Windows XP Professional
00:00:01.535 OS Release: 5.1.2600
00:00:01.535 OS Service Pack: 2
00:00:01.536 Host RAM: 1535MB RAM, available: 372MB
00:00:01.536 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:01.537 Process ID: 7232
00:00:01.537 Package type: WINDOWS_32BITS_GENERIC
00:00:01.537 Installed Extension Packs:
00:00:01.537 Oracle VM VirtualBox Extension Pack (Version: 4.1.6 r74713; VRDE Module: VBoxVRDP)
00:00:02.323 Power up failed (vrc=VINF_SUCCESS, rc=E_FAIL (0X80004005))

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:56
by Perryg

Code: Select all

00:00:01.536 Host RAM: 1535MB RAM, available: 372MB
How much RAM have you assigned to the guest?

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 04:59
by ajjdkrnasnl93m
299 MB

Re: VERR_NOT_SUPPORTED

Posted: 17. Nov 2011, 05:01
by Perryg
Have you tried rebooting the host to clear out any cached memory and see if the guest will run then?