Predator Desktop not recognizing cloned SSD Predator Orion 3000

jt03
jt03 Member Posts: 4 New User
edited February 15 in 2020 Archives
I have a Predator Orion 3000 that came with a 1TB Intel Optane HDD. I cloned it to a 1TB Samsung Evo SSD using the Samsung Data Clone software. As far as I know, there were no partitions in the original drive, I've done this successfully on 6-7 different computers w/o any issues. But on this one, the computer can't find a boot disk (only the cloned SSD connected). Checking BIOS, I can see the SSD listed only under the peripherals section as connected to Sata 1 port - event he serial no. is listed. But drive does not show up on the boot list under Windows Boot Manager. I tried disabling the boot manager and changing from UEFI to Legacy, I still don't see the SSD in the boot drive list or the general boot order list. Another strange thing I noticed is that after put the original HDD back in and connected the cloned SSD with a USB dongle, computer doesn't recognize the drive. However, the SSD does connect to other computers with the same dongle - I can check and verify that the cloned files are there, including the WIndows System files. It's just bizarre and I don't know what to do at this point. Any tips/help would be appreciated.

Best Answer

  • jt03
    jt03 Member Posts: 4 New User
    Answer ✓
    I was sure the disabling of the Optane memory and re-cloning was going to solve the issue but it didn’t. What DID solve it was cloning it for the 3rd time with Macrium Reflect. Although the Samsung software had always worked for me in the past, it really failed in this case. Thank you, Macrium!

Answers

  • jt03
    jt03 Member Posts: 4 New User
    Couple of updates: the PC says (under disk manager) that the second disk connected has a signature collision. This explains why the original PC couldn't read the cloned SSD after it was connected with the USB dongle. However, the original issue remains. SSD seems healthy and the cloning seems to be done successfully (recovery and EFI partitions were cloned).
  • jt03
    jt03 Member Posts: 4 New User
    I keep answering my own question :) but I wonder if the Optane memory is the issue. I don't know much about it except I just read somewhere that it should be turned off before cloning.
  • jt03
    jt03 Member Posts: 4 New User
    Answer ✓
    I was sure the disabling of the Optane memory and re-cloning was going to solve the issue but it didn’t. What DID solve it was cloning it for the 3rd time with Macrium Reflect. Although the Samsung software had always worked for me in the past, it really failed in this case. Thank you, Macrium!
  • billsey
    billsey ACE Posts: 34,584 Trailblazer
    Yes, some of the clone software is too literal. Most resize some of the partitions to match the destination drive, and therefore change the signature, some just do a quick clone clone and everything is the same on the destination drive, including the signature. Those require you to remove the old drive in order to work right with the new one. Macrium is one of the better pieces of software...
    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.