Hi, passing zypper ref then zypper dup to achieve an upgrade to the newest snapshot result with the following message displayed in konsole <
%posttrans(dracut-pcr-signature-0.5+1-1.1.noarch) script output:
Error: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.
%transfiletriggerin(sdbootutil-1+git20241217.5aeb4e9-1.1.x86_64) script output:
Error: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.
warning: %transfiletriggerin(sdbootutil-1+git20241217.5aeb4e9-1.1.x86_64) scriptlet failed, exit status 1
Running post-transaction scripts .......................................................................................................[done]
I have not attempted to powercycle the machine as of yet. I am unfamiliar as to how to address this situation. Your response is welcome.
-Thanks
Really interesting. That tool is only when you are using BTRFS in system partition:
Tool to manage systemd-boot in a btrfs based, snapper managed system. Can install systemd-boot with shim as well as install kernels into the ESP. Allows to interactively explore kernels, snapshots and boot loader entries. A non-interactive mode can be called from scriptlets or triggers.
In fact, I have no sdbootutil installed, despite I have my system with BTRFS.
Update: I think your system installs sdbootutil cause you have encrypted partitions.
I’m wondering if perhaps I should try to remove is via Gparted? Then I would with to have /dev/sda2 become /dev/sda1 though I think. This is a fresh install nearly.
Why do you want to “sda2” become “sda1”, I don’t understand that.
And about sdbootutil, maybe you are using systemd-boot instead GRUB. To know more about that, you must do bootctl status.
In my case, not using GRUB, I get this ouput:
bootctl status
systemd-boot not installed in ESP.
System:
Firmware: n/a (n/a)
Firmware Arch: x64
Secure Boot: disabled
TPM2 Support: yes
Measured UKI: no
Boot into FW: supported
More streamlined looking output when lsblk -fs is passed.
Sending result of bootctl info now…
# bootctl status
systemd-boot not installed in ESP.
System:
Firmware: n/a (n/a)
Firmware Arch: x64
Secure Boot: disabled
TPM2 Support: no
Measured UKI: no
Boot into FW: supported
Current Boot Loader:
Product: n/a
Features: ✗ Boot counting
✗ Menu timeout control
✗ One-shot menu timeout control
✗ Default entry control
✗ One-shot entry control
✗ Support for XBOOTLDR partition
✗ Support for passing random seed to OS
✗ Load drop-in drivers
✗ Support Type #1 sort-key field
✗ Support @saved pseudo-entry
✗ Support Type #1 devicetree field
✗ Enroll SecureBoot keys
✗ Retain SHIM protocols
✗ Menu can be disabled
✗ Boot loader sets ESP information
ESP: n/a
File: └─n/a
Random Seed:
System Token: not set
Exists: no
Available Boot Loaders on ESP:
ESP: /boot/efi (/dev/disk/by-partuuid/711cfe69-00b6-4628-99af-4494e49f12ab)
File: ├─/EFI/BOOT/bootx64.efi
├─/EFI/BOOT/fallback.efi
└─/EFI/BOOT/MokManager.efi
Boot Loaders Listed in EFI Variables:
Title: opensuse-secureboot
ID: 0x0000
Status: active, boot-order
Partition: /dev/disk/by-partuuid/711cfe69-00b6-4628-99af-4494e49f12ab
File: └─/EFI/opensuse/shim.efi
Boot Loader Entries:
$BOOT: /boot/efi (/dev/disk/by-partuuid/711cfe69-00b6-4628-99af-4494e49f12ab)
token: opensuse-tumbleweed
0 entries, no entry could be determined as default.
I just preformed a fresh install again after my last message. Behavior appears to be the same following ‘guided setup’ and allowing installer to remove any previous partitions.
Is it possible due to this being UEFI? Legacy setup does not require this shim ‘perhaps’?
On the fresh install zypper se -si sdbootutil displays no results, as did prior.
I do not think it has something to do with Logical Volume Managment or LUKS?
-Thanks for your insight.
TW was reported to have recently switched boot default from Grub to systemd-boot. You must actively change boot type back to Grub via the installation summary screen if you wish a new TW installation to boot from Grub. More info I cannot provide, as zypper dup keeps me keeping on, no need for fresh TW installations since change was implemented.
Did you create that image by booting to a system with no existing partition table? What happens might depend on whether existence of Grub is already evident on a system.
I don’t remember where. It was not very recent, like probably not within the past two weeks. I’m not an announcements list subscriber, so I would not likely have seen it there if it occurred there. It could have been a comment made by Andrei or by a bootloader or dracut bug report owner or commenter. I think it may have been along with a comment related to whether or not or how systemd-boot is selected for installation, something like BLS earlier in alphabetic sort than Grub. Searching forums and bugzilla for more than the past half hour produced nothing in support of my statement. I’m more inclined to think now that it’s the default in Fedora, so perhaps my old brain crosslinked TW to it.
Yes. It is a totally fresh VM. Standard BTRFS preselection. UEFI boot. Recent Tumbleweed image.
No adjustments to the installer done, except creating a username/password and selecting Plasma.
Hi, this is what I have proceeded to do (installer)and providing information as installation of openSUSE Tumbleweed proceeds on Dell-Optiplex-3010:
Notes <
Used Guided Setup
Used LVM
Used LUKS
The installation is currently at 30%…
I will report back with lsblk -fs output andbootctl status output once/when/if installation has completed.
Thank you for your help with this.
Hi, openSUSE Tumbleweed has been installed on the machine.
The problem was happening from me attempting to install onto non UEFI I think.
Here are the results of lsblk (list block devices) andbootctl status
Dell-OptiPlex-3010:~> lsblk
systemd-boot not installed in ESP.
System:
Firmware: n/a (n/a)
Firmware Arch: x64
Secure Boot: disabled
TPM2 Support: no
Measured UKI: no
Boot into FW: supported
Current Boot Loader:
Product: n/a
Features: ✗ Boot counting
✗ Menu timeout control
✗ One-shot menu timeout control
✗ Default entry control
✗ One-shot entry control
✗ Support for XBOOTLDR partition
✗ Support for passing random seed to OS
✗ Load drop-in drivers
✗ Support Type #1 sort-key field
✗ Support @saved pseudo-entry
✗ Support Type #1 devicetree field
✗ Enroll SecureBoot keys
✗ Retain SHIM protocols
✗ Menu can be disabled
✗ Boot loader sets ESP information
ESP: n/a
File: └─n/a
Random Seed:
System Token: not set
Exists: no
Available Boot Loaders on ESP:
ESP: /boot/efi (/dev/disk/by-partuuid/2785e95f-82d1-418d-9c1a-c9e81a09a84e)
File: ├─/EFI/BOOT/bootx64.efi
├─/EFI/BOOT/fallback.efi
└─/EFI/BOOT/MokManager.efi
Boot Loaders Listed in EFI Variables:
Title: opensuse-secureboot
ID: 0x0000
Status: active, boot-order
Partition: /dev/disk/by-partuuid/2785e95f-82d1-418d-9c1a-c9e81a09a84e
File: └─/EFI/opensuse/shim.efi
Boot Loader Entries:
$BOOT: /boot/efi (/dev/disk/by-partuuid/2785e95f-82d1-418d-9c1a-c9e81a09a84e)
token: opensuse-tumbleweed
0 entries, no entry could be determined as default.
lines 9-51/51 (END)
The output of the command makes it clear that you are not using systemd-boot, so at some point something you installed installed the package. If I’m not mistaken, you don’t need it. The way to check is to pretend to remove the package with sudo zypper rm systemd-boot and it will show you if it needs (or not) to uninstall other applications or libraries that depend on it. If there ARE other programs that need it, you cancel the uninstallation and that’s it.
