VM öffnet nicht

[Toolcontrol]

Hallo,
meine VM lässt sich nicht mehr öffnen - folgende Fehlermeldung:

Konnte die virtuelle Maschine in C:/VirtualBox/MSEdge - Win10/MSEdge - Win10.vbox nicht öffnen.

A differencing image of snapshot {8b52db44-b3a5-454f-af6a-093ee2de578d} could not be found. Could not find an open hard disk with UUID {b5b386b3-7ed1-432a-a643-ba99765344b9}.

Fehlercode:E_FAIL (0x80004005)
Komponente:SnapshotMachine
Interface:IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
Callee:IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}

Was kann ich tun?

Mein "MSEdge - Win10" Ordner enthält folgendes:
Ordner "Logs"
Ordner "Snapshots"
MSEdge - Win10.vbox - 25KB
MSEdge - Win10.vbox-prev - 26KB
MSEdge - Win10-disk002.vdi - 46.330.880KB

Meine VB: Version 6.0.4 r128413 (Qt5.6.2) + Ext.Pack

Host: (mein PC) 64bit + 16GB-RAM
Guest: vergessen

VBoxHardening.log (339KB) und VBox.log (162KB) sind leider zu groß zum hochladen.

Hilfe, nach etwa einem Jahr brauche ich die VM mal wieder dringend.
Vielen Dank
Jens

[mpack]

A differencing image of snapshot {8b52db44-b3a5-454f-af6a-093ee2de578d} could not be found. Could not find an open hard disk with UUID {b5b386b3-7ed1-432a-a643-ba99765344b9}.

The message says that a differencing file (snapshot segment or linked clone) is missing.

Did you delete some files on the host recently, or a complete VM? If so then you need to restore it from a backup.

[Toolcontrol]

Ja ich musste mal meinen PC aufräumen und dachte ich hätte alle Dateien gesichert - hab leider kein backup mehr

ich hab folgende Dateien:

MSEdge - Win10.vbox - 25KB
MSEdge - Win10.vbox-prev - 26KB
MSEdge - Win10-disk002.vdi - 46.330.880KB

Folder Snapshots:
{7fd315ce-bb16-4840-b39c-1dfb8a040fc4}.vdi
{87d2cee2-98bf-417d-a290-fe65160011a1}.vdi
2019-03-21T11-33-35-284334200Z.sav
2020-03-27T11-10-46-081533600Z.sav

Folder Logs:
VBox.log
VBox.log.1
VBox.log.2
VBox.log.3
VBoxHardening.log

Was fehlt? Kann man das irgendwie nachträglich erstellen?

[mpack]

If you zip and attach the ".vbox" file of the VM then we can look at the media list and see what it requires.

However you should prepare to be disappointed: if you deleted a necessary file and don't have any backups then you are in trouble. If this VM is a linked clone and you deleted the VM it was linked to and don't have backups then the linked clone is dead.

VMs that have unnecessary dependencies are prone to human errors such as this. That's why most experienced users will not employ either linked clones or snapshots.

[Toolcontrol]

Vielen Dank für Ihre Hilfe

[mpack]

Thanks for the .vbox file.

It looks like this VM does not register any media at all, which means it was 100% dependent on some other VM for base media. I.e. this looks like this started life as a linked clone, plus you seem to have created two additional snapshots {548d527b-ff71-45cb-b7e4-ead3f8b32bf5} and later {8b52db44-b3a5-454f-af6a-093ee2de578d}, the latter of which appears to be current.

The "{b5b386b3-xxxx} media seems to belong to the current snapshot. I'm puzzled as to why the matching vdi file does not appear in the Snapshots subfolder. If you can't replace this missing VDI from a backup then I would suggest that you first back up the VM folder, and then try reverting to the older snapshot state. If that works then I suggest that you clone the VM, current state only, to get rid of all of the snapshot dependencies from the clone.

Btw, ".sav" files are hibernation (saved state) files. We can live without those.

[fth0]

Code: Select all

Snapshot uuid                          Image uuid                             Image filename
-------------------------------------- -------------------------------------- ------------------------------------------ 
{8b52db44-b3a5-454f-af6a-093ee2de578d} {b5b386b3-7ed1-432a-a643-ba99765344b9} x.vdi
{548d527b-ff71-45cb-b7e4-ead3f8b32bf5} {87d2cee2-98bf-417d-a290-fe65160011a1} {87d2cee2-98bf-417d-a290-fe65160011a1}.vdi
Current State                          {7fd315ce-bb16-4840-b39c-1dfb8a040fc4} {7fd315ce-bb16-4840-b39c-1dfb8a040fc4}.vdi

I came to a slightly different conclusion, and I see two possibilities here:

1. The VM is not a linked clone: "x.vdi" would be "MSEdge - Win10.vdi" then, the file would be missing in the VM's folder, and the MediaRegistry section would be missing in the "MSEdge - Win10.vbox" file.

2. The VM is a linked clone: "x.vdi" would be "{b5b386b3-7ed1-432a-a643-ba99765344b9}.vdi" then, the file would be missing in the VM's Snapshot folder, and the MediaRegistry section would be located in the ".vbox" file of the parent VM.

In both cases, the first image of the VM ("x.vdi") is missing, and be needed for restoration. If you can restore the file, we could repair the "MSEdge - Win10.vbox" file by manually adding the missing MediaRegistry section.

---

PS: @mpack, the ordering of the snapshots is the opposite from what you assumed. If you're still puzzled, please don't hesitate to ask.