Salta al contenuto principale

Acronis DD10 trashed windows 7 partition

Thread needs solution

I tried to reclaim 617MB by resizing my Windows partition (140GB)and now it reports 140.6GB and unformatted.
The machine is a dual boot Win7x64 and Opensuse 11.3.

How do I reverse the effects of the Acronis partition change.

The original configuration showed 199MB System Partition 617MB unallocated 140GB NTFS

0 Users found this helpful

William:

ADD10 does not officially support Win7x32 or x64.

I have both ADD10 (Build 2.160) and ADD11 (Builds 216 and 2121) and only ADD11 (either build) worked reliably on my Win7x64 system. Interestingly, only ADD10 worked reliably on my XP32 system, while ADD11 (Build 216) created worthless unbootable clones and copies.

I can not speak to ADD11 (Build 2121) service in XP32 as I have only downloaded the update file, but have not used it on XP.

BoS

It's possible DD wasn't able to finish the resize for some reason. Were any error messages displayed?

Did you try this from Windows or from the DD CD?

It may be possible to recover the partition by deleting it (don't wipe it) and using the recovery wizard. My guess would be that you would want the original partition recovered (the one with unallocated space before it) since the new one isn't showing correctly.

It's also possible that the partition is corrupted and can't be recovered. Do you have a current backup image of the partition/drive? This is recommended before making any partitioning changes.

I used TestDisk available from sourceforge.net to recover my data from which I was able to rebuild my system. I will not be using DD11 for any subsequent operations. It doesn't have any recourse in the event of failure if there are any glitches. The batch file that executes on reboot should be able to check for potential failure to complete the operation and allow you to cancel without going part way through and scrambling your disk.

This is the main reason it's recommended to boot to the DD CD to do any "reboot" procedures. It gives you control over it and you can see if it's working or not.

In this case, it may or may not have helped since the error seems to have happened part way through the process.