From: nospam@needed.invalid   
      
   On Fri, 1/2/2026 4:03 AM, Lawrence D’Oliveiro wrote:   
   > On Fri, 2 Jan 2026 18:51:00 +1100, Axel wrote:   
   >   
   >> (b) Make a new install of Mint on the target disk. Use Backup Tool   
   >> on the source disk to produce a copy of the current Applications and   
   >> a copy of the /Home directory including hidden files. Restore the   
   >> source disk Applications and /Home on the new install using Backup   
   >> Tool   
   >   
   > Just copy all the files, both OS and user. Then fix up the fstab and   
   > bootloader.   
   >   
   >> *However, I do not know how to install a Boot-Loader   
   >   
   > The usual command is grub-install.   
   >   
      
   Scenarios:   
      
   1) You are in a working and running OS, and you seek to reinstall grub.   
      
         sudo grub-install   
      
   2) The target disk contains a slash, but it no longer boots. The materials   
      present at the time are.   
      
         Working_OS_HDD (booted) and   
         has the Boot Repair program   
                    or                        Target Disk (slightly in need of a   
   grub-install)   
         YannBuntu Repair CD (booted)   
      
         You would be chrooted into   
         the target disk, while doing that.   
      
   Occasionally, when using Yannbuntu Boot Repair LiveCD disc,   
   instead of automatically running commands, Yannbuntu will show you   
   a list of commands, which are the chrooting-in procedure, followed   
   by the grub-install.   
      
   https://help.ubuntu.com/community/Boot-Repair   
      
      https://sourceforge.net/projects/boot-repair-cd/files/   
      
   The disc may be a copy of Ubuntu 18.04 or so, with the Boot Repair   
   auto-loading when the CD boots up. That's just to make an appliance   
   of the disc. You will need a blank single layer DVD to make boot   
   media for your optical drive, at least. Or "dd" onto a USB stick.   
      
   You can copy a partition, and use the Boot Repair to make it   
   work. However, you the user, have to "know what a useful set of   
   partitions and flags look like" to encourage the tool to do the   
   Repair. If the Repair program notices that critical partitions   
   are missing, it won't install any additional partitions. The   
   program has to stay in its lane and not damage the goods, which   
   is why the program does not go crazy and just re-pave the thing   
   for you.   
      
   But for coincidental damage, it can usually manage to do a Boot Repair.   
   If you deleted one file in some GRUB directory, it would tip   
   your machine back upright for you.   
      
   It cannot repair your installation of Fedora, and in the screen output,   
   I did not manage to gather any clues as to what pattern it did not   
   like. But for a Debian/LinuxMint/LMDE/Ubuntu setup, it can repair   
   it for you.   
      
   Very handy, if you don't want to do your own chroot. I don't mind doing   
   the chroot manually, except for the "chroot recipe" changes from year   
   to year, and it is tedious beyond words to "find the correct list   
   this time". I used to do a lot of chrooting-in, in the Gentoo era.   
      
   # It just keeps getting more arcane. Steam punk almost.   
      
   https://wiki.gentoo.org/wiki/Chroot   
      
      Configuration   
      
      Before entering the chroot a number of directories must be mounted:   
      
      root #mount --rbind /dev /mnt/mychroot/dev   
      root #mount --make-rslave /mnt/mychroot/dev   
      root #mount -t proc /proc /mnt/mychroot/proc   
      root #mount --rbind /sys /mnt/mychroot/sys   
      root #mount --make-rslave /mnt/mychroot/sys   
      root #mount --rbind /tmp /mnt/mychroot/tmp   
      root #mount --bind /run /mnt/mychroot/run   
      
      ...   
      chroot /mnt/mychroot /bin/bash           # Now, you're "inside" the target   
   HDD OS, and things executed   
                                               # are executed in the context of   
   that HDD OS.   
      
   Your "activity" starts here. Similar to this.   
      
       sudo update-grub   
       exit                                    # We have exited the chroot   
   (Change Root), and are now back in Kansas   
                                               # with our little dog Toto.   
      
   Later in the page, they take down their mounts...   
      
        umount -f /mnt/mychroot/dev   
        umount -f /mnt/mychroot/proc   
        umount -f /mnt/mychroot/sys   
        umount -f /mnt/mychroot/tmp   
      
        blah blah  shutdown...   
      
   That's just to give some idea, how you fix a busted boot   
   using a LiveCD and "your hard drive that can almost boot" :-)   
   The Yannbuntu disc makes this easier, by giving you recipes,   
   or by just doing it so you don't learn a thing. At least one   
   of the Yannbuntu recipes is a "chroot procedure".   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)