Skip to main content

Cannot clone identical size HDD to Crucial MX500 (1TB)

Thread needs solution

Have been trying to clone a 1TB seagate HDD to a crucial MX500 and it keeps failing. I've done a full check of the error logs, this is basically where it fails (i think). Doing a full system dump both disks have 512 bytes/sector but i've noticed that 

HDD has

Disk 1 properties:
  BIOS number:    0x80
  Geometry:       121602 255 63  LSS: 512, PSS: 512, LSO: 0

and SDD

Disk 6 properties:
  Geometry:       121602 255 63  LSS: 512, PSS: 4096, LSO: 0

 

Can the different PSS number be the issue or is it something with my HDD

 

Any help please would be greatly appreciated

 

Regards

 

========================================

  FS:                NTFS
  File System Error 0x70003: Read error.
| line: 0x2cbdd167cbca9501
| file: c:\jenkins_agent\workspace\ati-main-win\1575\core\resizer\generic\fs.cpp:77
| function: resizer::FSProcessor::Read
| line: 0x2cbdd167cbca9501, c:\jenkins_agent\workspace\ati-main-win\1575\core\resizer\generic\fs.cpp:77, resizer::FSProcessor::Read
| $module: system_report_vs_39200
|
| error 0x10c45a: Failed to read the snapshot.
| line: 0x3fec04e376b89ed0
| file: c:\jenkins_agent\workspace\ati-main-win\1575\core\fdisk\win_snapshot.cpp:474
| function: win_snapshot_volume::IoOp
| line: 0x3fec04e376b89ed0, c:\jenkins_agent\workspace\ati-main-win\1575\core\fdisk\win_snapshot.cpp:474, win_snapshot_volume::IoOp
| $module: system_report_vs_39200
|
| error 0x9: Unknown status.
| line: 0x2aacb7b2ab852ac
| file: c:\jenkins_agent\workspace\ati-main-win\1575\core\fdisk\ver2\arch\windows\win_errors.cpp:40
| function: Fdisk::AddKstatusError
| line: 0x2aacb7b2ab852ac, c:\jenkins_agent\workspace\ati-main-win\1575\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError
| code: 0x5aa
| $module: system_report_vs_39200
|
| error 0xfff0: Insufficient system resources exist to complete the requested service
| line: 0xbd28fdbd64edb8f1
| file: c:\jenkins_agent\workspace\ati-main-win\1575\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\jenkins_agent\workspace\ati-main-win\1575\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x800705aa
| $module: system_report_vs_39200

===================================================================

0 Users found this helpful

TP, welcome to these public User Forums.

If the new Crucial MX500 is using a different sector size to the HDD then you cannot clone them.  The HDD is using 512 bytes per sector but the SSD is using 4K / 4096 bytes per sector.

See KB 45437: Acronis Cyber Protect Home Office, Acronis True Image: cloning and disk/partition recovery to a disk with different logical sector size is not supported

TP,

Be sure to check msinfo32 for the sector size of both disks.  Most SSD's will use a 512E sector format which makes them compatible with HDD's that use standard 512 sector size.

Thank you Steve and Enchantech,

i've checked the bytes/sector and it's identical as per link that Steve has sent. Please see below the 2 hard drives

Current HDD is not even half full as well, no bad sectors, run all checks, etc.

Perplexing.

Thank you for replying and if you have any more ideas please post

 

Regards

TP

 

=============================

Description    Disk drive
Manufacturer    (Standard disk drives)
Model    ASMT 2115 USB Device
Bytes/Sector    512
Media Loaded    Yes
Media Type    External hard disk media
Partitions    2
SCSI Bus    0
SCSI Logical Unit    0
SCSI Port    0
SCSI Target ID    0
Sectors/Track    63
Size    931.51 GB (1,000,202,273,280 bytes)
Total Cylinders    121,601
Total Sectors    1,953,520,065
Total Tracks    31,008,255

Tracks/Cylinder    255
Partition    Disk #5, Partition #0
Partition Size    40.00 MB (41,943,040 bytes)
Partition Starting Offset    1,048,576 bytes
Partition    Disk #5, Partition #1
Partition Size    13.25 GB (14,224,982,016 bytes)
Partition Starting Offset    42,991,616 bytes
    
Description    Disk drive
Manufacturer    (Standard disk drives)
Model    ST31000524AS
Bytes/Sector    512
Media Loaded    Yes
Media Type    Fixed hard disk
Partitions    3
SCSI Bus    0
SCSI Logical Unit    0
SCSI Port    0
SCSI Target ID    0
Sectors/Track    63
Size    931.51 GB (1,000,202,273,280 bytes)
Total Cylinders    121,601
Total Sectors    1,953,520,065
Total Tracks    31,008,255

Tracks/Cylinder    255
Partition    Disk #0, Partition #0
Partition Size    39.19 MB (41,094,144 bytes)
Partition Starting Offset    32,256 bytes
Partition    Disk #0, Partition #1
Partition Size    13.25 GB (14,224,982,016 bytes)
Partition Starting Offset    41,943,040 bytes
Partition    Disk #0, Partition #2
Partition Size    918.22 GB (985,936,166,912 bytes)
Partition Starting Offset    14,266,925,056 bytes
 

Instead of using cloning, you could use Backup & Recovery, i.e. make a full disk backup of the HDD and then recover it to the SSD.  This is my preferred method and a backup is always recommended before attempting to clone, plus you can remove the HDD to do the recovery to keep it well away from any change etc.

I understood that you were using Acronis True Image for this disk migration?

You are welcome to look at the YouTube videos I have posted on my personal channel which shows examples of doing both Backup and Recovery operations.

Indeed i am. i was just making sure you were not suggesting anything else.

Thanks for the videos also. very helpful