Page 1 of 1
W7 VM inaccessible VDI
Posted: 18. Oct 2020, 17:13
by shahesam
Hi,
Can someone please help me solving this issue that has happened due to the host restart:
Failed to open a session for the virtual machine Win7_test.
Could not open the medium 'E:\VirtualBox VMs\Win7_test\Win7_test\Win7_test.vdi'.
VDI: invalid pre-header in 'E:\VirtualBox VMs\Win7_test\Win7_test\Win7_test.vdi' (VERR_VD_VDI_INVALID_HEADER).
VD: error VERR_VD_VDI_INVALID_HEADER opening image file 'E:\VirtualBox VMs\Win7_test\Win7_test\Win7_test.vdi' (VERR_VD_VDI_INVALID_HEADER).
Result Code: E_FAIL (0x80004005)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
It is W7 VM (Version 6.1.14 r140239 (Qt5.6.2)) on a W10 host machine. The storage SATA port 0 says the .vdi file is Normal, Inaccessible. I can confirm that the .vdi file is accessible on my disk so it is not file permission problem. My other VM is working properly but this one crashes every time I start after the host last restart.
Here is the VBox.log:
Code: Select all
00:00:02.719390 Console: Machine state changed to 'Starting'
00:00:02.719563 Qt version: 5.6.2
00:00:02.721524 Console: Machine state changed to 'PoweredOff'
00:00:02.721886 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:02.854259 Power up failed (vrc=VINF_SUCCESS, rc=E_FAIL (0X80004005))
00:00:03.355010 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1278x966
00:00:03.355079 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:03.355291 GUI: Aborting startup due to power up progress issue detected...
Appreciate your help in advance.
Sam
Re: W7 VM inaccessible VDI
Posted: 18. Oct 2020, 23:14
by scottgus1
Try Mpack's
CloneVDI on the guest VDI file. If it's fixable, CloneVDI will fix it. If not you'll need to rely on your backups.
Re: W7 VM inaccessible VDI
Posted: 18. Oct 2020, 23:52
by shahesam
scottgus1 wrote:Try Mpack's CloneVDI on the guest VDI file. If it's fixable, CloneVDI will fix it. If not you'll need to rely on your backups.
Thanks for this but it didn't help. I can't open the new cloned .vdi file as storage for this VM. How can I check if there is any backup and where to find them?
Re: W7 VM inaccessible VDI
Posted: 18. Oct 2020, 23:56
by scottgus1
Folks need to manually set up their own backup routine with host OS or 3rd-party software. If you don't know where the backups are you don't have any.
shahesam wrote:I can't open the new cloned .vdi file as storage for this VM.
Are you getting any errors?
Re: W7 VM inaccessible VDI
Posted: 19. Oct 2020, 04:39
by shahesam
scottgus1 wrote:Folks need to manually set up their own backup routine with host OS or 3rd-party software. If you don't know where the backups are you don't have any.
shahesam wrote:I can't open the new cloned .vdi file as storage for this VM.
Are you getting any errors?
Thanks a lot. I was able to make it work. Just removed the previous version from Virtual Media Manager and add the new one. Now the VM works again
.
Re: W7 VM inaccessible VDI
Posted: 19. Oct 2020, 16:50
by scottgus1
shahesam wrote:removed the previous version from Virtual Media Manager and add the new one.
I'm going to guess this means the previous version of the drive file and the clone from CloneVDI.
This kind of issue can happen if both drive files have the same UUID. Virtualbox wont let multiple drive files with the same UUID exist in its database, even if the drive files have different names. CloneVDI has an option to change the drive UUID, which allows both drives to be in Virtualbox, but can also upset in-the-guest things like grub. Your solution was the way to handle it if two drives have the same UUID: remove the old, attach the new.
Glad you're up and running!
Re: W7 VM inaccessible VDI
Posted: 20. Oct 2020, 00:09
by shahesam
scottgus1 wrote:shahesam wrote:removed the previous version from Virtual Media Manager and add the new one.
I'm going to guess this means the previous version of the drive file and the clone from CloneVDI.
This kind of issue can happen if both drive files have the same UUID. Virtualbox wont let multiple drive files with the same UUID exist in its database, even if the drive files have different names. CloneVDI has an option to change the drive UUID, which allows both drives to be in Virtualbox, but can also upset in-the-guest things like grub. Your solution was the way to handle it if two drives have the same UUID: remove the old, attach the new.
Glad you're up and running!
Exactly. This time I created the new vdi file with new UUID. maybe that did the trick.
Thanks again