virtualbox.org

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 ...

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

card reader works for some hours and umounts suddenly and won't attach to VM even on the action of detach and attach. I've to restart the VM to get it to work again. Virtual box version : 6.1.12 host os : windows 10 guest os : Ubuntu 16.04 $ pkcs15-tool -D Using reader with a card: OMNIKEY AG CardMa...

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

Please mark this as solved as I had a typo while created a new vdi(I had entered 825 instead of 852).

I came to know this after fsck reported a mismatch in size. Apologies for my mistake.

Mpack's manual solution works for me

clone vdi says "source file corrupt - block map contains errors

I've a corrupted vdi header and vm does not boot I tried to copy 512 bytes from a new vdi to the corrupted vdi but end up with UUID issue as I missed to release and remove the corrupted vdi in virtual box virtual box version - 6.1.12 vdi size - 852 GB (915,260,047,360 bytes) attached the 2MB+ hex da...