parent UUID of the medium does not match

Allgemeine Diskussionen über den Einsatz von VirtualBox.
VM-F4n
Posts: 181
Joined: 25. Oct 2015, 12:53
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Win7 64-Bit

Re: parent UUID of the medium does not match

Post by VM-F4n »

@MarkFalk
Du hast es also geschafft indem du die parent UUID gesetzt hast?! :)
Das macht Mut. :wink:

Kannst du deine genaue Vorgehensweise schildern?

Ich hab' zuerst

Code: Select all

vboxmanage internalcommands dumphdinfo "path to the base.vdi"
eingegeben und bekomme dann ja die Info (siehe unten).

Wie aber nun weiter?
Diese .vdi ist ja meine Basis-vdi (klar, dass sie keine PartenUUID haben kann, sie ist ja selber "parent" :wink: ).

Wenn ich den Befehl erweitere, auf beide Snapshots, dann sieht das folgendermaßen aus:
C:\Program Files\Oracle\VirtualBox>vboxmanage internalcommands dumphdinfo "path to the base.vdi"
--- Dumping VD Disk, Images=1
Dumping VD image "path to the base.vdi" (Backend=VDI)
Dumping VDI image "path to the base.vdi" mode=r/o uOpenFlags=9 File=0x00000000c37910
Header: Version=00010001 Type=1 Flags=0 Size=214748364800
Header: cbBlock=1048576 cbBlockExtra=0 cBlocks=204800 cBlocksAllocated=204728
Header: offBlocks=1048576 offData=2097152
Header: Geometry: C/H/S=1024/255/63 cbSector=512
Header: uuidCreation={847217ee-b549-4ae5-b0ef-ba9491afbe28}
Header: uuidModification={6c5fb456-9058-4d58-bed3-e91f67fd76fa}
Header: uuidParent={00000000-0000-0000-0000-000000000000}
Header: uuidParentModification={00000000-0000-0000-0000-000000000000}
Image: fFlags=00000000 offStartBlocks=1048576 offStartData=2097152
Image: uBlockMask=000FFFFF cbTotalBlockData=1048576 uShiftOffset2Index=20 offStartBlockData=0

Vorletzter Snapshot (Snapshot der zuerst erstellt wurde):
C:\Program Files\Oracle\VirtualBox>vboxmanage internalcommands dumphdinfo "path to the base\Snapshots\{594b0bd7-6302-4b7d-ae0d-46ebb2b5e916}.vdi"
--- Dumping VD Disk, Images=1
Dumping VD image "path to the base\Snapshots\{594b0bd7-6302-4b7d-ae0d-46ebb2b5e916}.vdi" (Backend=VDI)
Dumping VDI image "path to the base\Snapshots\{594b0bd7-6302-4b7d-ae0d-46ebb2b5e916}.vdi" mode=r/o uOpenFlags=9 File=0x00000000ed7af0
Header: Version=00010001 Type=4 Flags=0 Size=214748364800
Header: cbBlock=1048576 cbBlockExtra=0 cBlocks=204800 cBlocksAllocated=11180
Header: offBlocks=1048576 offData=2097152
Header: Geometry: C/H/S=1024/255/63 cbSector=512
Header: uuidCreation={594b0bd7-6302-4b7d-ae0d-46ebb2b5e916}
Header: uuidModification={110c5558-5df8-43f2-9fd1-c18b2406d160}
Header: uuidParent={3e387847-42d4-4b19-bffe-33e73f856e89}
Header: uuidParentModification={8129f66e-98da-4cf3-b7d2-158056598752}
Image: fFlags=00020000 offStartBlocks=1048576 offStartData=2097152
Image: uBlockMask=000FFFFF cbTotalBlockData=1048576 uShiftOffset2Index=20 offStartBlockData=0

