[SOLVED] M.2 & SSD woes

[Richard1439]

Experiencing strange disk behavior where the PC will not boot to the M.2 drive, if it is selected as the boot drive in the BIOS. If I disable it in the BIOS, it boots.
It's a 'Samsung 950 Pro M.2 512GB PCI-E 3.0 SSD'. MB is a new ASRock X570 Phantom Gaming 4.
With the M.2 disabled in the BIOS and booting/working, I then tried to add an SSD. The SSD (Samsung 860 Evo series 2.5" 500GB SATA III) gets recognized in the BIOS, but the system will not boot, and will not recognize the M.2 drive in the BIOS at all. Both drives were clones; the M.2 drive was cloned from a bootable SSD as an upgrade (SSD to M.2, more capacity, SSD replaced with a high capacity SSD) using Acronis.
Appreciate any suggestions.

 

[Lutfij]

Welcome to the forums, newcomer!

Seeing how you need to be on Windows 10 and the thing with Windows 10 is that you need to have Windows Boot Manager as the primary boot device within BIOS in order for the OS to even work, I think that's what you need to do.

Also, did you reinstall the OS on the M.2?

What BIOS version are you on for your motherboard?

 

[USAFRet]

Both drives were clones

Clones from what?

Other drives in this same system?
Something from a different system?

Please show us a screencap of the Disk Management window.

 

[Richard1439]

Welcome to the forums, newcomer!

Seeing how you need to be on Windows 10 and the thing with Windows 10 is that you need to have Windows Boot Manager as the primary boot device within BIOS in order for the OS to even work, I think that's what you need to do.

Also, did you reinstall the OS on the M.2?

What BIOS version are you on for your motherboard?

I do not get the boot manager option in the Bios, just the drive itself shows up; the Bios is version 870F10/8701021. We did not reinstall Windows after the clone.

 

[USAFRet]

We did not reinstall Windows after the clone.

Is this a clone to a new drive in the same system?
Or a clone, moving it to a new system? ("MB is a new ASRock X570 Phantom Gaming 4 ")

Details and screencaps, please.

 

[Richard1439]

Clones from what?

Other drives in this same system?
Something from a different system?

Please show us a screencap of the Disk Management window.

Hi USAFRet,
The M.2 was cloned from a 128 GB SSD - SATA drive, which was on a different system yes. We upgraded the PC and cloned the disks over to newer, larger disks.

https://imgur.com/a/I40DPUT

View: https://imgur.com/a/I40DPUT

 

[USAFRet]

Hi USAFRet,
The M.2 was cloned from a 128 GB SSD - SATA drive, which was on a different system yes. We upgraded the PC and cloned the disks over to newer, larger disks.

A new motherboard really really needs a fresh OS install on the desired drive.

SATA -> NVMe
Old mb -> New mb

Too many changes.

Bite the bullet and do a full OS reinstall on this new system.
Do this OS install with ONLY the desired drive connected.
Reconnect others later.

How To - Windows 10 clean install tutorial

If you are looking for the Windows 11 Clean install tutorial, you can find that here: Windows 11 Clean install tutorial (Click here) Otherwise, welcome to the Windows 10 Clean install tutorial This tutorial is intended to help you, step by step, to perform a clean install of Windows...

forums.tomshardware.com

 

[Richard1439]

Wanted to close the loop on this, re-installing windows resolved the issues. Problem was cloning the OS drive from SSD to a larger M.2 (NVME) using Acronis True Image. All other disk copies worked, so I'll continue using the product, just wanted to advise of this should anyone else be considering a disk upgrade like this one.

 

[USAFRet]

Wanted to close the loop on this, re-installing windows resolved the issues. Problem was cloning the OS drive from SSD to a larger M.2 (NVME) using Acronis True Image. All other disk copies worked, so I'll continue using the product, just wanted to advise of this should anyone else be considering a disk upgrade like this one.

Non-OS drives are not a problem.
Cloning from one OS drive to another in the same system is generally not a problem.
Crossing systems with a clone - Problem.

Glad it all worked out in the end.