"Unsupported GRUB configuration" in YaST Bootloader

Hy again!

Wanted to fix VBox by removing some boot option (see Virtual subforums) and on one machine I got when opening Booloader in YaST:

The “missing” disk ist apparently a 250GB WD drive, no idea where it comes from, not installed/removed recently.

So I wanted to have a look in grub.cfg to see, what is removed if I accept the proposed new grub config (some “resume” option?), but I found no “WDC” or “2112A345” as search terms in grug.cfg or any other files in /etc/grub.d.

But as this machine is remote, I don’t want to make changes zu grub without EXACTLY knowing what is changed.

Any help to find where this 250GB WDC drive might be referenced in grub config files?

Use following snippet to show the mappings of by-id to the partition:
ls -l /dev/disk/by-id/


The modern way to add or remove kernel command line parameters is via update-bootloader. It works with systemd-boot, grub2, grub2-efi, grub2-bls, u-boot

To see which bootloader you are using:
sudo update-bootloader --show

Remove an option:

sudo update-bootloader --del-option "kvm.enable_virt_at_load= 0"
sudo update-bootloader --config

Add an option:

sudo update-bootloader --add-option "kvm.enable_virt_at_load= 0"
sudo update-bootloader --config

Show the actual settings:
sudo update-bootloader --default-settings

Hi there!

Here we have:

sudo update-bootloader --show
[sudo] password for root: 
grub2

with ls no hint whatsoever of this 250GB WD drive YaaST is apparently missing.

Do I get you right that you propose to ignore the output of YaST and manipulate grub2 directly (remove the kvm.enable option)?

Apparently there is no reference to the WD drive in current grub config:

sudo update-bootloader --default-settings
kernel=/usr/lib/modules/7.0.12-1-default/vmlinuz
initrd=/boot/initrd-7.0.12-1-default
append="splash=silent ipv6.disable=1 net.ifnames=0 quiet mitigations=auto kvm.enable_virt_at_load=0"

That means ls -l /dev/disk/by-id/ does not show this WDC drive? Did you check the content of /etc/fstab?. YaST partition manager or Cockpit drives should also show if this drive is still in use and where.

This seems to be an older installation as grub2 ist still in use instead of grub2-efi. Do you remember if you have removed or used a Western Digital SDD (WDC) in this Box?

You can use inxi -Dojpl to show your disk and partition information.

...
  ID-1: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB
  ID-2: /dev/sdb vendor: Western Digital model: WDS480G2G0B-00EPW0
    size: 447.13 GiB
...

Maybe, maybe, I copied over the initial install via dd to the current /dev/sda/ some years ago. But not really interested in the exact story, as long as removing the kvm.enable option will not kill my grub boot setup. Is this assumption correct on my end?

With a little grep I found the grub file referencing the old (?) SSD where the OS was installed on (dd copy some years ago to fresh SSD…):

cat /etc/default/grub_installdevice
/dev/disk/by-id/ata-WDC_WDS250G2B0B-00YS70_2112A3451610
activate

and

/etc/default> ls -al
total 48
drwxr-xr-x   2 root root  4096 Jun 27 16:00 .
drwxr-xr-x 143 root root 12288 Jun 27 16:04 ..
-rw-r--r--   1 root root  1680 Jun 27 16:00 grub
-rw-r--r--   1 root root  1680 Feb 13 18:16 grub.old
-rw-r--r--   1 root root    65 Jul 23  2022 grub_installdevice
...

What to make out of this? Delete the file , apparently not used anymore?

Simply let YaST do it’s job and use the proposed new grub config (opening post)?