Letzter Snapshot (Snapshot der als letzter erstellt wurde):
C:\Program Files\Oracle\VirtualBox>vboxmanage internalcommands dumphdinfo "path to the base\Snapshots\{45f64ae1-5df4-4065-97c3-e0655c6f33e7}.vdi"
--- Dumping VD Disk, Images=1
Dumping VD image "path to the base\Snapshots\{45f64ae1-5df4-4065-97c3-e0655c6f33e7}.vdi" (Backend=VDI)
Dumping VDI image "path to the base\Snapshots\{45f64ae1-5df4-4065-97c3-e0655c6f33e7}.vdi" mode=r/o uOpenFlags=9 File=0x00000000e77cd0
Header: Version=00010001 Type=4 Flags=0 Size=214748364800
Header: cbBlock=1048576 cbBlockExtra=0 cBlocks=204800 cBlocksAllocated=52059
Header: offBlocks=1048576 offData=2097152
Header: Geometry: C/H/S=1024/255/63 cbSector=512
Header: uuidCreation={45f64ae1-5df4-4065-97c3-e0655c6f33e7}
Header: uuidModification={eb234163-1fbd-4625-8561-3c23aa5bc018}
Header: uuidParent={594b0bd7-6302-4b7d-ae0d-46ebb2b5e916}
Header: uuidParentModification={110c5558-5df8-43f2-9fd1-c18b2406d160}
Image: fFlags=00020000 offStartBlocks=1048576 offStartData=2097152
Image: uBlockMask=000FFFFF cbTotalBlockData=1048576 uShiftOffset2Index=20 offStartBlockData=0

C:\Program Files\Oracle\VirtualBox>
Edit:
Kann es so einfach sein?

Fehlt hier nicht ein </HardDisk> ?

Code: Select all

<HardDisks>
        <HardDisk uuid="{847217ee-b549-4ae5-b0ef-ba9491afbe28}" location="path to base.vdi" format="VDI" type="Normal">
          <HardDisk uuid="{594b0bd7-6302-4b7d-ae0d-46ebb2b5e916}" location="Snapshots/{594b0bd7-6302-4b7d-ae0d-46ebb2b5e916}.vdi" format="VDI">
            <HardDisk uuid="{45f64ae1-5df4-4065-97c3-e0655c6f33e7}" location="Snapshots/{45f64ae1-5df4-4065-97c3-e0655c6f33e7}.vdi" format="VDI"/>
          </HardDisk>
        </HardDisk>
      </HardDisks>

Ich sehe 3 geöffnete <HardDisk> aber nur 2 geschlossene </HardDisk>.[/s]

Edit:
Hat nichts geholfen (VM lässt sich nicht per .vbox Datei "einbinden", sondern bringt eine erneute - anderweitige :roll: - Fehlermeldung sobald man ein </HardDisk> manuell einfügt), deshalb gestrichen.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: parent UUID of the medium does not match

Post by fth0 »

Bzgl. des XML-Formates hast Du vermutlich den "/" im innersten "<Harddisk ... />" übersehen, der dieses bereits abschließt.

Bzgl. der VDIs fehlt Dir (mindestens) das VDI mit der UUID {3e38...}. Wenn Du uuidParent im "vorletzten Snapshot" anpasst, wird VirtualBox vermutlich nicht mehr meckern. Aber es sollte klar sein, dass dadurch in der Regel kein benutzbares Dateisystem für den Gast entsteht, da wahrscheinlich nicht nur die Dateien, sondern auch die Verzeichnisse korrupt sind. D.h., Du kannst das Ergebnis dann als zweite Festplatte in eine VM einbinden und retten, was zu retten ist.
Last edited by fth0 on 23. Mar 2021, 18:39, edited 1 time in total.
VM-F4n
Posts: 181
Joined: 25. Oct 2015, 12:53
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Win7 64-Bit

Re: parent UUID of the medium does not match

Post by VM-F4n »

Wenn ich es nur hinbekomme, dass die VM wieder starten würde (oder Tricks), dann könnte ich mit CloneVDI ja probieren aus dem letzten Snapshot eine neue .vdi zu erstellen (was es so eben nicht macht).
Was schlägst du vor, wie ich jetzt vorgehen soll?
Ich hab' nur die 2 Snapshots, keinen mit der UUID {3e38...}.

