Question Cloned Seagate 1TB SSHD to new 1TB SSD and now neither drive will boot

Jan 4, 2024
1
0
10
I purchased a 1TB Crucial SSD and downloaded the included Acronis cloning software. I connected the new SSD to a free SATA port on my HP Envy desktop, ran the cloning software in "Automatic" mode for cloning drive for use in same PC as boot device (which I believe selected GPT) and waited until it finished, saying "clone successful". I shut down the PC, unplugged my original primary drive (which is a Seagate SSHD ST1000DX001), moved the SSD to that SATA cable, and restarted. Upon boot I get a black screen white text saying essentially "ERROR: No Boot Disc has been detected".

So I figured I'd first plug my original SSHD back in, unplug the SSD, and reboot. Problem is, now my original drive won't boot and I get the same error.

Could Acronis have messed with the original drive while cloning it?
Could the fact that this is a SSHD (hybrid drive) and not a true HDD have factored into the equation - maybe the special SSD partition couldn't be cloned correctly?

Forget the new SSD for the moment, what is the best way to boot back into Windows using my original drive? I tried a Win10 boot USB I had on hand, but none of the apps on there worked (including Start-up Repair and System Recovery). The only thing I could get into was Command Prompt.

I was going to try SeaTools Bootable recovery tonight when home from work and see if that can diagnose the SSHD.

If all else fails, I may try to figure out how to reinstall a clean version of Windows 10 on the new SSD and just take to time to reinstall all my programs using the old SSHD as a aux storage drive.

Thanks!
 
Just go into bios and if the drives show up there use the bios boot menu, it's some F key combo that it will tell you at boot time. Some bios also have a boot override setting inside the bios so you can select whichever drive from there.
I think it's just the boot order that got mixed up.

The automated cloning needs a very specific order of things for it to work, I believe it would have made the clone work on whatever port it was during cloning and not on the port the original was.