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,985 of 30,566   
   nomail@gmail.com to alan   
   Re: Recovering a system from one machine   
   21 Aug 25 22:25:45   
   
   On Thu, 21 Aug 2025 17:17:33 -0000 (UTC)   
   alan  wrote:   
      
   > I don't want to lose the contents by reinstalling. Is there a procedure I   
   >  can take to recover it?   
      
   If you trust AI, here is what deep seek say.   
      
   This is a common issue when moving a Linux installation between   
   different hardware, especially motherboards from different   
   manufacturers. The problem is typically related to hardware detection,   
   driver compatibility, and initramfs configuration.   
      
   Here are the steps to resolve this:   
      
   1. Boot from Live USB and Chroot   
   First, boot from a Linux Live USB and mount your system:   
      
   bash   
   # Mount the root partition   
   sudo mount /dev/nvme0n1pX /mnt  # replace X with your root partition   
   number   
      
   # Mount other necessary partitions   
   sudo mount /dev/nvme0n1pY /mnt/boot  # if separate boot partition   
   sudo mount /dev/nvme0n1pZ /mnt/boot/efi  # if EFI partition   
      
   # Mount virtual filesystems   
   sudo mount --bind /dev /mnt/dev   
   sudo mount --bind /proc /mnt/proc   
   sudo mount --bind /sys /mnt/sys   
   sudo mount --bind /run /mnt/run   
      
   # Chroot into your system   
   sudo chroot /mnt   
   2. Reconfigure Initramfs and Kernel   
   bash   
   # Update initramfs for all installed kernels   
   update-initramfs -u -k all   
      
   # Reinstall kernel packages (Ubuntu/Debian)   
   apt install --reinstall linux-image-generic linux-headers-generic   
      
   # For other distributions:   
   # Fedora: dnf reinstall kernel   
   # Arch: pacman -S linux   
   3. Check and Update GRUB   
   bash   
   # Update GRUB configuration   
   update-grub   
      
   # Reinstall GRUB to the EFI partition   
   grub-install /dev/nvme0n1  # replace with your drive   
   4. Check Hardware-Specific Drivers   
   bash   
   # Install common hardware support packages   
   apt install firmware-linux firmware-linux-nonfree   
      
   # Check for missing firmware   
   dmesg | grep -i firmware   
   5. Alternative: Boot with Fallback Options   
   Try booting with these kernel parameters at the GRUB menu (press 'e' to   
   edit):   
      
   text   
   nomodeset acpi=off noapic   
   If this works, you can make it permanent by adding to /etc/default/grub:   
      
   bash   
   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"   
   update-grub   
   6. Filesystem Check   
   bash   
   # Check filesystem integrity   
   fsck /dev/nvme0n1pX  # replace with your root partition   
   7. If All Else Fails: Fresh GRUB Installation   
   bash   
   # Completely reinstall GRUB   
   apt purge grub-efi-amd64 grub-common   
   apt install grub-efi-amd64 grub-common   
   grub-install /dev/nvme0n1   
   update-grub   
   After completing these steps, reboot and you should be able to boot   
   successfully. The key is regenerating the initramfs with the new   
   hardware detection and ensuring all necessary drivers are included.   
      
   PLEASE DON'T KILL ME ;-)   
      
      
   --   
   Running Linux Mint 22.1 (Xia) using Kernel=6.14.0-28-generic on x86_64 ,   
   Cinnamon, lightdm, x11   
   AMD Ryzen 7 5700G with Radeon Graphics (16) @ 5.288GHz   
      
   --- 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