ltburch2000
February 20th, 2020, 04:51 PM
So I have a 19.10 Ubuntu ext4 LVM system which has just the root and swap partitions no separate boot partition.
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 488396799 487346176 232.4G Linux LVM
I have been backing up by taking LVM snapshots and then using fsarchiver to archive that snapshot. The idea being to recover I can just run a ubuntu installer and install a LVM ubuntu fresh then lay my file system down from a backup.
However when I do this it fails to boot, saying there is no boot loader. Previous to this I was able to boot off the fresh install.
One notable thing is that in the most recent ubuntu installer it now names the LVMs a little differently than before
New:
--- Physical volume ---
PV Name /dev/nvme0n1p2
VG Name vgubuntu
PV Size 232.38 GiB / not usable 2.00 MiB
Old:
--- Physical volume ---
PV Name /dev/sdc5
VG Name ubuntu-vg
PV Size <232.17 GiB / not usable 2.00 MiB
So the VG changed name, I can change that to match
LVs are relatively speaking the same
New:
--- Logical volume ---
LV Path /dev/vgubuntu/root
Old:
--- Logical volume ---
LV Path /dev/ubuntu-vg/root
So if I rename the VG from vgubuntu to ubuntu-vg and restore the file system image I should be OK right? However when I boot it says there is no boot loader. Where am I going wrong? Is it some problem with the mapper?
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 488396799 487346176 232.4G Linux LVM
I have been backing up by taking LVM snapshots and then using fsarchiver to archive that snapshot. The idea being to recover I can just run a ubuntu installer and install a LVM ubuntu fresh then lay my file system down from a backup.
However when I do this it fails to boot, saying there is no boot loader. Previous to this I was able to boot off the fresh install.
One notable thing is that in the most recent ubuntu installer it now names the LVMs a little differently than before
New:
--- Physical volume ---
PV Name /dev/nvme0n1p2
VG Name vgubuntu
PV Size 232.38 GiB / not usable 2.00 MiB
Old:
--- Physical volume ---
PV Name /dev/sdc5
VG Name ubuntu-vg
PV Size <232.17 GiB / not usable 2.00 MiB
So the VG changed name, I can change that to match
LVs are relatively speaking the same
New:
--- Logical volume ---
LV Path /dev/vgubuntu/root
Old:
--- Logical volume ---
LV Path /dev/ubuntu-vg/root
So if I rename the VG from vgubuntu to ubuntu-vg and restore the file system image I should be OK right? However when I boot it says there is no boot loader. Where am I going wrong? Is it some problem with the mapper?