From: nospam@needed.invalid   
      
   On Mon, 12/22/2025 6:34 AM, J. P. Gilliver wrote:   
      
   > "I downloaded the Samsung Magician software to transfer to the new   
   > drive. When I went to use it, it showed my current drive as the source   
   > drive and prompted me install the Samsung SSD drive. It was already there.   
   > After a couple of tries, I unhooke3d the ssd and plugged it in when   
   > prompted. Nothing."   
   >   
   > That read to me (assuming this "Magician software" is in effect a   
   > cloning software) as saying it wasn't working as you and I would have   
   > expected it to.   
   >   
   >> But we're dealing with computers, and just about anything   
   >> can happen with a computer.   
   >>   
   >>    Paul   
   >   
   > :-(   
   >   
   > Yes, I suppose I'd try manually making a partition in the "unallocated"   
   > space on the new drive in Disk Management. Though with a sinking feeling   
   > (in case the cloning software coughs if it sees anything on the target).   
   >   
      
   I've been writing code here for the last couple days, and   
   just about every possible thing that could go wrong, did   
   go wrong. It was *very* educational, the project is complete   
   now, and the last curve ball was put to bed (the F5 refresh   
   in Windows 11 is not working properly right now for me on 24H2).   
      
   One problem with Samsung Magician (and some other "toolbox suites"),   
   is the drives are treated unevenly. Toolboxes will tell you, of   
   some Enterprise class devices, that your device can be ignored   
   or "not supported", when you ask for things like SMART.   
   And you are looking at the device, and yet indeed, it has   
   a Samsung icon and branding on the product, leaving no doubt   
   in your mind what you thought you bought.   
      
   I don't know if that is what is happening in this case. I think   
   the OP mentioned an 870 perhaps. That should be supported.   
      
   Some other cloning softwares, which are not "SSD toolbox suite",   
   they clone without putting on a fuss like this. Macrium is not   
   going to have a problem. There are plenty of other things   
   that work the same way (a there are 30+ backup products to   
   choose from, several of which have free versions, and they do   
   cloning.   
      
   And if you're absolutely desperate to clone, you can always   
   use "dd" or "dd.exe", but this will make a mess and then   
   I'll be writing more posts on how to clean up that mess.   
   There is nothing wrong with "dd", but the assumption is,   
   if you select it you are on a desert island and have no access   
   to the wealth of stuff we've got as alternatives. "dd" is a tool   
   of last resort. I use such things, when in a new environment, and   
   having not built trust in some other softwares for the job.   
      
   Cloning is inherently safe... as long as you have a GUI to   
   display what each disk has on it, and you check and double   
   check that you have selected the correct source and dest drives.   
      
   dd.exe makes it real easy to "pave backwards" and destroy the   
   source disk. But that Windows port that is dd.exe, it has   
   a new option which is "dd --list" and that displays disk   
   contents and helps inform you which drive is empty and   
   which drive is full, and which clone direction would be naughty.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)