From: nospam@needed.invalid
On Mon, 1/5/2026 2:26 PM, Steve wrote:
> On 1/5/2026 8:18 AM, Frank Slootweg wrote:
>> Roger Mills wrote:
>>> On 04/01/2026 21:47, Steve wrote:
>>>> The holidays are over and I should have time to continue the project I
>>>> was working on 2 weeks ago.
>>>>
>>>> I'm trying to switch to my new Samsung 870 EVO SATA 2.5 inch drive. The
>>>> paper in the box said to use Samsung Magician to clone the data. I'm
>>>> starting to believe that it doesn't work with a SATA drive!
>>>>
>>>> People suggested I use a different cloning tool. I dismissed that idea
>>>> because, certainly, Samsung Magician would work after I got my computer
>>>> to recognize the new drive. Well I did that. It's now showing on File
>>>> Explorer as drive (J:) and I have formatted it. I tested it by copying a
>>>> file with several pictures inside to (J:). It went right in and the
>>>> pictures opened just fine. I formatted again to empty it.
>>>>
>>>> I looked at you tube videos about using Samsung Magician. They all
>>>> showed a ssd that did not look like my SATA drive. Samsung Magician
>>>> seems to have 2 ways to get to "Data Migration". One way pops up a
>>>> message that the drive isn't compatible. I originally feared that it was
>>>> warning me that the new drive wasn't compatible with my computer. Going
>>>> in the other way, it shows my C: drive as the source drive but it
>>>> prompts me to connect the Samsung SSD. It doesn't see it even though it
>>>> IS there and it works.
>>>>
>>>> What cloning software is going to work with my SATA SSD?
>>>
>>> Have you installed the SATA SSD inside the computer alongside the
>>> existing drive? If so, that could be the problem. I have a feeling that
>>> Magician expects the SSD to be an external drive, mounted in a suitable
>>> enclosure and connected by USB3. That's certainly what happened when I
>>> replaced a rotating drive with an SSD in a laptop a few years ago. That
>>> worked fine. That was the only option in my case because the laptop
>>> couldn't accommodate more than one internal drive at a time.
>>>
>>> Maybe worth a try?
>>
>> I indeed think that an *internal* drive which is *formatted* - i.e.
>> has a drive letter -, is a no-no for Samsung Magician.
>>
>> IIRC, initially the SSD was not visible in Disk Management, causing
>> Samsung Magician not to see it. Now the SSD *is* visible in Disk
>> Management, but because it has a drive letter and is formatted, Samsung
>> Magician probably considers it as a no-go area and rightfully so.
>>
>> So Steve may want to remove the (J:) partition and see if Samsung
>> Magician now recognizes the SSD.
>>
>> OTOH, as others have also suggested, it's better to use Macrium
>> Reflect (Free) to do the cloning or imaging, because for Macrium you
>> don't have to guess what is doing what (and there's a lot of Macrium
>> experience/expertise in these groups).
>
> Thanks Frank.
I finally pushed the button and tested it.
Samsung Magician does copy hidden partitions. Since it does not admit to doing
this, it's hard to say how many hidden partitions it is willing to copy.
[Picture] Download original if the picture is not clear...
https://imgur.com/a/XG8zuGq
https://i.postimg.cc/qvX5TCK7/Samsung-Magician-Copies-C-W10.gif
Now, we check for dis-ambiguation. Macrium changes the BLKID so
both devices boot independently of one another. Now, we check Samsung
to see if they do boot repair by editing the BCD file as well as
generating new IDs.
sda = Samsung 870EVO 1TB clone device [ sdb PARTUUID should not change ]
$ sudo blkid
/dev/sda1: LABEL="Recovery" BLOCK_SIZE="512" UUID="8C18EFC418EFAC00"
TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="2760a238-
a8e-11f0-a9dd-40167ea8940e"
/dev/sdb1: LABEL="Recovery" BLOCK_SIZE="512" UUID="8C18EFC418EFAC00"
TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="faf38ecc-
5ec-4f5c-8f49-ed4fb01a5e28"
/dev/sda2: UUID="A8EF-E75A" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system
partition" PARTUUID="2760a239-ea8e-11f0-a9dd-40167ea8940e"
/dev/sdb2: UUID="A8EF-E75A" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system
partition" PARTUUID="cf778fb9-8847-415c-ba7b-282d3e7c4ab6"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="27
0a23a-ea8e-11f0-a9dd-40167ea8940e"
/dev/sdb3: PARTLABEL="Microsoft reserved partition" PARTUUID="f4
537a1-e080-45ff-b34f-51e55a98c771"
/dev/sda4: LABEL="W14393" BLOCK_SIZE="512" UUID="1846F27446F251CC" TYPE="ntfs"
PARTLABEL="Basic data partition" PARTUUID="2760a23b-ea8e-11f0-a9
d-40167ea8940e"
/dev/sdb4: LABEL="W14393" BLOCK_SIZE="512" UUID="1846F27446F251CC" TYPE="ntfs"
PARTLABEL="Basic data partition" PARTUUID="1d3e1de4-2290-44eb-ab
1-bd1be638b02a"
mint@mint:~$
This is a Macrium clone done right afterwards.
$ blkid
/dev/sda1: LABEL="Recovery" BLOCK_SIZE="512" UUID="8C18EFC418EFAC00"
TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="65a2373c-
506-46ab-8995-435cf261db6f"
/dev/sdb1: LABEL="Recovery" BLOCK_SIZE="512" UUID="8C18EFC418EFAC00"
TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="faf38ecc-
5ec-4f5c-8f49-ed4fb01a5e28"
/dev/sda2: UUID="A8EF-E75A" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system
partition" PARTUUID="775e88e8-6f8f-4c66-9ecb-8e38fab01494"
/dev/sdb2: UUID="A8EF-E75A" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system
partition" PARTUUID="cf778fb9-8847-415c-ba7b-282d3e7c4ab6"
/dev/sda4: LABEL="W14393" BLOCK_SIZE="512" UUID="1846F27446F251CC" TYPE="ntfs"
PARTLABEL="Basic data partition" PARTUUID="936e516e-61d1-4cf2-ac
5-b12af89b6da5"
/dev/sdb4: LABEL="W14393" BLOCK_SIZE="512" UUID="1846F27446F251CC" TYPE="ntfs"
PARTLABEL="Basic data partition" PARTUUID="1d3e1de4-2290-44eb-ab
1-bd1be638b02a"
mint@mint:~$
Summary: The graphic interface may suck on Samsung Magician, but the engine is
good, and
seems to be a somewhat quality clone function.
It's hard to guess from the behavior, how it would handle the hidden
partitions on my triple boot HDD.
Paul
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
