Boot drive clone won't boot

[Joshua K.]

Hey everyone!

 

I am trying to clone my C drive (Samsung 512GB MZALQ512HALU-000L2) to a new 2TB drive (Crucial P3 CT2000P3SSD8). My Lenovo L340 laptop only has one M.2 slot, so I used a M.2 to USB adapter to connect the new drive to my system. I then used Macrium Reflect to clone the old drive over to the new drive. Upon swapping the new drive in, however, the system failed to boot. I got the error 0x0000000e as seen in the screenshot. I've double checked that the new drive is selected in UEFI, and that the drive is a GPT partition. I'm not really sure what I need to do here to make it work. Does anyone have any ideas?

[191x7]

7 minutes ago, Joshua K. said:

c

The cloning was perhaps unsuccessful or didn't clone all the partitions.

Clear all the partitions on the new and redo the cloning of the whole drive.

[Joshua K.]

Do you recommend any software specifically? Or should I just use Macrium Reflect again?

[DigitalGoat]

You can run Macriums 'Fix Boot' option from it's menus (if using a bootable USB with Macrium environment on it), this usually sorts the issue. However if there are missing partitions then you may need to clone again, but a better method might be to make an image of the original disk's partitions then 'restore' those partitions to the new disk which might be a better solution.

[Beerzerker]

I agree with the above comments - Something went wrong during the cloning process making the drive unbootable.
If you can get that sorted it should be fine but I'd also suggest redoing the cloning process too on this drive.

Be sure to reread things on Macrium so you can figure out if you had messed up somehow - Can't say I was never guilty of that before myself.

[Joshua K.]

Thank you guys for your help. Here is a screenshot of my cloning operation. Does this look right to you guys?

[Joshua K.]

On 2/3/2023 at 2:14 AM, DigitalGoat said:

You can run Macriums 'Fix Boot' option from it's menus (if using a bootable USB with Macrium environment on it), this usually sorts the issue. However if there are missing partitions then you may need to clone again, but a better method might be to make an image of the original disk's partitions then 'restore' those partitions to the new disk which might be a better solution.

I tried making an image and then restoring it and still no dice. Any other ideas?

[Harmsway1283]

Have you tried plugged it into your computer with the USB adapter and setting your BIOS to boot from USB? Just to rule out some kind of nvme or directory conflict. 

[Joshua K.]

44 minutes ago, Harmsway1283 said:

Have you tried plugged it into your computer with the USB adapter and setting your BIOS to boot from USB? Just to rule out some kind of nvme or directory conflict. 

Yeah it didn't work there either

[DigitalGoat]

On 2/3/2023 at 8:06 PM, Joshua K. said:

Thank you guys for your help. Here is a screenshot of my cloning operation. Does this look right to you guys?

In the image you supply there is a message at the bottom of the screen stating "! At least one partition cannot be resized", since you have 4 partitions and the only one that this message seems to apply to is the Windows partition have you addressed this, (the partition cannot be resized as there is a partition entry immediately to it's right)?

 

There are two things to try regardless of the above message, first is to swap the drives round and clone the original from the M.2 - USB adapter to the new drive fitted in the PC.

Second option is to open an admin command in Windows and type reagentc /disable (this will put the recovery files into a hidden folder called Recovery in C:\) then delete the WINRE_DRV partition and try the clone again, you will then have the required space to extend C:\. (It might be an idea to run the Fix Boot option in Macrium after the clone, just to make sure).

 

If the cloned system works you can then open an admin command and type reagentc /enable to re enable the recovery environment (it will now be used from the Recovery folder on C:\ unless you recreate the recovery partition manually.)

 

I suggest before proceeding with any changes to the original system setup you make an up to date backup image and store it somewhere safe, just in case, if you haven't already done so.

[problemsolver]

First thing that comes to my mind that hasn't been mentioned is did the old drive use the Samsung NVMe driver in Windows?  If so, than Windows likely can't boot because the nvme driver it's trying to use won't work with the Crucial nvme drive.

 

You can check by booting to your old drive >> going to Device Manager >> Storage Controllers >> and check if it's using the Standard NVM Express Controller.  If it is, then that rules that issue out.

 

If it says anything else..  then you'll likely want to uninstall that NVMe driver >> reboot >> let Windows install the default driver >> shutdown >> clone the drive and try again.

 

For example:  Seeing something like this likely would cause your cloned drive to have the exact issue you described.

[Joshua K.]

Thanks for the help everyone. I ended up getting it working by making a clonezilla bootable drive and then cloning with that