VERR_VD_VDI_INVALID_HEADER

[Vlczech]

Hello, VERR_VD_VDI_INVALID_HEADER occurs on my VDI image. How can I repair it? I tried CloneVDI (by @mpack ) also, but there occurs error "Source file is not a recognized VDI file format" Thank you very much

[scottgus1]

If CloneVDI can't fix it, it ain't fixable. Could be that more was damaged than just the header. Only way to continue is by restoring from your backups.

[itsme300]

I had the same issue where clonevdi failed to repair. But mpack's manual solution fixed it.

Edit: Sorry, I would not like to spread my misunderstanding. Please follow expert's suggestions.

viewtopic.php?f=6&t=100256

[mpack]

CloneVDI simply implements my manual method in code, so there's no way the "manual method" works when CloneVDI doesn't. Also, the manual method has to be tailored to each case, there's no way it works for anyone other than the original intended individual - but it may appear to have worked, if you have done no error checking (like CloneVDI does) until the internal inconsistencies (i.e. the fact that the header is valid except it doesn't correctly describe the image) wrecks the VM.

Though perhaps I have misunderstood: if you truly understand the manual method then you can tailor it to any repairable scenario, which is what CloneVDI in fact does. But that is not the vibe I'm getting.

[itsme300]

may be you can have a look at this --> viewtopic.php?f=6&t=100256

[mpack]

Yes, I already saw that topic when it was new, plus you already linked to it above. In that topic you said your problem was fixed, which is fine, I'm not going to argue if you're happy - hence didn't argue at the time. But the reason you gave for it being fixed makes no sense (as I've explained above), and I have to draw the line when you start spreading your misunderstanding into other's topics.

[itsme300]

I suggested you earlier to view my header issue in an attempt to know if only the header is corrupted or any other problems with my disk. BTW the manual solution would fix it only temporarily. I restarted my VM today to see some corruption issues with my /home vdi and I had to replace it with a new vdi. Sorry for the wrong direction.

[mpack]

There is no need for me to review your header: I stopped doing that after I codified the procedure in CloneVDI. The reason your fix is only temporary is that it isn't a fix, all you did was hide the header error - the underlying corruption remained and emerges again as soon as you do anything to the disk.

However, if your temporary workaround allows you to start the VM then I would certainly use that opportunity to copy out important files: but check them outside the VM, because with a corrupted filesystem can corrupt the file contents without affecting the size or filename.