I have a Crucial MX 500gb solid state drive.
I cloned it using Macrium (as I have in the past) to a Crucial MD 1Tb drive.
Swap drives and get a

Checking Media Presence…
Media Present…
Start PXE over IPv6

Says that for awhile then switches to
Start PXE over IPv4

It then Says boot error 1962 boot sequence will automatically restart.

Did something not clone properly do I format the drive and retry?

Make sure your BIOS settings are set up right

PC's still have a BIOS, right?

It's been a while since I used to build them

You might have a bios setting issue with uefi vs legacy.
However, if you simply cloned on the same machine and just unplugged the old drive then you things should not have changed.
Make sue the boot settings point to the new drive.

I agree with PASig ... sound like your cloned SSD is not set as the boot drive in the BIOS.

This should help you :

https://www.easeus.com/backup-...d-ssd-wont-boot.html

quote:

Originally posted by smschulz:
You might have a bios setting issue with uefi vs legacy.
However, if you simply cloned on the same machine and just unplugged the old drive then you things should not have changed.
Make sue the boot settings point to the new drive.

This is what I did and have done in the past and it just fired up as normal
Guess I’ll check the boot settings then.

If it isn't in the BIOS, the only other thing I can think of is that the drive was not completely "cloned." Specifically, that the boot sector was not copied, or some other vital boot information (e.g. the boot sector not being marked as such in the MBR) didn't get duped. In the olden days, you'd get this when the gemotry of the replacement drive (remember C/H/S?) didn't match the original because the BIOS was looking for the boot code in the wrong place. I would expect a modern cloning utility to address these issues, but software sometimes screws up. You might want to try cloning again paying extra attention to available options in the cloning proggie like system disk vs. data disk, etc.

Don't overlook that this might be a "feature" included in the cloning software to prevent "piracy."

Guess the clone got corrupted or just did not clone properly.
Formatted it and going to try again.

I’ve run a Macrium script to clone a 250GB SSD to a 500GB SSD for backup purposes weekly over a year. Macrium log file will have a record of what went wrong, assuming Macrium detected any errors. Make sure you selected all the partitions on the primary boot disk for cloning so you don’t miss the boot files as someone mentioned. Did you set the clone to make use of the entire 1TB disk as a single volume, assuming the 500GB boot disk is setup that way? Only thing else I got is to run chkdsk on the base boot disk to make sure there’re no crosslinked files on it. Macrium normally picks those up and aborts the clone process, but maybe it missed some?

Currently cloning the drive again.

I hate computers!!

It takes longer (add 50% or so depending on the CPU, RAM, and drives) but there is an option in Macrium to check and correct the image after it is created but before it is finalized. Also you can have Macrium check the image before you deploy it. Not sure how much time that adds as I have not used that option before.

Well I am certainly doing something wrong.
Same results as before.

Did I mention I hate computers.

Any suggestions for another cloning program to try?

quote:

Originally posted by Black92LX:
Well I am certainly doing something wrong.
Same results as before.

Did I mention I hate computers.

Any suggestions for another cloning program to try?

I don't know Windows software so, no, no alternative program comes to mind (except maybe Norton Ghost, which may indicate how long it has been since I used Windows).

However, you may want to consider breaking the problem into two parts, the boot part and the cloning/copying part.

To address the boot part, I would do a fresh OS install to the new disk to see if the system will boot it. I'd probably pick a Linux distribution (Knoppix, Clonezilla or SystemRescueCd) for this, but pick whatever OS your system supports (and you are comfortable with), even something like FreeDOS. You could probably even use Windows if you have distribution media available. I'm pretty sure you can download/install Windows to where it will boot without requiring "activation." This is to confirm that the new disk can be used with your system hardware, not for eventual operational use. In fact, I'd probably be inclined to try more than one alternative OS to bolster confidence in hardware compatibility.

If that succeeds, then the issue is with the cloning/copying step in which case identifying appropriate cloning software may not be a futile exercise.

If it fails, and you cannot boot anything from the new disk, then it is likely that there is something about the new disk that makes it inappropriate for booting your system. For example, it may be too big for the hard-coded parameters in your BIOS, or some subtle incompatibility with your disk controller. At this point you'd want to explore what it might take to update your BIOS, or try another drive.

Clonezilla???

Clonezilla

quote:

Originally posted by Black92LX:
Well I am certainly doing something wrong.
Same results as before.

Did I mention I hate computers.

Any suggestions for another cloning program to try?

Are these SATA 2.5 drives or m.2 drives? You are swapping drives after the clone operation? That is to say, old drives yanked out, new drive hooked to same sata cable as the source?

quote:

Originally posted by DonDraper:

quote:

Originally posted by Black92LX:
Well I am certainly doing something wrong.
Same results as before.

Did I mention I hate computers.

Any suggestions for another cloning program to try?

Are these SATA 2.5 drives or m.2 drives? You are swapping drives after the clone operation? That is to say, old drives yanked out, new drive hooked to same sata cable as the source?

SATA 2.5. Swapping them directly.
I did the exact same thing on the same computer a couple years back just went from a standard hard drive to a SSD.
Had zero issues.

Did the same on the wife’s laptop with no issue.

I’ll try the clonezilla. If that does not work guess I will just start a fresh windows install on it.

This message has been edited. Last edited by: Black92LX,

Agree with others the boot record might be messed up. Might be an easy fix. Create a USB installation drive. Search for "media creation tool" for your operating system. Download it and use it to create a bootable USB windows installation drive. With your new non-working SSD installed in your computer boot from the USB drive. This will probably involve hitting F10 or F12 when your computer first turns on. You can hit it every second until the menu comes up. Once you boot the USB it will give you the option to INSTALL or repair. Select repair you computer. Then select troubleshoot then command prompt. That will open up a text looking box. Type the following minus quotations "bootrec /fixMbr" then press Enter. Once done, turn off computer, remove USB, try again.

Alternately, I have been using Acronis for my backup and imaging needs for many years with good success. There should be a free version you could try.

Have you succeeded with 1TB drives with your software in the past?

It doesn't sound like it's getting to the 'boot from hard disk' process. Either BIOS/EFI isn't seeing SSD or SSD isn't bootable.
PXE = trying to boot from network server, usually that's 'last resort'. I'd disable PXE in the boot order & set HDD 1st.

If the SSD shows up elsewhere in the BIOS/EFI, follow cruiser's instructions to fix the MBR.

I've used Macrium/Acronis/Clonezilla to clone drives successfully & never had the issue you are seeing. SSDs gave clone programs fits at first, but I thought that would be a thing of the past.

I've used Macrium for years with great success. Make sure you are cloning everything over even the unallocated, "greyed out" spaces. It's possible you've missed the boot record.

Maybe skim over this website and see if anything is different from what you are doing ...

https://www.pcmag.com/how-to/c...stallation-to-an-ssd

Hope this helps.

example:


You can edit the primary partition to expand your drive if you haven't done that already too.