Error When i opened Virtual machine

Discussions related to using VirtualBox on Windows hosts.
Post Reply
anyways1
Posts: 4
Joined: 3. Nov 2019, 01:40

Error When i opened Virtual machine

Post by anyways1 »

Hello
I hope everybody is fine.My VM was fine.next day when i tried to start .it stopped working and shut down

Here is the log
00:00:01.813282 VirtualBox VM 6.0.10 r132072 win.amd64 (Jul 12 2019 09:34:54) release log
00:00:01.813289 Log opened 2019-11-01T20:41:20.193933900Z
00:00:01.813290 Build Type: release
00:00:01.813293 OS Product: Windows 8.1
00:00:01.813295 OS Release: 6.3.9600
00:00:01.813296 OS Service Pack: 
00:00:01.880233 DMI Product Name: 20351
00:00:01.884300 DMI Product Version: Lenovo G50-70
00:00:01.884310 Host RAM: 6036MB (5.8GB) total, 3277MB (3.2GB) available
00:00:01.884313 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
00:00:01.884314 Process ID: 7060
00:00:01.884315 Package type: WINDOWS_64BITS_GENERIC
00:00:01.884882 Installed Extension Packs:
00:00:01.884921   Oracle VM VirtualBox Extension Pack (Version: 6.0.10 r132072; VRDE Module: VBoxVRDP)
00:00:01.885460 Console: Machine state changed to 'Starting'
00:00:02.003463 Qt version: 5.6.2
00:00:02.005274 Console: Machine state changed to 'PoweredOff'
00:00:02.007509 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:02.045302 Power up failed (vrc=VINF_SUCCESS, rc=E_FAIL (0X80004005))
00:00:02.545574 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1360x684
00:00:02.545656 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:02.546045 GUI: Aborting startup due to power up progress issue detected...
I had 4 snapshots of my virtual machine and i was using 4th snapshot. 1st two snapshots are Working fine. 3rd and fourth snapshot is merged into Parent-child (3rd snapshot became parent) and 4th snapshot (became child). And fourth snap shot is giving error (vdI:ErrorReading pre-header in C:\path to snap shot).
Could not open the medium 'C:\Users\user\VirtualBox VMs\security\Snapshots/{ce66bbaf-8fd0-4bda-9c6e-0ba21a994a98}.vdi'.
VDI: error reading pre-header in 'C:\Users\user\VirtualBox VMs\security\Snapshots/{ce66bbaf-8fd0-4bda-9c6e-0ba21a994a98}.vdi' (VERR_EOF).
VD: error VERR_VD_VDI_INVALID_HEADER opening image file 'C:\Users\user\VirtualBox VMs\security\Snapshots/{ce66bbaf-8fd0-4bda-9c6e-0ba21a994a98}.vdi' (VERR_VD_VDI_INVALID_HEADER).
i dont know what happened.i will be very thankfull if any one helps me in this regard

Best regards
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Error When i opened Virtual machine

Post by socratis »

anyways1 wrote:
VD: error VERR_VD_VDI_INVALID_HEADER opening image file 'C:\Users\user\VirtualBox VMs\security
\Snapshots/{ce66bbaf-8fd0-4bda-9c6e-0ba21a994a98}.vdi' (VERR_VD_VDI_INVALID_HEADER).
Your "{ce66bbaf... vdi}" is corrupt. Take a look at "Snapshot basics" to have a better understanding and to see what your options are.

I want to see the recipe of the VM, the ".vbox" file. Right-click on the VM in the VirtualBox Manager, select "Show in Explorer". ZIP the selected ".vbox" file and attach it to your response.

Also I would like the output (as text, not as a picture) of the following command from the Command Prompt:
  • 
    dir /s "C:\Users\user\VirtualBox VMs\security\"
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
anyways1
Posts: 4
Joined: 3. Nov 2019, 01:40

Re: Error When i opened Virtual machine

Post by anyways1 »

hye
Thanks for helping me. i didnt delete any snapshot then how it is corrupted ?
will be very thankfull to you if you help me to recover it or its data.
I have attached the .vbox file and the output of the command .
08/25/2019  01:30 AM    <DIR>          .
08/25/2019  01:30 AM    <DIR>          ..
07/30/2018  01:01 AM       349,079,364 2018-07-29T20-01-42-840837200Z.sav
07/30/2018  10:51 PM       716,432,463 2018-07-30T17-50-32-539850500Z.sav
07/31/2018  12:27 AM       665,406,195 2018-07-30T19-27-16-595290900Z.sav
04/08/2019  05:18 PM                 0 2019-04-08T12-15-38-409051000Z.sav
08/25/2019  01:30 AM         2,097,152 {0d360d0e-83e7-4f33-919a-5e783b8bc2cb}.vdi
08/20/2019  02:23 AM         2,097,152 {11e740ce-76b4-4178-9b02-e6110cf958c8}.vdi
07/30/2018  10:50 PM     7,064,256,512 {2bf80d16-8fcb-4f53-9d2a-056c1e30ef93}.vdi
07/30/2019  11:53 AM    13,270,777,856 {45e4c283-80b1-46a0-aa17-a3b32edd995e}.vdi
08/20/2019  06:55 PM         2,097,152 {5e7f7d1d-31aa-493a-9af7-35ff007c761e}.vdi
08/20/2019  03:18 AM         2,097,152 {9bdeb85e-6580-46b6-b297-7d45a0a2f5fd}.vdi
08/20/2019  04:23 AM       369,098,752 {a8986780-d5b5-477e-92c8-59b1bfe4523e}.vdi
08/20/2019  02:29 AM       110,100,480 {c52779b2-2487-4e3b-aba8-28ac6e2165f2}.vdi
07/31/2018  12:27 AM       871,366,656 {c92e2b08-f725-4a71-b7dd-7f9eb48505ed}.vdi
04/08/2019  05:15 PM                 0 {ce66bbaf-8fd0-4bda-9c6e-0ba21a994a98}.vdi
              14 File(s) 23,424,906,886 bytes

     Total Files Listed:
              23 File(s) 33,399,233,287 bytes
               8 Dir(s)  79,765,549,056 bytes free
Best regards
Attachments
virtualboxfile.zip
This is .vbox file.
(3.15 KiB) Downloaded 9 times
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Error When i opened Virtual machine

Post by socratis »

Why in the seven kingdoms did you include the ".vbox-prev" and not the ".vbox" as instructed? I don't get it. Second, you did not enter the command I asked you to, you chose to just show me the "Snapshots" directory output, not the parent! :shock:

Listen... if you want to continue this, you got to do as told. Not as you think you should be doing, is that clear?

The situation is as following:
Snapshot 1                  security.vdi                                             ???
 |- Snapshot 2              {2bf80d16-8fcb-4f53-9d2a-056c1e30ef93}.vdi     7,064,256,512
     |- Snapshot 3          {c92e2b08-f725-4a71-b7dd-7f9eb48505ed}.vdi       871,366,656
         |- Snapshot 4      {ce66bbaf-8fd0-4bda-9c6e-0ba21a994a98}.vdi                 0
         |- Current State   {45e4c283-80b1-46a0-aa17-a3b32edd995e}.vdi    13,270,777,856
Your "Snapshot 4" is 0-bytes, which means it's toast, not recoverable, gone. If you read the article I gave you you will know why. Your only option is to delete "Snapshot 4" and remove it from the snapshot chain.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
anyways1
Posts: 4
Joined: 3. Nov 2019, 01:40

Re: Error When i opened Virtual machine

Post by anyways1 »

Hye
Thanks for replying.you misunderstood me. i did according to your Instructions.

When i clicked on show in Explorer, New window opened where my virtual machine files are. There was only one file shown with extension .vbox-prev. So i sent you. Now i found another file of VM which is also .vbox Extension.Security.vbox. Is it the same which you asking me to send?

