Virtual Disk Image Corrupted

[DODO333]

Hello All,

I just installed Windows android emulator and i restarted my pc after that virtual box ubuntu disk image is not booting up. i extracted vdi file and got two files 0.img and 1.img but i can't mount them on windows it says image is corrupted and vdi file size also gone to 17mb from 16gb now ubuntu is not booting up.Please help picture attached

vm.PNG (8.54 KiB) Viewed 2987 times

[scottgus1]

i extracted vdi file and got two files 0.img and 1.img

Whatever you did here will not help the guest boot.

If the guest is still intact with all the files in their original places, start the guest from full power off, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Please right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.

[DODO333]

log file attached you can view it thanks in advance

[DODO333]

i tried to convet img file to vdi after it makes vdi file added it as sata storage but it gives error
screenshot attached for command used

Fatal: No bootable medium found! system halted

ss.PNG (34.19 KiB) Viewed 2974 times

ss.PNG (34.19 KiB) Viewed 2974 times

[scottgus1]

Ok, what I thought might have been in the log was not there. What was there was this:

00:00:04.127731 AIOMgr: C:\Users\HWPVTLTD\VirtualBox VMs\Ubuntu 19\Snapshots\{126b0ba6-a2bd-4f4a-806a-fb5777652f5c}.vdi
00:00:04.127737 AIOMgr: C:\Users\HWPVTLTD\VirtualBox VMs\Ubuntu 19\NewVirtualDisk.vdi
......
00:00:06.802801 VDI: Out of range access (42094592) in image C:\Users\HWPVTLTD\VirtualBox VMs\Ubuntu 19\NewVirtualDisk.vdi, image size 17825792

Seems your base disk in the snapshot chain is bad.

You could try Mpack's CloneVDI to see if it can make anything of the disk file mentioned above. Or if Mpack himself happens by this topic he might have a suggestion.

The tricks you are doing with the .img files are unknown to me. You are not getting a usable disk file, thus the 'fatal' error. And you would then still have to shoehorn the resulting file back into the snapshot chain, which involves lots of Frankensteinish activity with UUIDs and a hex editor, and it quite likely still wouldn't work.

Restoring this bad disk file from a backup is the only sure thing I could suggest.

[DODO333]

ok thanks for the reply but can you give direction if there is any way to retrieve data from the .img file i will need to clone container which was made in ubuntu and copy it in new virtual machine if there could be any way to see files in ubuntu hdd so i can recover thanks ?

[scottgus1]

I do not know of any way to get data out of the .img file. I have no idea what it is or how you made it. If you made it from the corrupted vdi I would not hold out hope, unless the Windows size of the vdi file has not dropped even though Virtualbox says it is smaller.

I find that 7-zip, a free zip archive manipulator program, can open an Ubuntu vdi on my Windows host and extract files from it.

[DODO333]

yes i used 7zip to extract vdi file and then it made two files 0.img and 1.img after extraction and now i can't mount any of the disk image files on windows it says corrupted any clue ?

[mpack]

Ditch all .img files. They are meaningless.

Try opening the original VDI using CloneVDI. If you made the mistake of involving snapshots then put VDI files in one folder and open the most recent snapshot.