On 9/21/23 16:23, Grant Edwards wrote:
On 2023-09-21, Victor Ivanov <vic.m.iva...@gmail.com> wrote:
On Wed, 20 Sept 2023 at 23:58, Grant Edwards <grant.b.edwa...@gmail.com> wrote:
Just make sure you update /etc/fstab and bootloader config file
with the new filesystem UUID or partition indices.
I always forget one or the other until after I try to boot the
first time. That's why I keep systemrescuecd and Gentoo minimal
install USB drives on hand.
Me too, even just recently when I migrated my OS to another build I
decided to do a few partition touch ups and fell once more into this
trap. I updated fstab but not the bootloader. Luckily, Gentoo
minimal install image is so tiny a bootable medium can literally be
created in minutes.
The tar backup restore worked just fine (and didn't take long, even
though both drives were connected via USB). I've since fixed a second
machine by adding a bios-boot partition. I should have started using
them when I switched from MBR to GPT, but I think I got bios-boot
partitions confused with UEFI boot partitions. :/
I'm also working on switching to using either labels or uuids in fstab
and grub configs so that changes in partition numbers don't cause
problems. Of course I've discovered for the Nth time in the past
10-15 years, that for the root= command line argument, the kernel
doesn't grok LABEL or UUID values -- it only understands device names
and PARTUUID.
while my Gentoo grub.cfg has root=PARTUUID=, my Artix Linux install
(using openrc) has root=UUID=. I wasn't aware they had mucked with grub
(2.12-rc1) nor do I know if it's a recent change in grub.
