This means all your files, programs, and settings will be transferred over, and your computer will boot up and run just like before – only faster! Step 1: Connect the SSD to your computerĬonnect your SSD to your computer using a SATA-to-USB cable or an SSD enclosure. By the end of this process, you’ll have an exact copy of your hard drive on your new SSD. So I'm really hoping disconnecting ALL drives before rebooting from the new clone does the trick.5 Conclusion Step by Step Tutorial: How to Clone HDD to SSDīefore we dive into the steps of cloning your HDD to SSD, let’s understand what we’re aiming to achieve here. after enabling legacy mode, my new M.2 cloned drive also shows up but will not boot. thats how I was able to test if my SATA drive would boot in the new computer as is & it does. another complication is my old boot drive is MBR, so I've enabled both legacy & UEFI mode in the BIOS. I've been wrecking my head trying to migrate over to my new computer for damn near a week now lol without any luck. If I'm missing anything here or may have overlooked, folks feel free to chime in. also if it matters I've been using Win 10 Pro which is what I'm cloning to the new M.2. the reason I bought a new M.2 is because the one that came with the computer was Gen 3 & my new mobo/CPU supports Gen 4 so why not. To give even more context, I bought a new computer which came with its own M.2 NVME SSD (Gen 3) pre-loaded with Win 10 Home, I booted into that & am using Macrium Reflect to clone my old computers boot drive to a new M.2. I hope that works but if not, I'm truly at a loss. I'm redoing the clone & will disconnect ALL other drives in the system when attempting to boot from the new clone. but you only mention disconnecting SATA drives and/or connecting to the original port. I didnt see this recommended anywhere else cept here/in your post. now I didnt disconnect the old drives in the system before attempting to boot from the new clone. but the M.2 throws up errors & wont boot. the SATA SSD boots in the new computer no issues. This will probably require the commandline diskpart function, and the clean command.Ĭlick to expand.hi, quick question - I'm cloning a SATA SSD to a PCIe M.2 NVME SSD (Gen 4). Later, reconnect the old drive and wipe all partitions on it. Maybe reboot a time or two, just to make sure. It should boot from the new drive, just like the old drive. Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive This is to allow the system to try to boot from ONLY the SSD You can manipulate the size of the partitions on the target (larger)driveĬlick on "Cloned Partition Properties", and you can specifiy the resulting partition size, to even include the whole thingĭisconnect ALL drives except for the new SSD If you are going from a smaller drive to a larger, by default, the target partition size will be the same as the Source. Select ALL the partitions on the existing C drive Run the Macrium Reflect (or Samsung Data Migration) If you are cloning from a SATA drive to PCIe/NVMe, install the relevant driver for this new NVMe/PCIe drive.ĭisconnect ALL drives except the current C and the new SSD Verify the actual used space on the current drive is significantly below the size of the new SSDĭownload and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD) Specific steps for a successful clone operation: What is the make/model/size of the new SSD? The only difference I can see myself is Disk 1 is dynamic, but everything I've read says there should be no problem.ĭon't mess with MBR-GPT in the middle of the process.Īfter the clone operation is finished, the FIRST thing you do is power down, disconnect the old drive, and power the system up with ONLY the new drive. Disk 1 is my current boot drive, but it's using I think the ESP drive on disk 2 to boot to the C. I'd really rather not take10 minutes to boot from an HDD right now, nor do I want to waste a$200 drive. Currently it half-way boots to the SSD, in that it uses the cloned Windows Boot Manager partition on my SSD, but boots to my original C: drive. I have tried to change the SSD to a dynamic disk, and tried using it as a basic disk While the SSD was in GPT I tried several diskpart commands to fix UEFI, but windows told me for almost every one that the commands were not recognized had the SSD as both MBR and GPT with no changes Cloned the HDD to the SSD several times (and want to avoid doing so again so as to preserve the lifespan of the SSD as much as possible) Since then I have been trying to switch my boot drive over to the SSD with zero success. I got an SSD nearly a month ago to replace my current HDD, as it's performance has been degrading and it currently runs at 100% no matter what I do to fix it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |