VirtualBox VM doesn't restart after blackout

[manuelmagic]

I can't make my VirtualBox VM manually restart after a blackout (it was running before the power went off).

This is the error I get:

Code: Select all

vbox@chebasti:~/VirtualBox VMs/DockerRegistry$ VBoxHeadless --startvm "DockerRegistry" -e "TCP/Ports=4444"
Oracle VM VirtualBox Headless Interface 4.0.4
(C) 2008-2011 Oracle Corporation
All rights reserved.
    
Error: failed to start machine. Error message: UUID {20afee16-bf06-43c4-ab02-770106ce3498} of the medium '/home/vbox/VirtualBox VMs/DockerRegistry/ubuntu-14.04-server-amd64-disk1.vdi' does not match the value {4c6a8bcb-3766-4581-9f45-0de031c65c95} stored in the media registry ('/home/vbox/.VirtualBox/VirtualBox.xml')

I already tried to search the error online and tried to follow different instructions but none worked.

You can find the output of VBoxManage showvminfo DockerRegistry --details in the attached file.

The output of VBoxManage showhdinfo ubuntu-14.04-server-amd64-disk1.vdi is:

Code: Select all

vbox@chebasti:~/VirtualBox VMs/DockerRegistry$ VBoxManage showhdinfo ubuntu-14.04-server-amd64-disk1.vdi
UUID:                 4c6a8bcb-3766-4581-9f45-0de031c65c95
Accessible:           no
Access Error:         UUID {20afee16-bf06-43c4-ab02-770106ce3498} of the medium '/home/vbox/VirtualBox VMs/DockerRegistry/ubuntu-14.04-server-amd64-disk1.vdi' does not match the value {4c6a8bcb-3766-4581-9f45-0de031c65c95} stored in the media registry ('/home/vbox/.VirtualBox/VirtualBox.xml')
Logical size:         0 MBytes
Current size on disk: 0 MBytes
Type:                 normal (base)
Storage format:       VDI
Format variant:       dynamic default
In use by VMs:        DockerRegistry (UUID: 952200e9-db58-420a-8fe1-ef49523def3d)
Location:             /home/vbox/VirtualBox VMs/DockerRegistry/ubuntu-14.04-server-amd64-disk1.vdi

I don't know if it is of any use but here you are the output of VBoxManage showhdinfo \{4d495022-b596-47c0-8f38-f16c6c5d7f63\}.vdi:

Code: Select all

vbox@chebasti:~/VirtualBox VMs/DockerRegistry/Snapshots$ VBoxManage showhdinfo \{4d495022-b596-47c0-8f38-f16c6c5d7f63\}.vdi 
UUID:                 4d495022-b596-47c0-8f38-f16c6c5d7f63
Accessible:           yes
Logical size:         0 MBytes
Current size on disk: 564 MBytes
Type:                 normal (differencing)
Storage format:       VDI
Format variant:       differencing default
In use by VMs:        DockerRegistry (UUID: 952200e9-db58-420a-8fe1-ef49523def3d)
Location:             /home/vbox/VirtualBox VMs/DockerRegistry/Snapshots/{4d495022-b596-47c0-8f38-f16c6c5d7f63}.vdi
Auto-Reset:           off

[mpack]

Even a new user can add picture or zip attachments directly to these topics. There's no need for the offsite obfuscated URL tomfoolery.

Please provide a complete VM log file. See Minimum information needed for assistance.

And how old is this VM? It's been years since VirtualBox stopped storing media registration details in VirtualBox.xml.

[manuelmagic]

Thank you for your reply.

Even a new user can add picture or zip attachments directly to these topics. There's no need for the offsite obfuscated address tomfoolery.

Sorry, I didn't thought about attachment, my fault. As soon I end writing this post I'll change the original one.

Please provide a complete VM log file. See Minimum information needed for assistance.

Ok

And how old is this VM? It's been years since VirtualBox stopped storing media registration details in VirtualBox.xml.

The VM is quite new (2 weeks), but the OS and the Virtual Box in use are quite old (they are not under my control).

Code: Select all

vbox@chebasti:~$ uname -a
Linux chebasti 2.6.26-2-amd64 #1 SMP Sun Mar 4 21:48:06 UTC 2012 x86_64 GNU/Linux

vbox@chebasti:~$ VBoxManage --version
4.0.4r70112

The guest OS is Ubuntu 14.04 LTS server 64 bit (no GUI), with no guest additions installed.

I hope this is the correct log file as explained in your link:

Code: Select all

