Separate /boot

[birb57]

Hi

Can we use a separate /boot partition with boom ?

Could be useful in case of grub/boot issue following red hat update otherwise our root snapshot will not be bootable directly

That's for your support

[bmr-cymru]

Hi,

Please respond to my comments on the issue you opened last week, #41 - it's not clear to me from what you've written so far what exactly you mean by "separate /boot", or "EFI system without /boot dedicated filesystem".

To understand your problem better I'd need more information on your system configuration - lsblk is a good start and also an example of a working (e.g system provided) and non-working (e.g. created with boom) boot entry from the affected system - you can find those in /boot/loader/entries. They are small files so you can just paste them into a comment.

Thanks,

[bskou57]

Hello

$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 80G 0 disk
├─sda1 8:1 0 200M 0 part /boot/efi
└─sda2 8:2 0 79.8G 0 part
├─SysVGSystem-Root-real 253:0 0 12G 0 lvm
│ ├─SysVGSystem-Root 253:1 0 12G 0 lvm /
│ └─SysVGSystem-Root_snap 253:3 0 12G 0 lvm
├─SysVGSystem-Var-real 253:4 0 16G 0 lvm
│ ├─SysVGSystem-Var 253:5 0 16G 0 lvm /var
│ └─SysVGSystem-Var_snap 253:7 0 16G 0 lvm
├─SysVGSystem-Opt-real 253:8 0 4G 0 lvm
│ ├─SysVGSystem-Opt 253:9 0 4G 0 lvm /opt
│ └─SysVGSystem-Opt_snap 253:11 0 4G 0 lvm
├─SysVGSystem-Swap 253:12 0 4G 0 lvm [SWAP]
├─SysVGSystem-Var_Tmp 253:13 0 6G 0 lvm /var/tmp
├─SysVGSystem-Tmp 253:14 0 2G 0 lvm /tmp
├─SysVGSystem-local-real 253:15 0 512M 0 lvm
│ ├─SysVGSystem-local 253:16 0 512M 0 lvm /local
│ └─SysVGSystem-local_snap 253:18 0 512M 0 lvm
├─SysVGSystem-local_snap-cow 253:17 0 512M 0 lvm
│ └─SysVGSystem-local_snap 253:18 0 512M 0 lvm
├─SysVGSystem-appl-real 253:19 0 512M 0 lvm
│ ├─SysVGSystem-appl 253:20 0 512M 0 lvm /appl
│ └─SysVGSystem-appl_snap 253:22 0 512M 0 lvm
├─SysVGSystem-appl_snap-cow 253:21 0 512M 0 lvm
│ └─SysVGSystem-appl_snap 253:22 0 512M 0 lvm
├─SysVGSystem-usr_home 253:23 0 512M 0 lvm /usr/home
├─SysVGSystem-opt_sysload 253:24 0 4G 0 lvm
├─SysVGSystem-var_audit 253:25 0 4G 0 lvm /var/audit
├─SysVGSystem-var_opt_CARKaim 253:26 0 2G 0 lvm
├─SysVGSystem-sandbox 253:27 0 10G 0 lvm
├─SysVGSystem-opt_esm 253:28 0 2G 0 lvm
├─SysVGSystem-opt_crowdstrike 253:29 0 1G 0 lvm
└─SysVGSystem-usr_openv 253:30 0 10G 0 lvm
sdb 8:16 0 40G 0 disk
├─SysVGSystem-Root_snap-cow 253:2 0 4G 0 lvm
│ └─SysVGSystem-Root_snap 253:3 0 12G 0 lvm
├─SysVGSystem-Var_snap-cow 253:6 0 4G 0 lvm
│ └─SysVGSystem-Var_snap 253:7 0 16G 0 lvm
└─SysVGSystem-Opt_snap-cow 253:10 0 2G 0 lvm
└─SysVGSystem-Opt_snap 253:11 0 4G 0 lvm

[bmr-cymru]

It's still not clear to me how you are creating this configuration - presumably /boot is a directory on the root logical volume, SysVGSystem/Root? Can you give steps to re-create this configuration using the installer? Even the /root/anaconda-ks.cfg file from the system might provide some clues.

Do the regular boot entries on the system (provided by the kernel-core package scripts/kernel-install command) work? Or do you need to edit them to include the /boot prefix too?