Edit:
3e28 3e38
Last edited by VM-F4n on 23. Mar 2021, 16:21, edited 1 time in total.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: parent UUID of the medium does not match

Post by mpack »

You don't need to run a VM in order to fix up the links and clone the disk using CloneVDI. I gave you instructions already in the CloneVDI topic, you never commented on them.
VM-F4n
Posts: 181
Joined: 25. Oct 2015, 12:53
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Win7 64-Bit

Re: parent UUID of the medium does not match

Post by VM-F4n »

@mpack
Thanks, now after your help i tracked backwards... see:
viewtopic.php?f=6&t=22422&p=496689#p496689

Ok, i think, if i want to use this VM i only could use the base .vdi, because all in the snapshots are "lost" because of the missing snapshot chain (no problem, because of 2 points, 1. i've a new vm installed with win10 instead of win7 and 2. after i run the vm with the "trick" i've saved my missing files.)

Nevertheless I would want to try to rewrite the uuids :oops: (only for testing).
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: parent UUID of the medium does not match

Post by mpack »

Ok, I had a closer look, and I agree that you are missing at least one snapshot, the newest of which would have UUID {3e38 xxx}.

So, you can try linking snapshot {5954 xxx} to the base VDI. To do that you would navigate to the folder containing the VDIs and enter the command (I assume you already have backups):

Code: Select all

VBoxManage internalcommands sethdparentuuid "{594b0bd7-6302-4b7d-ae0d-46ebb2b5e916}.vdi" "{847217ee-b549-4ae5-b0ef-ba9491afbe28}"
This should fix up the broken link and you can then create a merged VDI using CloneVDI by cloning the newest snapshot ({45f64ae1-5df4-4065-97c3-e0655c6f33e7}.vdi) as previously discussed. Also as previously discussed, there is no guarantee that this merged disk will actually be useable. Heavy corruption is likely, since we didn't restore the missing data (including filesystem structures), we only prevented the host tools from detecting that data is missing.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: parent UUID of the medium does not match

Post by mpack »

MarkFalk wrote:
scottgus1 wrote:CloneVDI also never changes the original files
Are you sure?
Very sure.
MarkFalk wrote: There are existing 2 programms called CloneVDI:
https://www.freeware.de/download/clonevdi/
and
viewtopic.php?t=22422

I assume we are talking about the second one.
Yes to the latter assumption. In fact the "freeware.de" tool called CloneVDI existed before my tool, but I was unaware of it at the time because it was only discussed on German speaking forums, and online translation did not exist at the time. I became aware of CloneVDI-GUI some time after my CloneVDI was released. Since CloneVDI-GUI didn't seem to be very well known I decided not to worry about it. The word "clonevdi" itself originated in VBoxManage - Ostoturn did not invent it (it was the original form of the command now documented as "clonemedium").

The "freeware.de" tool is not equivalent to my CloneVDI, it is only a GUI wrapper around VBoxManage and hence can provide no feature unless VBoxManage provides it first. If VBoxManage fails on a particular VDI then the freeware.de GUI will also fail. Since modern VirtualBox has it's own GUI now I would assume that the "freeware.de" tool is defunct.
But it clones .VDI only - means: It accepts as input also .vhd, but it generates .vdi only, doesn´t matter the given extension.
Absolutely. CloneVDI will only ever output the VirtualBox native format: I don't believe in adding placebo features. CloneVDI is specifically intended to be a VirtualBox support tool - I have no interest in supporting other VM platforms.
On the other hand - when a files get damaged it doesn´t matter if it is one single VM-file or one of a dozend files of a VM.
It matters a great deal. A single file (i.e. with no dependencies) is much easier to backup, restore - and most importantly - to repair.
VM-F4n
Posts: 181
Joined: 25. Oct 2015, 12:53
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Win7 64-Bit

Re: parent UUID of the medium does not match

Post by VM-F4n »

