F5F Stay Refreshed Hardware Desktop Performs cloning of HDD to SSD, restarts several times before failure.

Performs cloning of HDD to SSD, restarts several times before failure.

Performs cloning of HDD to SSD, restarts several times before failure.

M
MR_ItzLuka_YT
Junior Member
32
01-11-2016, 09:03 AM
#1
I'm working with a 1 TB SATA spinning hard drive for your grandparents' setup and attempting to transfer it to a 500 GB SATA SSD. The process keeps looping through clones, sometimes booting twice before encountering an error that prompts a reboot and device selection. I've tried using a Windows 10 installation drive but encountered issues with the Acer display.
M
MR_ItzLuka_YT
01-11-2016, 09:03 AM #1

I'm working with a 1 TB SATA spinning hard drive for your grandparents' setup and attempting to transfer it to a 500 GB SATA SSD. The process keeps looping through clones, sometimes booting twice before encountering an error that prompts a reboot and device selection. I've tried using a Windows 10 installation drive but encountered issues with the Acer display.

S
SOBGelo
Member
162
01-11-2016, 05:32 PM
#2
Could the 1TB SATA storage actually contain more information than the available space on the 500GB SSD?
S
SOBGelo
01-11-2016, 05:32 PM #2

Could the 1TB SATA storage actually contain more information than the available space on the 500GB SSD?

R
RG48
Posting Freak
778
01-14-2016, 02:01 PM
#3
Usually you need a drive with equal or greater capacity for cloning. Some software can shrink the image to fit a smaller drive, but this doesn’t always function correctly. If possible, use a 1TB or bigger storage device. The type of drive (HDD or SSD) isn’t important as long as it matches the size of the original drive being cloned. This might fix the issue, so check if you have one that fits.
R
RG48
01-14-2016, 02:01 PM #3

Usually you need a drive with equal or greater capacity for cloning. Some software can shrink the image to fit a smaller drive, but this doesn’t always function correctly. If possible, use a 1TB or bigger storage device. The type of drive (HDD or SSD) isn’t important as long as it matches the size of the original drive being cloned. This might fix the issue, so check if you have one that fits.

M
MoathyJr
Member
164
01-14-2016, 03:05 PM
#4
There was ample unused capacity on the 1TB storage device, and I reduced the excess space in Macrium. It functions smoothly across about two to three operating systems now.
M
MoathyJr
01-14-2016, 03:05 PM #4

There was ample unused capacity on the 1TB storage device, and I reduced the excess space in Macrium. It functions smoothly across about two to three operating systems now.

Y
YoloBausMC
Member
57
01-16-2016, 06:28 AM
#5
It depends on the partition size of the original drive rather than the amount of data or available space. This impacts the MBR and may cause issues later, even if it functions initially. Use a drive with the same or bigger partition size than the source. I can't ensure success, but testing it is worth trying if possible.
Y
YoloBausMC
01-16-2016, 06:28 AM #5

It depends on the partition size of the original drive rather than the amount of data or available space. This impacts the MBR and may cause issues later, even if it functions initially. Use a drive with the same or bigger partition size than the source. I can't ensure success, but testing it is worth trying if possible.

N
Nayumo
Member
118
01-16-2016, 06:37 AM
#6
I finally got it running by reducing the original partition to a smaller size and trying a USB boot drive. It reported failure, but somehow worked now. Thanks to the tech gods—praise be to tech Jesus!
N
Nayumo
01-16-2016, 06:37 AM #6

I finally got it running by reducing the original partition to a smaller size and trying a USB boot drive. It reported failure, but somehow worked now. Thanks to the tech gods—praise be to tech Jesus!