[SUGGESTION] ATIH / DD should check the source / target for NTFS errors prior making any operations
Acronis b5634 Linux (Acronis 64bit)
I have made a full backup of a Sony Laptop in order to restore it to a SSD.
First of all the backup takes AGES, tried via USB 2.0 and Network.
HDD is 500 GB, 49 GB used.
Windows 10, MBR Layout.
When I try to restore the backup I face 2 issues:
1. the partition name is missing
2. the partition size and usage is reported wrong so I simply cannot restore the drive!
I have built in the HDD again, started up Win 10 and ran chkdsk, but he did not found any issues.
Ran the backup job again, and again the partition is reported to be completely filled upon restore so I cannot restore the 46 GB back to the 250 GB SDD.
Source disk:
Hitachi, 5K750-500, SATA 3 GBs, 500 GB
HTS547550A9E384
Attachment | Size |
---|---|
restore.jpg | 6.28 MB |
backup.jpg | 4.58 MB |

- Log in to post comments

Hi Berti,
I am not sure if the explainations will solve the issue. Later on I tried to attach the HDD and SSD to my own computer and tried to clone the disk directly, which did fail aswell.
At the end of the day the problem was that Windows 10 chkdsk has not found any NTFS issue on the source disk but in fact when I checked the same HDD with from Windows 10 DVD he fixed a MFT error (free space), which was likely the cause of the problem and also the problem for the long backup and restore times as ATIH, even though he indicated only 49 GB were in use he seem to backup 465 GB in sector to sector mode.
suggestion to Acronis: Acronis TI and Disk Director should consider to check the hard disk for inconsistencies and NTFS issues prior any backup or operation, and this should be done in the Linux Recovery or WinPE and the live Windows alike. This would have saved me a lot of nerves and 6 hours (if I just reinstalled Windows from the beginning...).
I have no clue why Windows 10 does not find any issues in a live check but does find issues in an offline check.
After repairing the NTFS issues and cloning the disk I still had issues that the bootmanager of Windows was broken, which was fixable by using bootrec.exe and later on using the Windows startup repair.
- Log in to post comments