Page 1 of 1
VM INACCESSIBLE
Posted: 21. Apr 2021, 21:27
by WB2020
Hi,
When I tried to connect to my VM of windows Server 2019 today I got a forbiden icon and an "inaccssible statut". I can't launch my VM.
Cannot attach medium 'D:\WDS-19\VS2019\VS2019.vdi' {62756913-42c5-4f0e-a328-ef0a0d937870}: medium is already associated with the current state of machine uuid {0fe7e026-8bec-42b6-b1c8-e09b18f47a58}!.
Code d'erreur : VBOX_E_OBJECT_IN_USE (0x80BB000C)
Composant : MediumWrap
Interface : IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Any idea of what is going wrong ? there is no other VM launched at the same time.
Thank you in advance for your help..
Re: VM INACCESSIBLE
Posted: 21. Apr 2021, 21:44
by scottgus1
That error appears to mean that the vdi file is in use by another running VM or is part of another VM's snapshots.
First try rebooting your host then start the inaccessible VM.
If the host reboot doesn't work, we're going to need more info: Run the following commands in your host PC's Command Prompt, then post the text output:
CD "C:\Program Files\Oracle\Virtualbox"
vboxmanage showmediuminfo "D:\WDS-19\VS2019\VS2019.vdi"
Re: VM INACCESSIBLE
Posted: 22. Apr 2021, 17:24
by WB2020
Hi,
rebooting did not work
here is the text output:
C:\Program Files\Oracle\VirtualBox>vboxmanage showmediuminfo "D:\WDS-19\VS2019\VS2019.vdi"
UUID: 62756913-42c5-4f0e-a328-ef0a0d937870
Parent UUID: base
State: created
Type: normal (base)
Location: D:\WDS-19\VS2019\VS2019.vdi
Storage format: VDI
Format variant: dynamic default
Capacity: 51200 MBytes
Size on disk: 17580 MBytes
Encryption: disabled
Property: AllocationBlockSize=1048576
In use by VMs: (UUID: 0fe7e026-8bec-42b6-b1c8-e09b18f47a58)
Thank you in advance
Re: VM INACCESSIBLE
Posted: 22. Apr 2021, 17:31
by scottgus1
Thanks for the info. So the disk is attached to only one VM, the one with the UUID in the error message.
Can you please describe what this means?
WB2020 wrote:When I tried to connect to my VM
Does it mean "When I tried to start my VM"?
Please right-click the VM in the main Virtualbox window's VM list, choose "Show in Explorer/Finder/File Manager". In the window that opens, zip the VM's .vbox file, and post the zip file, using the forum's Upload Attachment tab. (If you have a Windows host, please make sure all file extensions are shown, so you will be able to see the .vbox extension easier.)
Re: VM INACCESSIBLE
Posted: 22. Apr 2021, 18:34
by WB2020
https://ibb.co/fH6jTQQ
I can't access to anything even file explorer as you can see in the img
Yes I meant when I try to start.
Find attached my .vbox file
Thank you for the help
Re: VM INACCESSIBLE
Posted: 22. Apr 2021, 20:13
by scottgus1
There is something odd in the VM, maybe. Here is the media registered in the VM:
<MediaRegistry>
<HardDisks>
<HardDisk uuid="{62756913-42c5-4f0e-a328-ef0a0d937870}" location="VS2019.vdi" format="VDI" type="Normal"/>
<HardDisk uuid="{0a8c975c-8123-461b-841f-62f24c46bed3}" location="VS2019_1.vdi" format="VDI" type="Normal"/>
<HardDisk uuid="{fcbe3a6c-258a-4c99-b0eb-96a32159d7d4}" location="VS2019_2.vdi" format="VDI" type="Normal"/>
</HardDisks>
<DVDImages>
<Image uuid="{ece3c713-56c2-476f-a36a-62c7330ecb9d}" location="D:/Downloads/17763.737.190906-2324.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_fr-fr_1.iso"/>
</DVDImages>
Here are the attached media files:
<StorageController name="SATA" type="AHCI" PortCount="5" useHostIOCache="false" Bootable="true" IDE0MasterEmulationPort="0" IDE0SlaveEmulationPort="1" IDE1MasterEmulationPort="2" IDE1SlaveEmulationPort="3">
<AttachedDevice type="HardDisk" hotpluggable="false" port="0" device="0">
<Image uuid="{62756913-42c5-4f0e-a328-ef0a0d937870}"/>
</AttachedDevice>
<AttachedDevice passthrough="false" type="DVD" hotpluggable="false" port="1" device="0">
<Image uuid="{ece3c713-56c2-476f-a36a-62c7330ecb9d}"/>
</AttachedDevice>
<AttachedDevice type="HardDisk" hotpluggable="false" port="2" device="0">
<Image uuid="{fcbe3a6c-258a-4c99-b0eb-96a32159d7d4}"/>
</AttachedDevice>
<AttachedDevice type="HardDisk" hotpluggable="false" port="3" device="0">
<Image uuid="{0a8c975c-8123-461b-841f-62f24c46bed3}"/>
</AttachedDevice>
<AttachedDevice type="HardDisk" hotpluggable="false" port="4" device="0">
<Image uuid="
{51ecd1d4-35fc-4ac7-9e13-1f6d85b8bae7}"/>
</AttachedDevice>
</StorageController>
The four media UUIDs match up to four of the attached devices. There is a fifth, the bottom disk, that is not mentioned in the Media section. What is that disk?
Re: VM INACCESSIBLE
Posted: 22. Apr 2021, 20:38
by WB2020
The last I guess is one I deleted from an other VM. But did that after It was already broken.
Re: VM INACCESSIBLE
Posted: 22. Apr 2021, 20:40
by scottgus1
OK. The VM think's it is still attached at this point. So go in and delete it, then try the VM again. If the VM does not boot, re-post the .vbox file.
Re: VM INACCESSIBLE
Posted: 23. Apr 2021, 10:55
by WB2020
Delete the lines on .vbox file worked. Thank you for helping me on this.
Re: VM INACCESSIBLE
Posted: 24. Apr 2021, 15:10
by scottgus1
Great! Glad you're up and running.