somehow the relation of snapshots is faulty a deleted snapshot is still in the list, see attachment.
I deleted Snapshot f4e29b17-f388-427b-8c4d-12da4670ec55 and its content was combined into the main disk grafanaServer-disk001.vmdk and the snapshot file {f4e29b17-f388-427b-8c4d-12da4670ec55}.vmdk was also deleted on disk.
I also checked the parentuuid settings in the vmdk files and this seems to be ok:
Code: Select all
uwe@uwe-HP-EliteBook-840-G1:~/VirtualBox VMs/Debian64$ vboxmanage internalcommands dumphdinfo grafanaServer-disk001.vmdk
--- Dumping VD Disk, Images=1
Dumping VD image "grafanaServer-disk001.vmdk" (Backend=VMDK)
Header: Geometry PCHS=16383/16/63 LCHS=1024/255/63 cbSector=131951680
Header: uuidCreation={97c0f820-b39d-405b-a774-ea1c6065e272}
Header: uuidModification={ca0e5df0-2901-41f0-8925-d165b4605dae}
Header: uuidParent={00000000-0000-0000-0000-000000000000}
Header: uuidParentModification={00000000-0000-0000-0000-000000000000}
uwe@uwe-HP-EliteBook-840-G1:~/VirtualBox VMs/Debian64$ ll Snapshots/
insgesamt 19559352
drwx------ 2 uwe uwe 4096 Feb 13 19:06 ./
drwx------ 4 uwe uwe 4096 Feb 13 19:41 ../
-rw------- 1 uwe uwe 6254624768 Feb 13 19:02 {1158baa2-d28c-4902-95e0-df5d6dfb1d4f}.vmdk
-rw------- 1 uwe uwe 7536508928 Feb 11 21:59 {6d101a84-bb53-4ae0-a311-0d7b47b2c9ba}.vmdk
uwe@uwe-HP-EliteBook-840-G1:~/VirtualBox VMs/Debian64$ vboxmanage internalcommands dumphdinfo Snapshots/\{1158baa2-d28c-4902-95e0-df5d6dfb1d4f\}.vmdk
--- Dumping VD Disk, Images=1
Dumping VD image "Snapshots/{1158baa2-d28c-4902-95e0-df5d6dfb1d4f}.vmdk" (Backend=VMDK)
Header: Geometry PCHS=16383/16/63 LCHS=1024/255/63 cbSector=131951680
Header: uuidCreation={1158baa2-d28c-4902-95e0-df5d6dfb1d4f}
Header: uuidModification={811c48ca-78e3-4d76-8a1a-2e8f5f12963a}
Header: uuidParent={97c0f820-b39d-405b-a774-ea1c6065e272}
Header: uuidParentModification={f608b982-649a-4ed7-aee6-0f1b23793df7}
uwe@uwe-HP-EliteBook-840-G1:~/VirtualBox VMs/Debian64$ vboxmanage internalcommands dumphdinfo Snapshots/\{6d101a84-bb53-4ae0-a311-0d7b47b2c9ba\}.vmdk
--- Dumping VD Disk, Images=1
Dumping VD image "Snapshots/{6d101a84-bb53-4ae0-a311-0d7b47b2c9ba}.vmdk" (Backend=VMDK)
Header: Geometry PCHS=16383/16/63 LCHS=1024/255/63 cbSector=131951680
Header: uuidCreation={6d101a84-bb53-4ae0-a311-0d7b47b2c9ba}
Header: uuidModification={ab94aa13-4d43-472c-a0bc-8a6ceb22adfc}
Header: uuidParent={1158baa2-d28c-4902-95e0-df5d6dfb1d4f}
Header: uuidParentModification={811c48ca-78e3-4d76-8a1a-2e8f5f12963a}
Code: Select all
<MediaRegistry>
<HardDisks>
<HardDisk uuid="{97c0f820-b39d-405b-a774-ea1c6065e272}" location="grafanaServer-disk001.vmdk" format="VMDK" type="Normal">
<HardDisk uuid="{f4e29b17-f388-427b-8c4d-12da4670ec55}" location="Snapshots/{f4e29b17-f388-427b-8c4d-12da4670ec55}.vmdk" format="VMDK">
<HardDisk uuid="{1158baa2-d28c-4902-95e0-df5d6dfb1d4f}" location="Snapshots/{1158baa2-d28c-4902-95e0-df5d6dfb1d4f}.vmdk" format="VMDK">
<HardDisk uuid="{6d101a84-bb53-4ae0-a311-0d7b47b2c9ba}" location="Snapshots/{6d101a84-bb53-4ae0-a311-0d7b47b2c9ba}.vmdk" format="VMDK"/>
</HardDisk>
</HardDisk>
</HardDisk>
</HardDisks>
</MediaRegistry>
And If I start the VM I get the error, that the {f4e29b17-f388-427b-8c4d-12da4670ec55}.vmdk file is missing.
So how can I delete the entry f4e29b17-f388-427b-8c4d-12da4670ec55 in the MediaRegistry?
Uwe