Restore VM

[dashwind]

Hello, I have a complex problem with VirtualBox. I took a photo and it took forever to load. I set the other picture to be deleted because... ran out of space. Then the program froze and I completed it urgently. After that, my pictures were not launched or deleted because it said that the disk was occupied by the process. Apparently it was a messy last picture, only 4 MB in size. I decided to try to remove it. But it couldn’t be deleted through the regular menu, so I deleted it through Media Manager. This was the last photo. In general... after that VirtualBox began to write that the virtual machine has a different children's disk.

In general, I think that the vbox file needs to be edited correctly. I tried, but I get errors, like there’s an extra space, or something else. Please advise how to edit the document correctly to restore access to the virtual machine.

I also tried to make a clone of the last image via CloneVDI, but I got the error “app attend to seek beyond end of drive”.

When I was looking for a solution to this problem on this forum, I learned that snapshots make the system extremely vulnerable. Tell me how to save the system - what to copy? Save the state and turn off the virtual machine, then copy the file itself, which is not in the snapshots folder?
And if there is already a system with snapshots, there is no way to make it invulnerable without snapshots?

[scottgus1]

Please zip the .vbox file and post it in one zip file.

Please relate the exact error messages you're getting.

Also, did your VM's hard disk completely fill up? Or the host disk?

[dashwind]

Okay, I hope this helps. Also I changed hard disk for this VM to allow VDI CLone have a lot of free space. Now if I want to add this machine from new location it writes "impossible to open the VM"

[dashwind]

Here is another info.

[scottgus1]

<HardDisks>
<HardDisk uuid="{d17ebf78-1bf1-4456-90cb-67af93ab6d7e}" location="Linux Mint --- INFO-disk1.vdi" format="VDI" type="Normal">
<HardDisk uuid="{eb66c6ef-59de-4cbb-8ea0-7d7070b3c737}" location="Snapshots/{eb66c6ef-59de-4cbb-8ea0-7d7070b3c737}.vdi" format="VDI">
<HardDisk uuid="{ac1bb57f-d0af-42a5-bcd9-7e4410b2fd59}" location="Snapshots/{ac1bb57f-d0af-42a5-bcd9-7e4410b2fd59}.vdi" format="VDI">
<HardDisk uuid="{c41de5e2-70d7-45cf-978d-e8cba3165472}" location="Snapshots/{c41de5e2-70d7-45cf-978d-e8cba3165472}.vdi" format="VDI">
<HardDisk uuid="{c5aabe37-d7b0-40e4-9f53-fb1bc7dbb936}" location="Snapshots/{c5aabe37-d7b0-40e4-9f53-fb1bc7dbb936}.vdi" format="VDI">
<HardDisk uuid="{9523473c-30d5-403d-b256-cc3a2ba0e1f5}" location="Snapshots/{9523473c-30d5-403d-b256-cc3a2ba0e1f5}.vdi" format="VDI">
<HardDisk uuid="{781d83da-ad0b-492e-abf5-c5fc06df2b7f}" location="Snapshots/{781d83da-ad0b-492e-abf5-c5fc06df2b7f}.vdi" format="VDI">
<HardDisk uuid="{70b6a008-550c-470f-b6fc-ee796f22d57b}" location="Snapshots/{70b6a008-550c-470f-b6fc-ee796f22d57b}.vdi" format="VDI">
<HardDisk uuid="{04fd4b1f-1d52-4061-bb7d-4ee1305bc704}" location="Snapshots/{04fd4b1f-1d52-4061-bb7d-4ee1305bc704}.vdi" format="VDI">
<HardDisk uuid="{ab084613-fe2c-439e-9a91-206b15f75600}" location="Snapshots/{ab084613-fe2c-439e-9a91-206b15f75600}.vdi" format="VDI">
<HardDisk uuid="{7e41e1f8-2ace-4c3a-8b19-062d436b05ab}" location="Snapshots/{7e41e1f8-2ace-4c3a-8b19-062d436b05ab}.vdi" format="VDI">
<HardDisk uuid="{4453ee3f-ee86-4a5f-b6a0-85f6d5e401ad}" location="Snapshots/{4453ee3f-ee86-4a5f-b6a0-85f6d5e401ad}.vdi" format="VDI"/>
<HardDisk uuid="{abee221f-5a8f-4be8-ab2b-0e59e220bfbd}" location="Snapshots/{abee221f-5a8f-4be8-ab2b-0e59e220bfbd}.vdi" format="VDI">
<HardDisk uuid="{aa612408-0a3f-45cb-a3b5-3be9bb9299e2}" location="Snapshots/{aa612408-0a3f-45cb-a3b5-3be9bb9299e2}.vdi" format="VDI"/>
</HardDisk>
</HardDisk>
</HardDisk>
</HardDisk>
</HardDisk>
</HardDisk>
</HardDisk>
</HardDisk>
</HardDisk>
</HardDisk>
</HardDisk>
</HardDisk>
</HardDisks>

That's a lot of snapshots!

The one that's causing the trouble is the "abee..." snapshot disk in bold underlined red. It seems to be parallel with the "4453..." UUID disk above it.

If you don't need this house of cards stack of snapshots, you could try CloneVDI's snapshot cloning feature to clone either the "4453..." or the last "aa61..." snapshot disk.

Per CloneVDI's instructions you have to set up a new VM using the same hardware settings as the snapshot had set up, and use the clone as the disk for the new VM. This setup will get the cloned VM running without this:

if I want to add this machine from new location it writes "impossible to open the VM"

FWIW "impossible to open the VM" is not the complete error message. You really need to give the whole error message when you get an error, instead of summarizing the error message. We can't know what to do with summaries; lots of diagnostic data gets lost.