Cloned nvme won't boot

[xxenon]

Customer dropped off a system (Gigabyte B 450M, Ryzen 5 2600, Radeon 7870) to upgrade the Samsung Evo 860 500gb to a WD NVME SN570 1TB.
Cloned the drive with Macrium Reflect 8, no errors.
Bios shows new drive but it just won't boot. Anyone seen this before?

 

[Diggs]

Try pulling an image and cloning from the image instead of direct drive to drive.

 

[Philippe]

Is the partition active?

 

[nlinecomputers]

The bootable Reflect USB has boot repair tools. Usually a pass with that fixes this.

 

[NviGate Systems]

So a few things come to mind. First, Samsung is a M.2 SATA device, the new drive is PCIe NVME. Totally different. The board seems to support both, but you typically as stated need to do an image, then restore. Also, having a cloning software that can post restore scan for invalid boot devices will help avoid issues. This is often called bare metal restore or other such feature, the cloning software will look for changes in boot devices and make the appropriate changes. Not that Windows always messes this up, but SATA to NVMe is kinda a big leap.

As far as partition being active, depends how this system was installed. It does support UEFI, and if the partitions are GPT, active partitions no longer exist how they used to.

 

[HCHTech]

Is it possible to wipe the NVMe, install it on the motherboard, then attach the Samsung drive externally with a USB adapter then do the clone again? I remember having to do that on occasion in year's past to get around a non-boot issue.

Also, does that system have any other drives? Windows can and will put the boot partition on another drive in the system even though the OS is on the drive you expect. If that's what happened, and you clone only the OS drive, it won't boot from the clone for sure.