Jump to content

I used Macrium Reflect to clone my boot drive. I'm trying to move it over to my new SSD but I'm not sure what's the issue. I can see and use the drive in Windows. I've cloned it twice to make sure if there were any issues. And only 1 out of 3 times have I been able to see the drive in the BIOS, but have never been able to select it as my boot drive in the boot order. Any ideas what might be the issue? I know most people would say start from scratch, but I don't want to do it. My new SSD is faster. It's an Inland Premium 2 TB. My boot drive is an Intel 660p. Would it even be worth it to switch which drive is my boot? My 660p was too full and really slow. Would it just be better to offload things to the new drive so the 660p is able to get  back to full speed?

Link to comment
https://linustechtips.com/topic/1180834-cloning-and-being-identified/
Share on other sites

Link to post
Share on other sites

40 minutes ago, mikeike951 said:

I used Macrium Reflect to clone my boot drive. I'm trying to move it over to my new SSD but I'm not sure what's the issue. I can see and use the drive in Windows. I've cloned it twice to make sure if there were any issues. And only 1 out of 3 times have I been able to see the drive in the BIOS, but have never been able to select it as my boot drive in the boot order. Any ideas what might be the issue? I know most people would say start from scratch, but I don't want to do it. My new SSD is faster. It's an Inland Premium 2 TB. My boot drive is an Intel 660p. Would it even be worth it to switch which drive is my boot? My 660p was too full and really slow. Would it just be better to offload things to the new drive so the 660p is able to get  back to full speed?

The 660p is NVME, and really, every SSD is going to perform about the same for daily tasks. You literally will never notice a difference between SATA and nvme SSD's. With that, I would just leave the 660 as boot and offload your games for example to the new drive.

 

With that said, it is still weird you can't seem to select it. I have weird NVME issues though as well, my nvme drive doesn't even show up in BIOS at all, but it boots just fine.

 

Regardless though, I would likely just leave the 660p as boot, just more simple and really won't make a difference. 

 

For evidence: 

 

Rig: i7 13700k +Contact Frame - - Asus Z790-P Wifi - - RTX 4080 - - 4x16GB 6000MHz - - Samsung 990 Pro 2TB NVMe Boot + Main Programs - - Crucial P3 2TB NVMe for photo work - - Corsair RM850x - - Sound BlasterX EA-5 - - Corsair XC8 JTC Edition - - Corsair GPU Full Cover GPU Block - - PTM 7950 - - XT45 X-Flow 420 + UT60 280 rads externally mounted - - EK XRES RGB PWM - - Fractal Define S2 - - DellAlienware AW3423DWF 34" -- Logitech Pro X Superlight - - Logitech G710+ - - LTT Northern Lights Deskpad

 

Headphones/amp/dac: Schiit Bifrost Multibit - -  Schiit Lyr 3 - - Fostex TR-X00 - - Sennheiser HD 6xx

 

Homelab/Media Server: Proxmox VE host - - 512 NVMe Samsung 980 RAID Z1 for VM's/Proxmox boot - - Xeon e5 2660 V4- - Supermicro X10SRF-i - - 128 GB ECC 2133 - - 10x8TB WD Red RAID Z2 - - 2x 800 GB SAS SSD’s (1 SLOG, 1 L2Arc) - - 45 HomeLab HL15 15 Drive 4U - - Corsair RM650i - - LSI 9305-16i HBA - - TreuNAS + many other VM’s

 

Unifi UDM Pro in front of full unifi network infrastructure

 

iPhone 17 Pro - - MacBook Air M3

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×