vbox@chebasti:~/VirtualBox VMs/DockerRegistry/Logs$ cat VBox.log
00:00:00.011 VirtualBox 4.0.4 r70112 linux.amd64 (Feb 17 2011 18:05:57) release log
00:00:00.011 Log opened 2014-08-11T09:35:43.762281000Z
00:00:00.011 OS Product: Linux
00:00:00.011 OS Release: 2.6.26-2-amd64
00:00:00.011 OS Version: #1 SMP Sun Mar 4 21:48:06 UTC 2012
00:00:00.011 DMI Product Name: S3210SH
00:00:00.011 DMI Product Version: 
00:00:00.012 Host RAM: 8004MB RAM, available: 6532MB
00:00:00.012 Executable: /usr/lib/virtualbox/VBoxHeadless
00:00:00.012 Process ID: 9932
00:00:00.012 Package type: LINUX_64BITS_DEBIAN_5_0
00:00:00.035 Power up failed (vrc=VINF_SUCCESS, rc=NS_ERROR_FAILURE (0X80004005))

[mpack]

A dozen or so lines? If that really is the log then there is nothing I can tell from that.

I would check if the VM files are intact.

Afterthought: VBox seems to be quite confused about file IDs. Have you omitted any part of this story, e.g. have you been cloning or copying files?

[manuelmagic]

A dozen or so lines? If that really is the log then there is nothing I can tell from that.

Sorry, but that's it

I would check if the VM files are intact.

How do I do that?

Afterthought: VBox seems to be quite confused about file IDs. Have you omitted any part of this story, e.g. have you been cloning or copying files?

All I did was:
- download the guest image
- convert it from .vmdk to .vdi (so I could then change the size form 20 GB to 250 GB)
- use it (I did a snapshot when I finished setting up)

The VM was working well before the power sourge, I restared it a few times in order to check if a software inside was working well at restart.

There seems to be a problem with the hdd image, as you can see from the output of VBoxManage showhdinfo ubuntu-14.04-server-amd64-disk1.vdi in the first post.

There is no way to fix that?

[loukingjr]

Not that this helps any, but in the five years I've been using VB that happened to me once. A power outage while the guest was open. Never did find a way to fix it.

[mpack]

Well, the error message is referring to a problem in VirtualBox.xml, so how about you zip that up and post it?

[manuelmagic]

Well, the error message is referring to a problem in VirtualBox.xml, so how about you zip that up and post it?

Here you are!

[manuelmagic]

Not that this helps any, but in the five years I've been using VB that happened to me once. A power outage while the guest was open. Never did find a way to fix it.

Thanks for the feedback

[mpack]

Well, the error message is referring to a problem in VirtualBox.xml, so how about you zip that up and post it?

Here you are!

If that is the correct VirtualBox.xml then it doesn't have a media registry, so (a) there can't be a conflict there, (b) the error message can't be 100% accurate.

What I suspect is that the error (with legacy wording) really refers to the memory copy of the media registry - which since v4 is now an amalgam of all the local (.vbox) media registries - contains conflicting entries, perhaps two disk image files with the same name and different UUIDs. I believe it doesn't like that.

[manuelmagic]

Not that this helps any, but in the five years I've been using VB that happened to me once. A power outage while the guest was open. Never did find a way to fix it.

I gave up too and reinstalled the machine.

Thanks to everybody for the help!

[derleek]

Not that this helps any, but in the five years I've been using VB that happened to me once. A power outage while the guest was open. Never did find a way to fix it.

I try not to necro threads, but i think this one is very relevant....

My host crashed really hard (I dont think it had to do with vbox), which probably has the same consequences as a blackout. I am getting this error on the VM that was running but all of my others are just fine. I'd be happy to upload/debug this from the vbox side.

It appears the actual hard disk got corrupted somehow, which is not that hard to believe in a hard-reboot scenario.

Environment:

OSX: 10.10.1
Virtualbox: 5.0.14 r105127

[Perryg]

I try not to necro threads, but i think this one is very relevant....

My host crashed really hard (I dont think it had to do with vbox), which probably has the same consequences as a blackout. I am getting this error on the VM that was running but all of my others are just fine. I'd be happy to upload/debug this from the vbox side.

It appears the actual hard disk got corrupted somehow, which is not that hard to believe in a hard-reboot scenario.

Environment:

OSX: 10.10.1
Virtualbox: 5.0.14 r105127

9 times out of 10 it is the *.vbox file that has been corrupted and simply replacing it with the *.vbox-prev fixes the issue.