@mpack
Thanks! :)
My "only backup" is in this thread, see the text (with all UUID's) above. :wink:

Edit:
Für alle die es evtl. irgenwann mal benötigen können... der richtige Befehl:

Code: Select all

VBoxManage internalcommands sethdparentuuid "complete-path-to-{594b0bd7-6302-4b7d-ae0d-46ebb2b5e916}.vdi" "{847217ee-b549-4ae5-b0ef-ba9491afbe28}"
Starten/Testen der VM kann ich ggf. später noch oder ggf. auch erst morgen.
Ich werde hier den Ausgang berichten. :wink:
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: parent UUID of the medium does not match

Post by mpack »

Do not attempt to start the VM before creating the clone VDI as described.

Also, my instructions did say to "navigate to the folder containing the VDIs", in which case it will not have been necessary to add a path to the first filename.
VM-F4n
Posts: 181
Joined: 25. Oct 2015, 12:53
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Win7 64-Bit

Re: parent UUID of the medium does not match

Post by VM-F4n »

Also, die mit CloneVDI neu erstellte VM (aus dem letzten Snapshot) lässt sich starten und hat auch alle Dateien. :D
Ich hab' jetzt allerdings nicht alles ausführlich getestet... kann ich ggf. bei Gelegenheit aber noch tun.
Auf alle Fälle hat das Umschreiben der UUID parent und die Verwendung von CloneVDI der VM wohl nicht geschadet. :wink:
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: parent UUID of the medium does not match

Post by mpack »

Well, do make sure that you REALLY have all the files, and not only the correct file names but filled with garbage.

Though in fact even if that were the case, it's still the best you can do. Now would be a good time to copy vital files outside of the VM, because if the filesystem is corrupted then it could still destroy itself in the end. You should also be doing disk checks after copying out those vital files.
VM-F4n
Posts: 181
Joined: 25. Oct 2015, 12:53
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Win7 64-Bit

Re: parent UUID of the medium does not match

Post by VM-F4n »

@mpack
It looks like all files are good. :)
Why should i do a disk check?
The file system of the SSD (where the vm files are) is not the system with the (old) HDD with bad sectors.
This SSD is only a few month old!
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: parent UUID of the medium does not match

Post by mpack »

This has nothing to do with the host drive any longer. You need to check the filesystem INSIDE THE GUEST.

The procedure you followed has almost certainly destroyed part of the guest drive, you would be incredibly lucky if every sector lost in the missing snapshot had been replaced in the later one.

This can lead to errors such as the same file sectors being allocated to two files, or files being stored in sectors that the $BITMAP mft file says are not yet allocated. Less harmfully, the file table may address files that contain garbage. Using a suspect drive without checking it could eventually lead to catastrophic data loss.

So do a disk filesystem check inside the guest. I don't know why you would even query the need for this: if your drive has nothing wrong then the check will confirm it.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: parent UUID of the medium does not match

Post by mpack »

One additional thought, since it has been bugging me: you mention that the "new VM created by CloneVDI" is now working. In fact CloneVDI does not create VMs, it creates VDI copies of hard disk images. Of course you could simply mean a VM you created using the VDI created by CloneVDI, and I hope that is what you do mean. Plus I'm receiving this through online translation, which is never completely reliable when translating technical discussion.

Anyway, the cloned VDI needs to be added to a VM in order to be useful... and I'm hoping that you did in fact create a new VM for this, and did not simply plug this stand-alone VDI into a VM that expects snapshots. This would not be immediately fatal, but it does waste disk space and it will cause confusion if you later attempt to manipulate the apparant snapshots in the VM.
VM-F4n
Posts: 181
Joined: 25. Oct 2015, 12:53
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Win7 64-Bit

Re: parent UUID of the medium does not match

Post by VM-F4n »

@mpack
I use this VM (with a new uuid) which is created by CloneVDI - from the last snapshot - as a standalone VM and i never will use snapshots again (not in this VM and not in another one).
This VM will not be used as a productive system again.
There is a new VM with another OS for productive system.

The old VM (with the snapshots) will not be "touched" again.
Post Reply