And mistakenly i copied the half of the output of that Command.Here is the full out put.
C:\Users\user>dir /s "C:\Users\user\VirtualBox VMs\security\"
 Volume in drive C is Windows8_OS
 Volume Serial Number is 5613-CC87

 Directory of C:\Users\user\VirtualBox VMs\security

11/04/2019  02:59 AM    <DIR>          .
11/04/2019  02:59 AM    <DIR>          ..
11/03/2019  05:19 AM    <DIR>          Logs
11/03/2019  05:19 AM            17,299 security.vbox
11/03/2019  05:19 AM            17,299 security.vbox-prev
07/30/2018  01:01 AM     9,974,054,912 security.vdi
08/25/2019  01:30 AM    <DIR>          Snapshots
11/04/2019  02:59 AM             3,226 virtualboxfile.zip
               4 File(s)  9,974,092,736 bytes

 Directory of C:\Users\user\VirtualBox VMs\security\Logs

11/03/2019  05:19 AM    <DIR>          .
11/03/2019  05:19 AM    <DIR>          ..
11/03/2019  05:19 AM             1,485 VBox.log
11/02/2019  01:41 AM             1,486 VBox.log.1
11/02/2019  01:36 AM             1,486 VBox.log.2
10/03/2019  02:19 AM             1,486 VBox.log.3
11/03/2019  05:19 AM           227,722 VBoxHardening.log
               5 File(s)        233,665 bytes

 Directory of C:\Users\user\VirtualBox VMs\security\Snapshots

08/25/2019  01:30 AM    <DIR>          .
08/25/2019  01:30 AM    <DIR>          ..
07/30/2018  01:01 AM       349,079,364 2018-07-29T20-01-42-840837200Z.sav
07/30/2018  10:51 PM       716,432,463 2018-07-30T17-50-32-539850500Z.sav
07/31/2018  12:27 AM       665,406,195 2018-07-30T19-27-16-595290900Z.sav
04/08/2019  05:18 PM                 0 2019-04-08T12-15-38-409051000Z.sav
08/25/2019  01:30 AM         2,097,152 {0d360d0e-83e7-4f33-919a-5e783b8bc2cb}.vdi
08/20/2019  02:23 AM         2,097,152 {11e740ce-76b4-4178-9b02-e6110cf958c8}.vdi
07/30/2018  10:50 PM     7,064,256,512 {2bf80d16-8fcb-4f53-9d2a-056c1e30ef93}.vdi
07/30/2019  11:53 AM    13,270,777,856 {45e4c283-80b1-46a0-aa17-a3b32edd995e}.vdi
08/20/2019  06:55 PM         2,097,152 {5e7f7d1d-31aa-493a-9af7-35ff007c761e}.vdi
08/20/2019  03:18 AM         2,097,152 {9bdeb85e-6580-46b6-b297-7d45a0a2f5fd}.vdi
08/20/2019  04:23 AM       369,098,752 {a8986780-d5b5-477e-92c8-59b1bfe4523e}.vdi
08/20/2019  02:29 AM       110,100,480 {c52779b2-2487-4e3b-aba8-28ac6e2165f2}.vdi
07/31/2018  12:27 AM       871,366,656 {c92e2b08-f725-4a71-b7dd-7f9eb48505ed}.vdi
04/08/2019  05:15 PM                 0 {ce66bbaf-8fd0-4bda-9c6e-0ba21a994a98}.vdi
              14 File(s) 23,424,906,886 bytes

     Total Files Listed:
              23 File(s) 33,399,233,287 bytes
               8 Dir(s)  79,516,856,320 bytes free
What about the data in VM. I didn't delete any snapshot then how this bullshit happened. I will be very thankful if you help me to recover its data.

One thing which i noticed in the chain of virtual machine snapshots when i clicked on Tools>Media in the Virtual Machine Manager.In Hard disks Window .In the end of the Snapshots Chain
Parent-------{ce66bbaf-8fd0-4bda-9c6e-0ba21a994a98}.vdi --   --         --
    Child----{45e4c283-80b1-46a0-aa17-a3b32edd995e}.vdi --   64.00GB    12.36GB
