Hi, I restarted my computer and when it attempted to restart, it didn't boot to the opensuse grub operating system selection screen for my multiboot computer with Opensuse Tumbleweed and Windows11. It instead booted to grub command line. I tried to research the problem on the internet to try to correct this problem from grub command line, but none of the attempts I have made have worked. The commands only bring up the response "file system unknown" instead of the expected response. I've gotten Tumbleweed to boot with supergrub2-206s2-beta1-multiarch-USB, where no other version of supergrub2 would work to boot Tumbleweed from the bios bootmenu. I thought, "Great, I'm out of the woods. I'll just reinstall the grub2-efi bootloader via yast2, and I'll be back in business!" But it didn't work out that way. When I try to do that, I get this message: Error Execution of command "[["/usr/sbin/shim-install", "-config-file=/boot/grub2/grub.cfg"]]" failed. Exit code: 1 Error output: /usr/sbin/grub2-probe: error: ../grub-core/kern/fs.c: 121:unknown filesystem. I've been launched into another Linux learning adventure without asking for the opportunity, so can the list advise me how to get this problem fixed? This may not be pertinent to this problem, but when I select Windows boot manager from the bios boot list, windows boots normally from that point. I'm running opensuse Tumbleweed 20230416 with KDE PLasma version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 6.2.10-1-default (64-bit) Thanks, Mark
On Fri, Apr 21, 2023 at 6:05 AM Mark Misulich <munguanaweza@gmail.com> wrote:
Hi, I restarted my computer and when it attempted to restart, it didn't boot to the opensuse grub operating system selection screen for my multiboot computer with Opensuse Tumbleweed and Windows11. It instead booted to grub command line.
It implies that grub did not find its usual configuration file grub.cfg.
I tried to research the problem on the internet to try to correct this problem from grub command line, but none of the attempts I have made have worked. The commands only bring up the response "file system unknown" instead of the expected response.
I've gotten Tumbleweed to boot with supergrub2-206s2-beta1-multiarch-USB, where no other version of supergrub2 would work to boot Tumbleweed from the bios bootmenu. I thought, "Great, I'm out of the woods. I'll just reinstall the grub2-efi bootloader via yast2, and I'll be back in business!" But it didn't work out that way. When I try to do that, I get this message:
Error Execution of command "[["/usr/sbin/shim-install", "-config-file=/boot/grub2/grub.cfg"]]" failed. Exit code: 1 Error output: /usr/sbin/grub2-probe: error: ../grub-core/kern/fs.c: 121:unknown filesystem.
This matches what you got in grub CLI. grub2-probe is using the same drivers as the grub boot time binary.
I've been launched into another Linux learning adventure without asking for the opportunity, so can the list advise me how to get this problem fixed?
Run bash -ex /usr/sbin/shim-install --config-file=/boot/grub2/grub.cfg it should show the command invocation that failed. But my guess is that the filesystem on /boot/efi is somehow corrupted.
This may not be pertinent to this problem, but when I select Windows boot manager from the bios boot list, windows boots normally from that point.
I'm running opensuse Tumbleweed 20230416 with KDE PLasma version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 6.2.10-1-default (64-bit)
Thanks, Mark
On Fri, 2023-04-21 at 10:05 +0300, Andrei Borzenkov wrote:
On Fri, Apr 21, 2023 at 6:05 AM Mark Misulich <munguanaweza@gmail.com> wrote:
Hi, I restarted my computer and when it attempted to restart, it didn't boot to the opensuse grub operating system selection screen for my multiboot computer with Opensuse Tumbleweed and Windows11. It instead booted to grub command line.
It implies that grub did not find its usual configuration file grub.cfg.
I tried to research the problem on the internet to try to correct this problem from grub command line, but none of the attempts I have made have worked. The commands only bring up the response "file system unknown" instead of the expected response.
I've gotten Tumbleweed to boot with supergrub2-206s2-beta1-multiarch-USB, where no other version of supergrub2 would work to boot Tumbleweed from the bios bootmenu. I thought, "Great, I'm out of the woods. I'll just reinstall the grub2-efi bootloader via yast2, and I'll be back in business!" But it didn't work out that way. When I try to do that, I get this message:
Error Execution of command "[["/usr/sbin/shim-install", "-config-file=/boot/grub2/grub.cfg"]]" failed. Exit code: 1 Error output: /usr/sbin/grub2-probe: error: ../grub-core/kern/fs.c: 121:unknown filesystem.
This matches what you got in grub CLI. grub2-probe is using the same drivers as the grub boot time binary.
I've been launched into another Linux learning adventure without asking for the opportunity, so can the list advise me how to get this problem fixed?
Run
bash -ex /usr/sbin/shim-install --config-file=/boot/grub2/grub.cfg
it should show the command invocation that failed. But my guess is that the filesystem on /boot/efi is somehow corrupted.
This may not be pertinent to this problem, but when I select Windows boot manager from the bios boot list, windows boots normally from that point.
I'm running opensuse Tumbleweed 20230416 with KDE PLasma version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 6.2.10-1-default (64-bit)
Thanks, Mark
Here's the readout: bash -ex /usr/sbin/shim-install --config-file=/boot/grub2/grub.cfg ++ uname -m + arch=x86_64 + rootdir= + bootdir= + efidir= + install_device= + efibootdir= + ca_string= + no_nvram=no + removable=no + clean=no + sysconfdir=/etc + libdir=/usr/lib64 + datadir=/usr/share + source_dir=/usr/share/efi/x86_64 + efibootmgr=/usr/sbin/efibootmgr + grub_probe=/usr/sbin/grub2-probe + grub_mkrelpath=/usr/bin/grub2-mkrelpath + grub_install=/usr/sbin/grub2-install + grub_install_target= ++ basename /usr/sbin/shim-install + self=shim-install + grub_cfg=/boot/grub2/grub.cfg + update_boot=no + def_grub_efi=/usr/share/efi/x86_64/grub.efi + def_boot_efi= + '[' '!' -r /usr/etc/default/shim ']' + '[' '!' -r /etc/default/shim ']' + '[' -z '' ']' + def_shim_efi=shim.efi + source_shim_efi=/usr/share/efi/x86_64/shim.efi + '[' xx86_64 = xx86_64 ']' + grub_install_target=x86_64-efi + def_boot_efi=bootx64.efi + '[' '!' -d /usr/share/efi/x86_64 -o '!' -e /usr/share/efi/x86_64/grub.efi ']' + test -f /etc/default/grub + . /etc/default/grub ++ GRUB_DISTRIBUTOR= ++ GRUB_DEFAULT=saved ++ GRUB_HIDDEN_TIMEOUT=0 ++ GRUB_HIDDEN_TIMEOUT_QUIET=true ++ GRUB_TIMEOUT=8 ++ GRUB_CMDLINE_LINUX_DEFAULT='splash=silent resume=/dev/disk/by- uuid/c210e8d8-ee1e-462e-a95d-889908be36d8 quiet security=apparmor mitigations=auto' ++ GRUB_CMDLINE_LINUX= ++ GRUB_TERMINAL=gfxterm ++ GRUB_GFXMODE=auto ++ GRUB_BACKGROUND= ++ GRUB_THEME=/boot/grub2/themes/openSUSE/theme.txt ++ SUSE_BTRFS_SNAPSHOT_BOOTING=true ++ GRUB_USE_LINUXEFI=true ++ GRUB_DISABLE_OS_PROBER=false ++ GRUB_ENABLE_CRYPTODISK=n ++ GRUB_CMDLINE_XEN_DEFAULT=vga=gfx-1024x768x16 + '[' x = x ']' + '[' -f /etc/os-release ']' + . /etc/os-release ++ NAME='openSUSE Tumbleweed' ++ ID=opensuse-tumbleweed ++ ID_LIKE='opensuse suse' ++ VERSION_ID=20230419 ++ PRETTY_NAME='openSUSE Tumbleweed' ++ ANSI_COLOR='0;32' ++ CPE_NAME=cpe:/o:opensuse:tumbleweed:20230419 ++ BUG_REPORT_URL=https://bugzilla.opensuse.org ++ SUPPORT_URL=https://bugs.opensuse.org ++ HOME_URL=https://www.opensuse.org ++ DOCUMENTATION_URL=https://en.opensuse.org/Portal:Tumbleweed ++ LOGO=distributor-logo-Tumbleweed + GRUB_DISTRIBUTOR='openSUSE Tumbleweed ' ++ echo 'openSUSE Tumbleweed ' ++ tr A-Z a-z ++ cut '-d ' -f1 + bootloader_id=opensuse + test -z opensuse + efi_distributor=opensuse + bootloader_id=opensuse-secureboot + case "$bootloader_id" in + ca_string='openSUSE Secure Boot CA1' + test 1 -gt 0 + option=--config-file=/boot/grub2/grub.cfg + shift + case "$option" in ++ echo --config-file=/boot/grub2/grub.cfg ++ sed s/--config-file=// + grub_cfg=/boot/grub2/grub.cfg + test 0 -gt 0 + test -n '' + '[' -z '' ']' + bootdir=/boot + '[' -n '' ']' + test -n '' + test -d /boot/efi ++ /usr/sbin/grub2-probe --target=device --device-map= /boot/efi + install_device=/dev/nvme0n1p1 ++ /usr/sbin/grub2-probe --target=device --device-map= /boot + test x/dev/nvme0n1p1 '!=' x/dev/nvme0n1p5 + efidir=/boot/efi + test -n /boot/efi ++ /usr/sbin/grub2-probe --target=fs /boot/efi /usr/sbin/grub2-probe: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1. /usr/sbin/grub2-probe: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1. /usr/sbin/grub2-probe: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1. /usr/sbin/grub2-probe: error: ../grub-core/kern/disk.c:236:disk `hostdisk//dev/nvme0n1p1' not found. + efi_fs=
On Fri, Apr 21, 2023 at 2:45 PM lxmark <munguanaweza@gmail.com> wrote: > > > Error output: /usr/sbin/grub2-probe: error: ../grub-core/kern/fs.c: > > > 121:unknown filesystem. ... > ++ /usr/sbin/grub2-probe --target=fs /boot/efi > /usr/sbin/grub2-probe: warning: disk does not exist, so falling back to > partition device /dev/nvme0n1p1. > /usr/sbin/grub2-probe: warning: disk does not exist, so falling back to > partition device /dev/nvme0n1p1. > /usr/sbin/grub2-probe: warning: disk does not exist, so falling back to > partition device /dev/nvme0n1p1. > /usr/sbin/grub2-probe: error: ../grub-core/kern/disk.c:236:disk > `hostdisk//dev/nvme0n1p1' not found. > + efi_fs= Well, that is a different error although the result is the same. Is /boot/efi mounted? Show lsblk --fs Full output of journalctl -b --no-pager --full would be useful as well (upload to https://susepaste.org).
On Fri, 2023-04-21 at 14:58 +0300, Andrei Borzenkov wrote: > On Fri, Apr 21, 2023 at 2:45 PM lxmark <munguanaweza@gmail.com> > wrote: > > > > > Error output: /usr/sbin/grub2-probe: error: ../grub- > > > > core/kern/fs.c: > > > > 121:unknown filesystem. > ... > > ++ /usr/sbin/grub2-probe --target=fs /boot/efi > > /usr/sbin/grub2-probe: warning: disk does not exist, so falling > > back to > > partition device /dev/nvme0n1p1. > > /usr/sbin/grub2-probe: warning: disk does not exist, so falling > > back to > > partition device /dev/nvme0n1p1. > > /usr/sbin/grub2-probe: warning: disk does not exist, so falling > > back to > > partition device /dev/nvme0n1p1. > > /usr/sbin/grub2-probe: error: ../grub-core/kern/disk.c:236:disk > > `hostdisk//dev/nvme0n1p1' not found. > > + efi_fs= > > Well, that is a different error although the result is the same. Is > /boot/efi mounted? Show > > lsblk --fs https://paste.opensuse.org/pastes/0ac5ca4e5452 > > Full output of > > journalctl -b --no-pager --full https://paste.opensuse.org/pastes/43cc98b99aac > > > would be useful as well (upload to https://susepaste.org).
On Fri, Apr 21, 2023 at 3:12 PM lxmark <munguanaweza@gmail.com> wrote:
Full output of
journalctl -b --no-pager --full
This needs to be run as root, not user.
On Fri, 2023-04-21 at 15:34 +0300, Andrei Borzenkov wrote:
On Fri, Apr 21, 2023 at 3:12 PM lxmark <munguanaweza@gmail.com> wrote:
Full output of
journalctl -b --no-pager --full
This needs to be run as root, not user.
On Fri, 2023-04-21 at 15:34 +0300, Andrei Borzenkov wrote:
On Fri, Apr 21, 2023 at 3:12 PM lxmark <munguanaweza@gmail.com> wrote:
Full output of
journalctl -b --no-pager --full
This needs to be run as root, not user.
I've had more time to work on this, and have a few more things to report. This problem initially happened after I installed the latest updates in Windows 11, and then attempted to restart into Tumbleweed. In the middle of some troubleshooting, the Bios updated on it's own, without my selecting an update. But that didn't change anything regarding the booting, as I still can't boot normally. Subsequently, I tried reinstalling Win 11, but that didn't help. I've found that now the computer won't recognize uefi formatted usb sticks that I have made with Rufus on Win10. The only way that it recognizes them to boot from them (such as g-parted, supergrub2, or Tumbleweed installation iso) is to disable secureboot in the bios. This never was an issue before the booting problem. I can't boot either Windows 11 or Tumbleweed from Grub, with secure boot activated in the bios. When I try to boot the computer in expectation of seeing the grub operating system selection menu, the grub screen never appears and I get a message: Verifying shim SBAT data failed. Security Policy Violation. Something has gone seriously wrong: SBAT Self-check failed: Security Policy Violation. I have to go into the bios boot selection list to boot the windows bootloader for a successful boot to Windows. When I try to select Tumbleweed in the bios boot menu, I get this message again: Verifying shim SBAT data failed. Security Policy Violation. Something has gone seriously wrong: SBAT Self-check failed: Security Policy Violation. If I deselect Secureboot in the Bios, the grub operating selection screen presents, and I can select the operating systems as I normally would. But booting doesn't occur normally. Selecting Tumbleweed boots to a screen saying: [ 0.052339][ T1]: [Firmware Bug]: TPM interrupt not working, polling instead You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit" to boot into default mode. Give root password for maintenance (or press Control-D to continue): [ 9.168832][ T1048] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 I can no longer boot into Tumbleweed at all, either with secureboot enabled or disabled in the bios. If I select Windows in the grub selection screen while booting with secureboot disabled, I get a blue Bitlocker screen asking for my harddrive passcode to enable boot. I had been using this laptop computer as a multiboot with Win 11 and openSUSE for a few years now without a problem. This booting problem has only just presented itself since I first posted about it on the mailing list. It seems as if the computer no longer recognizes Tumbleweed as being secureboot capable, and won't allow it to operate. Mark
On 29.04.2023 16:49, Mark Misulich wrote:
On Fri, 2023-04-21 at 15:34 +0300, Andrei Borzenkov wrote:
On Fri, Apr 21, 2023 at 3:12 PM lxmark <munguanaweza@gmail.com> wrote:
Full output of
journalctl -b --no-pager --full
This needs to be run as root, not user.
Sorry, I got distracted, so missed you reply and now I cannot download log. But recently I noticed grub2 changelog that fixes filesystem type detection on disks with 4K sectors. What sector size your disk has? ...
I can't boot either Windows 11 or Tumbleweed from Grub, with secure boot activated in the bios. When I try to boot the computer in expectation of seeing the grub operating system selection menu, the grub screen never appears and I get a message:
Verifying shim SBAT data failed. Security Policy Violation. Something has gone seriously wrong: SBAT Self-check failed: Security Policy Violation.
This means you booted very moder shim at least once. See https://bugzilla.suse.com/show_bug.cgi?id=1209985 ...
Selecting Tumbleweed boots to a screen saying:
[ 0.052339][ T1]: [Firmware Bug]: TPM interrupt not working, polling instead You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit" to boot into default mode.
The only reason to go into emergency mode is failed mount. Check your /etc/fstab, check which devices are available. It could also be resume=... kernel option referring to a missing device.
Give root password for maintenance (or press Control-D to continue): [ 9.168832][ T1048] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
I can no longer boot into Tumbleweed at all, either with secureboot enabled or disabled in the bios.
If I select Windows in the grub selection screen while booting with secureboot disabled, I get a blue Bitlocker screen asking for my harddrive passcode to enable boot.
I had been using this laptop computer as a multiboot with Win 11 and openSUSE for a few years now without a problem. This booting problem has only just presented itself since I first posted about it on the mailing list. It seems as if the computer no longer recognizes Tumbleweed as being secureboot capable, and won't allow it to operate.
Mark
participants (3)
-
Andrei Borzenkov -
lxmark -
Mark Misulich