On Sun, 24 Nov 2024 at 13:27, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
teller:~ # cat /etc/default/grub_installdevice
Are these only created on install?
They are managed by YaST Bootloader module.
Okay, makes sense. I pretty much ignore yast after install, in this case it's been many years ago, just using zypper dup.
Supposed to update automatically? If
Update from what to what? They most certainly are not supposed to be updated by grub-install.
I don't know, probably it would be hard to guess what to put there. I guess I was hoping something magical might be done (supposed to run) whenever grub packages get updated, and/or after boot, but I guess that was naive, especially for a more complex setup like mine. By now I also saw / vaguely remember I must have run into that on my production systems a while ago, because there we eventually ran into the issue that hardware raid volumes (HP smartarray) randomly switched between sda and sdb naming (if we have two logical arrays) - and I added something (systemd boottime service) to actually check (with knowledge about our further LVM setup and naming conventions, not generalizable) what the booted-from device is named on the current boot cycle - and write that name to both /boot/grub2/device.map and /etc/default/grub_installdevice. Just thought I type that in case someone runs into something similar. I'm happy with the situation, now I understand it (again). Thanks Andrei for your answers! best regards Patrick