Restoring to a new SSD. Issues with fstab and UUID
The Swiss Army Knife of System Recovery
Brought to you by:
rescuezilla
Menu
▾
▴
I know this has been asked a thousand times, but I've read many threads, websites and forums and I'm still confused.
I used RescueZilla to restore a RHEL v9.3 installation from one PC to a near identical PC. The actual resoration of partitions and files went well and the new PC booted ... sort of. Howver, I have fallen foul of the UUID and fstab issue.
On booting I was presented with the "You are in emergency mode" message. After logging in as root I ran "mount -a" which returned the error
Back in fstab I rem'ed out the /rhel_server-home line:
and rebooted. The system rebooted as normal but without 'home' of course.
I've taken a look at "lsblk -r", "blkid", "ls -l /dev/disk/by-uuid" and a few other things.
This is where I'm stuck. I know I need to fix the UUID but I've hit the wall.
Guidance and/or pointers much appreciated.
Thanks from AU.
For the benefit of others, I found a solution that seems to work for me.
Looking at this page from the Rocky Linux site:
https://docs.rockylinux.org/release_notes/9_2/
and specifically, the box titled: "Upgrading with LVM devices may result in boot failure"
I followed 'Option 2' ...
"Prior to rebooting after upgrading, rename the /etc/lvm/devices/system.devices file (e.g., mv /etc/lvm/devices/system.devices{,.bak}) and, once the system has rebooted, run vgimportdevices --all to regenerate the file in the new format."
... and while the issue described wasn't exactly what I was seeing - by renaming "system.devices" and regenerating it did the trick. I was able to un-rem /dev/mapper/rhel_server-home in fstab and get a clean boot.
This may, or may not, work for others, but maybe it's worth trying as it solved my problem.