both are Virtual size and Actual Size, Parent is not showing any of them but child is showing both sizes.

As you are saying {ce6... is Corrupted Then why child is showing 12.36GB.
Last edited by anyways1 on 9. Nov 2019, 14:43, edited 2 times in total.
anyways1
Posts: 4
Joined: 3. Nov 2019, 01:40

Re: Error When i opened Virtual machine

Post by anyways1 »

i think no one wants to help .this is really very sad .
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Error When i opened Virtual machine

Post by scottgus1 »

anyways1 wrote:i think no one wants to can help
FTFY. The snapshot chain has to be complete from beginning to the end of the chain you're on. The link 'ce66bbaf.../vdi' has no data in it:
04/08/2019  05:15 PM                 0 {ce66bbaf-8fd0-4bda-9c6e-0ba21a994a98}.vdi
There should be data in it, even if it never was used and another snapshot was immediately made. I just made a snapshot of a shut-down guest. Even with no activity on that snapshot at all the file is still 2048kB size.
anyways1 wrote:As you are saying {ce6... is Corrupted Then why child is showing 12.36GB.
I see that parent/child structure in the .vbox file:
<HardDisk uuid="{baa2ca6f-f04b-484f-8d0c-196e54eec0f1}" location="security.vdi" format="VDI" type="Normal">
          <HardDisk uuid="{2bf80d16-8fcb-4f53-9d2a-056c1e30ef93}" location="Snapshots/{2bf80d16-8fcb-4f53-9d2a-056c1e30ef93}.vdi" format="VDI">
            <HardDisk uuid="{c92e2b08-f725-4a71-b7dd-7f9eb48505ed}" location="Snapshots/{c92e2b08-f725-4a71-b7dd-7f9eb48505ed}.vdi" format="VDI">
>            <HardDisk uuid="{ce66bbaf-8fd0-4bda-9c6e-0ba21a994a98}" location="Snapshots/{ce66bbaf-8fd0-4bda-9c6e-0ba21a994a98}.vdi" format="VDI">
>               <HardDisk uuid="{45e4c283-80b1-46a0-aa17-a3b32edd995e}" location="Snapshots/{45e4c283-80b1-46a0-aa17-a3b32edd995e}.vdi" format="VDI"/>
At one time the ce66bbaf snapshot file was good. It isn't anymore.

Interestingly, the .sav file of the same date is also 0 bytes. Something went very far south somewhere.

Your snapshot chain is broken, how it happened is anyone's guess. Snapshots are known to make the guest more delicate. This may have to do with using consumer-class PCs instead of server-class computers with tons of error-correction. Either way, snapshots should not be used on guests where data is important without having a non-snapshot-based reliable & restorable backup. Virtual machines should not be used where data is important without having a non-virtual-machine-based reliable & restorable backup. Computers should not be used where data is important without having a non-computer-based reliable & restorable backup. Paper should not be used where data is important without having another reliable & restorable backup. You see where this is going...

This is a hard cup of stiff black coffee to swallow, but your data is gone. We cannot get it back, unless you backed it up.

Socratis points out this as a solution that will at least get the guest running again:
Socratis wrote:Your only option is to delete "Snapshot 4" and remove it from the snapshot chain.
Data up to snapshot 3 should still be good.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Error When i opened Virtual machine

Post by socratis »

anyways1 wrote:i think no one wants to help .this is really very sad .
You're not the only one that needs help. The oldest tab that I have open and I would like to reply to (at some point) is from 2019-09-12, 00:25. Tell me about why you're complaining again? Even in that case, help has been given. Clear guidance:
socratis wrote:Your only option is to delete "Snapshot 4" and remove it from the snapshot chain.
anyways1 wrote:What about the data in VM ... I will be very thankful if you help me to recover its data
The Snapshot3 data is gone, unless you have a backup.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply