Can't boot and even read mounted drive after reclaim space

quick_joey

Junior Member
Backgroud

While updating windows 10 to 1903 version I was asked to add some more space. After that I resized partition back inside windows so I had 14Gb of unused space. Then I've been trying to resize windows drive from 50Gb down to 36Gb to get those 14Gb in my mac. Instead parallels starts to inflate virtual disk until no space left on real drive on mac.

Windows was unable to boot from this drive from both EFI and plain BIOS. Says "No boot device available". Mounting this drive with parallels mount utility shows EFI boot folder and nothing else.

Now I have 80Gb virtual drive file with content shown on screenshot:

1_virtual_hdd_package_content.png

Steps I already tried

  • prl_disk_tool check --hdd /Users/dennis/vm/Windows\ 10\ x64-0.hdd - no errors
  • prl_disk_tool merge --hdd /Users/dennis/vm/Windows\ 10\ x64-0.hdd - no errors - got 50Gb drive which looks just like there was no merge
  • gparted from installed ubuntu with mounted corrupted virtual drive
2_gparted.png
  • windows check disk from fresh installed windows
  • ntfs toolkit
  • macrium reflected show this structure
Снимок экрана 2019-07-22 в 13.55.56.png
  • disk internals ntfs recovery
The best result I got is partialy recovered files looks just like uncomplete copy from another drive. I mean every tool shows target partition that supposed to be new, resized one. But obviously there should be a source partition. If someone has any suggestion how to get old partition back I would very appreciate.
 
Yes, I did it twice.
Fisrt with no actions on virtual hdd, second with merged hdd (using prl utility). In both case result was the same I see drive inside windows but can't access it.
 
@quick_joey we have several options (like disk_tool_check) for the hdd recover and you've already tried it without any results.
In this case probable solution is restoring it from the backup.
 
Back
Top