home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.mint      Looks pretty on the outside, thats it!      30,566 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 28,989 of 30,566   
   Paul to All   
   Re: Recovering a system from one machine   
   21 Aug 25 22:32:43   
   
   From: nospam@needed.invalid   
      
   On Thu, 8/21/2025 5:36 PM, Lawrence D’Oliveiro wrote:   
   > On Thu, 21 Aug 2025 17:17:33 -0000 (UTC), alan wrote:   
   >   
   >> It is cloning the contents of a 1TB drive to a 2TB drive. When it is   
   >> finished, the 1TB drive will be removed.   
   >   
   > Is “cloning” going to end up with only a 1TB usable volume on the 2TB   
   > drive? Don’t do that.   
   >   
      
   I only tested in a VM, as it was the quickest thing to do.   
   I tested LM221 EFI/GPT, then cloned with dd to a 2x larger disk.   
      
   My VM seemed to freeze at some step during UEFI boot, when using   
   the larger disk (with its invalid secondary partition table). And the   
   virtual environment isn't capable of Secure Boot, as there is no TPM.   
   Control never seemed to get handed off to LM221. After I booted the   
   LM221 DVD again, and used "gparted" on it, the "size fix" which moves   
   the GPT table, seemed to be sufficient to make the larger disk boot OK.   
      
   *******   
      
   The boot part of it (if damaged) can be fixed with the Boot Repair disc,   
   which is easier than doing the chroot as the AI advised.   
      
   The Boot Repair disc (Yann), it does the chrooting for you. But at this point,   
   we don't know the extent of the damage, whatever the damage happens to be.   
   The current Boot Repair disc, downloads from SourceForge, and it uses a Ubuntu   
   core to make the disc bootable, plus a copy of the Boot Repair code.   
      
   Of the two disks, the 1TB and the 2TB, when doing the Boot Repair, only   
   the 2TB would be plugged in. Anything which is sensitive to "disk identifiers",   
   should be done with its clone unplugged from the machine. The 1TB and 2TB can't   
   be plugged in at the same time, when Boot Repairing. Since we're trying to   
   get the 2TB booting, it needs to be Boot Repaired (if the first procedure   
   was still un-bootable), and you would boot repair it when it is by itself.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca