Clone disk operation failed due to file record corrupted
I have tried clone my 256 Crucial SSD to a 512 Crucial SSD following the Acronis instructions for cloning laptop hard drives using an external USB enclosure with the new SSD installed in my laptop and the old source SSD installed as an external USB drive. I did the same process about 1.5 years ago when I cloned the factory hard drive to the 256 Crucial SSD. But now, the clone is failing due to what Acronis thinks as a corrupted file.
I've run chkdsk /f/r several times and have also run chkdsk /f and chkdsk /r independently. Windows does not find any problems with the drive. However, when I try to clone the drive, it fails within the first 30 seconds -- screenshots are attached.
Also attached are some disks.txt files generated by the System Reports tool.
I continue to receive the following error code: AEE-SV File record corrupted
And while I know SSD drives do not need to be / should not be defragged, I gave it a go as it was 19% fragmented. After the defrag, the disks.txt error code is slightly different: ACC-SV
The more detailed disks.txt files are attached. Any help would be greatly appreciated as I've spent 2 days on this without any progress.
Allegato | Dimensione |
---|---|
disks_after_defrag.txt | 24.52 KB |
disks_before_defrag.txt | 41.58 KB |
error_screen_left_adjust.jpg | 1.12 MB |
error_screen_right_adjust.jpg | 1.72 MB |


- Accedi per poter commentare

One other possibiliy if your a win user. SYSTEM FILE CHECKS - From a Win OS standpoint Enchanter has best idea in org. back-up otherwise if a Win back-up is not avail and recovery is as when attempting to solve corrupted file the C: prompt recovery console admin tools you already used then possibly alternate same level -Control panel in computer management/ disk management/ storage will let you right click (if the icon has a red down arrow and put it online) at the same screen the drive tools select tab select check-now in this second screen (SYSTEM FILE CHECKS) and basicall you chkdsk with auto fix which you already mentioned try to find the file listed from the org drive and copy it to the dup drive have probably already been there that file on a USB stick could be substituted in the correct directory but if not it may be worth getting a new build started.
- Accedi per poter commentare