Direkt zum Inhalt

TI Clone disk function failing for Cruxial MX500 ssd 250gb

Thread needs solution

Hi All,

 

I need help please, I am trying to run TI to clone my HHD with just 178gb on it onto my new Crucial MX500 250gb SSD drive. It has failed every time.

I checked the evt files and it said a message about bad permisssions, so I ran it as administrator but it still failed.

I did more googling, saw some ppl said chkdsk /r fixed the issue, I tried that, then tried TI clone disk, still failed,

I am out of ideas, 

these were the only warnings I saw, and stillgot them even after doing the above steps:

 

Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{a4d4c6be-7804-4945-9212-e0eff958f3ca}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly.  Check security on the volume, and try the operation again. 
 

Please can someone help me

Thanks 

 

Patrick

Anhang Größe
AcronisSystemReport2.zip 1.01 MB
0 Users found this helpful

Patrick, welcome to these User Forums.

Thank you for providing the System Report file in support of this issue.

Please can you confirm the version and build of ATI that you are using here?  This is shown on the Account page in the main ATI GUI.  (You look to be using ATI 2017 but with a very old build?).

The information in the report shows you are cloning from a 500GB (466GB Toshiba DT01ACA050) HDD drive with 5 partitions to a new 250GB (233GB Crucial CT250MX500SSD1) drive and attempting to perform the clone from within Windows 10 64-bit.

The latest clone attempt log shows the following events:

30/07/2018 02:42:06 :596  Operation Clone Disk started.
30/07/2018 02:42:06 :596  Operation description: Clone Disk 1. Clearing disk Hard disk: 2
2. Clearing disk Hard disk: 2
3. Copying partition Hard disk: 1 -> 2 Drive letter: - File system: NTFS
Volume label: Windows RE tools Size: 300 MB
4. Copying partition Hard disk: 1 -> 2 Drive letter: - File system: FAT32
Volume label: SYSTEM Size: 260 MB
5. Copying partition Hard disk: 1 -> 2 Drive letter: - File system: NTFS
Volume label: Recovery image Size: 6.348 GB -> 3.420 GB
6. Copying partition Hard disk: 1 -> 2 Drive letter: C: File system: NTFS
Volume label: Old 500gb Size: 458.3 GB -> 228.3 GB
7. Copying partition Hard disk: 1 -> 2 Drive letter: - File system: NTFS
Volume label: Size: 450 MB -> 455 MB
8. Copying MBR Hard disk: 1 -> 2
.
30/07/2018 02:42:59 :435  Pending operation 52 started: 'Clearing disk'.
30/07/2018 02:42:59 :435  Pending operation 52 started: 'Clearing disk'.
30/07/2018 02:42:59 :451  Pending operation 14 started: 'Copying partition'.
30/07/2018 02:43:29 :933  Pending operation 14 started: 'Copying partition'.
30/07/2018 02:43:32 :839  Pending operation 14 started: 'Copying partition'.
30/07/2018 02:43:33 :183  Error 0x101f6: A format/resize error.
30/07/2018 02:43:33 :183  Pending operation 14 started: 'Copying partition'.
30/07/2018 04:02:35 :137  Pending operation 14 started: 'Copying partition'.
30/07/2018 04:02:50 :308  Pending operation 61 started: 'Copying MBR'.
30/07/2018 04:03:42 :929  Error 0x13c0005: Operation has completed with errors.

The error looks to be given when ATI is attempting to clone the Recovery image partition, not the main C: OS (Old 500gb) partition.

The detailed error information states:  error 0x70008: Resize impossible

This is also shown in the Disk information text file included in the System Report where it shows only 4 partitions have been created on the Crucial SSD with a 3.4GB unallocated gap shown where the resized Recovery image partition should have been created.

A CHKDSK /R may help here with this issue but this can only be used for partitions which have been given a drive letter, so you would need to try to assign a drive letter via Windows Disk Management for this 6.3GB Recovery image partition, then run CHKDSK /R against that drive letter.

It is also possible that this Recovery image partition is no longer needed, i.e. this is the original factory restore partition to allow recovery of the computer back to how it was shipped and this has a very old version of Windows OS that you would never want to put back?  If so, then it may be simpler to just use the Delete volume option in Disk Management for this partition.  You may want to make a backup of the partition as a 'just in case' precaution.

Another option here is to go to the Toshiba Support website and download any diagnostic tools they offer for checking the disk drive as a whole entity, i.e. a disk surface check etc.

Hi Steve

Thanks so much for your swift and extensive diagnosis of my files.

I think i would be happy to not copy the 6gb recovery partition  onto my new SSD drive, do I have to delete it from the original HDD or is there a way to select which partitions I want to clone from the TI tool, leaving that 6gb recovery partition  out.. but still keeping it on the HDD drive for backup.?

As for the old version of it.. the instructions that came with the Crucial SSD drive were to go to a site like this.. crucial.com/support/ssd then follow the instructions to download TI and that was the only version I saw available.

Thank you

Pat

Pat, there are some options where you can choose what partitions to include when cloning but this then will probably require you to manually size all the other partitions instead of using the automatic cloning / resizing feature.

For the above reason, I would opt for deleting the unwanted Recovery image partition from the old HDD using either Disk Manager, or else using a partition manager tool such as the free MiniTool Partition Wizard, which would also allow you to allocate the space freed to your main C: partition rather than leave it as unallocated space.  Another benefit of using the MiniTool application is that it will also allow you to do a Surface check for the problem partition by right-clicking on this within the tool.

Thnx Steve... your 'Legend' title is well deserved! 

I deleted the 6gb recovery partition and the clone disk worked.. no hassles.

Thanx a lot!

 

Pat

Pat, glad to be able to help, thanks for the update / feedback.