Snapshot Problem

[Muggsy14]

Hello everyone,
I encounter the following problem on one of my client VMs :

Failed to open the disk image file D:\Snapshots\{973662c6-5dc5-4e7e-9757-535a51240e5d}.vhd.

Could not open the medium 'D:\Snapshots\{973662c6-5dc5-4e7e-9757-535a51240e5d}.vhd'.

Failed to open image "D:\Snapshots\{973662c6-5dc5-4e7e-9757-535a51240e5d}.vhd" (VERR_SHARING_VIOLATION).

VD: error VERR_SHARING_VIOLATION repairing corrupted image file 'D:\Snapshots\{973662c6-5dc5-4e7e-9757-535a51240e5d}.vhd' (VERR_SHARING_VIOLATION).

Code d'erreur : E_FAIL (0x80004005)
Composant : MediumWrap
Interface : IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
Fonction appelée : IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
Code retourné : VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

For further information , a person who knew the product went into the Media Manager and release the Snapshot believer to restart the VM.
So I end up with my VHD file 100GB and 30GB my snapshot . How to merge so I found my functional VM
Thank you in advance for your answers


Regards,

[socratis]

With the VM shutdown, right-click on the VirtualBox Manager. Select Show log. Save the VBox.log, zip it and attach it to your response, please.

[mpack]

VirtualBox doesn't put a VM on drive D:\ (i.e. it would never write to a root folder). That means that "D:\Snapshots" is not a path that VirtualBox would use either. Perhaps it would be useful to know how the VM came to be using paths it can't have chosen by itself.

Guess: the VM was copied out of the original VM folder and onto the root folder of a removable drive, from where it was Added to another host. The drive is external and uses FAT32 so the inevitable corruption happened. If files have been corrupted then you can't repair them, you can only throw them away or restore from a backup.

You may also be attempting to view the VHD file using the host OS VHD reader, which would cause the sharing violation.

I would recommend copying the VM into a local folder before attempting repairs.

[Muggsy14]

Hello , Attached items requested
thanks again

[socratis]

OK, my bad, I should have also asked for the following:
- Right-click on the VM in the VirtualBox Manager.
- Select "Show in Explorer". That's the "TEHA.vbox" file, the settings of your VM.
- ZIP it and attach it in your response.

[Muggsy14]

Here it is

[mpack]

That does not appear to be the .vbox file for a VM which is using snapshots. It is not referencing anything in the Snapshots subfolder.

You seem to have cloned an XP VM and then replaced the VDI with a link to "D:/MmeCHATEL//Mes partitions_full_b1_s1_v1.vhd". Is that correct? If yes then where in the snapshot chain does this VHD appear?

You can try fixing this with CloneVDI. Copy all of the VHD files (base included) into a folder. The chain will go something like <base>+<snapshot1>+<snapshot2> etc. Open up each VHD and work out what the chain is (each snapshot contains a parent UUID link). If any VHD is corrupted then that and all the snapshot chain elements following it are lost. Clone the newest usable VHD to get a merged VDI.

[Muggsy14]

For information, I opened the "snapshot" file on my Windows 10 using Windows Disk Management .
This opens without problems .
I attached the screenshot
Thank you

[mpack]

Well, I don't do Windows support, but as I said earlier - that would explain the sharing violation.

[Muggsy14]

This means that I 'd do my virtual machine properly.
Is it possible to give me the command to be applied to restore the operation of the virtual machine?
My client asks me every day if the virtual machine is operational
Thank you in advance

[mpack]

There is no "command to be applied" - the only good way to recover a broken VM is from a backup copy. I gave you instructions earlier for how CloneVDI might be used to rescue the snapshot chain.

[Muggsy14]

I tried to clone the file with VDH VBoxManage CLONEMEDIUM and got the attached error.
So I turned to my VBoxManage INTERNALCOMMANDS command syntax but does not.
My VHD is on a drive E : \ VirtualBox \ TEHA
Can you help me with the syntax of the command
Thanks !!!!!!!!!

[mpack]

You can't use VBoxManage. VBoxManage is VirtualBox, and we've already established that the snapshot chain is broken as far as VirtualBox is concerned.

My suggestion was that you use CloneVDI. There is a download link and instructions in an earlier message of mine. CloneVDI is a GUI app, so I don't feel that I need to labor over the details of its use - it even has a French language option: just set or add "Language=3" in the ini file.