At this point I understood that the data could have been lost. I had the same problem, GParted didn't recognize the partitions at all, and it was shown as unallocated space. Took a few hours, didn't find any issues. Went back into WinPE and deleted \boot, then ran bcdboot C:\windows /s C: to reinstall the bootloader.Īt the end I ran chkdisk /R to be sure the image was ok. First I used diskpart to mark the partition as active ( list disk, sel disk, sel par 0, active). Testdisk found the partitions and restored them.Īt this point the files were recovered but the bootloader failed for several issues. Therefore my 64-bit WinPE setup needed the 64-bit testdisk binary.) (Note: WinPE lacks WOW64, the 32-bit compatibility layer for 32-bit apps. If you are not familiar with this here's a shortcut: Boot from a Windows Setup DVD (Vista or higher) and hit shift-F10 once the GUI comes up, it will give you a command prompt.ĭownload testdisk, find a way to get it onto your WinPE image (or a simple USB stick would work), and run it from the WinPE environment. How to do this could be an article unto itself. VBox doesn't seem to have these issues with VDI so I gave up on VHD.īoot into WinPE, the Windows Preinstallation Environment. I'm guessing the bug really screws up the VHD file in a way that later I/O "re-breaks" it. When I skipped this step, I could recover files from the image but it would "break itself" again after a few reboots. Here's what I did:įirst, since apparently VBox support for VHD is buggy and terrible, begin by converting the VHD to a VDI with VBoxManage clonehd foo.vhd -format vdi foo.vdi. Unlike Edison the gparted live image did not find anything. I was able to recover an image that was broken by this bug. If you do not want to do it manually, you can use any free partitioning application, such as AOMEI Partition Assistant Standard, GParted and many others. Run New.vdi and go to Windows Computer Management and Extend the disk space (assign the empty space).Note: Both VDI should not be on the same path Vboxmanage clonehd /path/Old.vdi /path/New.vdi -existing VBoxManage createhd -filename /path/New.vdi -size 100000 Replace "vboxmanage modifyhd" with "vboxmanage clonehd"Ĭreate a new virtual disk VDI (With the size you want to expand). You need to execute "vboxmanage modifyhd (resize)" (to resize the VDI) In the path that contains all the files and folders associated with the VDI. The result is a corrupt partition, very difficult to recoverī. "vboxmanage modifyhd (resize)" generates error in many systems (Windows NT5, 9x, Server and x86 versions). Here they explain the problem (in spanish)Ī.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |