Problems after performing a data clone on Samsung SSDs Booting issues may occur following a data clone operation.
Problems after performing a data clone on Samsung SSDs Booting issues may occur following a data clone operation.
Hey there! My name is Andrew, I’m a technician in a repair shop. We’ve been facing a persistent problem for some time, and I’m hoping this visit can help us fix it. Most of the computers we receive need an upgrade from outdated mechanical hard drives to SSDs. I’ve been using Samsung 860/870 EVO SSDs and pairing them with Sabrent’s Acronis True Image tool and the DS-UTC2 docking station. So far, cloning drives via SATA hasn’t solved the issue. We’ve switched to Silicon Power SSDs because they consistently work without problems, even though I don’t like their lack of DRAM cache. I’m curious if this might be a BIOS-related problem or if we should consider using Crucial SSDs instead. Please share your thoughts and let me know if you have any additional information!
I cloned hundreds of Samsung SSDs in the last year. Not a single problem. I use no name USB to SATA adapters and clonezilla for copying the entire disk/partition and use Samsungs own migration tool if I only need windows. You may want to add more information about the problem you are facing. Error codes behavior etc.
Huh that's interesting issue. It could be related to the program. Have you tried alternative image program. Like clonezilla thanks @Levent But what I've usually do is Use linux live iso then run command DD if=/dev/sdx of=/dev/sdx status=progress If is from disk, of is to the disk then I'd use KDE partition manager to enable boot flag then disable boot flag and it fixes unoccupied space if it has more space than old one. After that you have to wipe old drive because it has same GUID names boot will get confused if there's two to boot from.
Regrettably there are no error messages. The clone functions properly on its own. The problem arises when trying to start from the cloned SSD, as the system fails to recognize it or refuses to boot
I rely heavily on this tool repeatedly without issues. I employ the COPY wizard which creates a perfect 1:1 copy for Windows boot manager. After that, I adjust the BIOS boot sequence to point to the alternate drive, then wipe or reformat the original. Since Windows typically has files in use, it restarts if copying a currently active C: drive, but after the copy completes and before restart, it switches to a mirrored setup. I’ve followed this process consistently and never faced problems.
Some users encounter issues starting and rebooting after a warm restart when using the Samsung EVO SSD, possibly due to a BIOS option called "aggressive LPM support." Look for this setting in your BIOS and turn it off.