From: nospam@needed.invalid   
      
   On Fri, 1/2/2026 10:18 PM, Lawrence D’Oliveiro wrote:   
   > On Sat, 3 Jan 2026 12:23:25 +1100, Axel wrote:   
   >   
   >> Lawrence D’Oliveiro wrote:   
   >>>   
   >>> On Fri, 2 Jan 2026 22:46:43 +1100, Axel wrote:   
   >>>   
   >>>> and in future when I format a disk I'll make the main partition   
   >>>> slightly smaller to avoid this issue.   
   >>>   
   >>> This kind of fudging should set off alarm bells that something is   
   >>> not quite right with this “solution” to the problem.   
   >>   
   >> it would allow Foxclone/Rexcuezilla to clone a disk when there's   
   >> enough space on the target disk to hold the files   
   >   
   > Which it seems they cannot manage otherwise?   
   >   
      
   For the tools that have the capability, they don't   
   always "automatically" mess with the partitions. But   
   with enough clicks and ticks, they will do it.   
      
   The Foxclone probably does not have the capability.   
   (I used the .deb from here, and set up three disks, the runtime disk, the   
   source disk, the dest disk)   
      
      https://foxclone.org/downloads.html   
      
   Results of various ways of doing things. The Macrium was slow   
   doing the shrink, but I was running it in a 32-bit Win VM.   
      
       [Picture] Macrium elected to shrink the last partition, Foxclone says to   
   use GParted instead   
      
        https://i.postimg.cc/5N3k79qL/Macrium-vs-Foxclone.gif   
      
   And as for your comment about "solution", yes, it's better   
   to root cause why the disk is the wrong size, than to be   
   messing around with the partitions. But the OP wants to   
   get on with it.   
      
   One test for disks, is to try them on two different   
   brands of Southbridge. I could use my Intel board and   
   my AMD board, the Intel with X79 PCH, the AMD with B550.   
   If the disk was smaller on the Intel, I would check the   
   BIOS and likely find it set to "RAID" for the SATA port.   
   While the disk was connected to the B550 SATA port,   
   I would erase the disk (which would remove the RAID   
   metadata) and return the disk to JBOD status. Then   
   when the disk is returned to the Intel box, the size should   
   be the same as the AMD box. But that's a solution for   
   a single issue, and that might not be the issue involved   
   this time.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)