e-zero
April 1, 2023, 11:12pm
#1
I received the following error during installation as well as when I open bootloader and try to click ‘OK’:
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 can’t get grub to show up when I boot my computer. I have to boot OpenSuse with the USB installation media. Any help?
Please post the output from:
parted -l
df
The first of those commands will need to be run as root.
e-zero
April 2, 2023, 12:18pm
#3
parted -l
Model: ESE2A044-512 NVMe Phison 512GB (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: pmbr_boot
Number Start End Size File system Name Flags
1 1049kB 253MB 252MB fat32 EFI system partition boot, esp
2 253MB 387MB 134MB Microsoft reserved partition msftres
3 387MB 472GB 472GB ntfs Basic data partition msftdata
4 472GB 510GB 37.6GB btrfs
5 510GB 512GB 2148MB linux-swap(v1) swap
df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 4096 8 4088 1% /dev
tmpfs 7989844 0 7989844 0% /dev/shm
tmpfs 3195940 10776 3185164 1% /run
/dev/nvme0n1p4 36700160 7812128 27836576 22% /
/dev/nvme0n1p4 36700160 7812128 27836576 22% /.snapshots
/dev/nvme0n1p4 36700160 7812128 27836576 22% /boot/grub2/i386-pc
/dev/nvme0n1p4 36700160 7812128 27836576 22% /boot/grub2/x86_64-efi
/dev/nvme0n1p4 36700160 7812128 27836576 22% /home
/dev/nvme0n1p4 36700160 7812128 27836576 22% /opt
/dev/nvme0n1p4 36700160 7812128 27836576 22% /root
/dev/nvme0n1p4 36700160 7812128 27836576 22% /srv
/dev/nvme0n1p4 36700160 7812128 27836576 22% /usr/local
/dev/nvme0n1p4 36700160 7812128 27836576 22% /var
tmpfs 7989848 0 7989848 0% /tmp
/dev/nvme0n1p1 241664 98624 143040 41% /boot/efi
tmpfs 1597968 80 1597888 1% /run/user/1000
Running df
on btrfs fails to display important details. Try this:
erlangen:~ # btrfs filesystem usage -T /
Overall:
Device size: 1.77TiB
Device allocated: 517.07GiB
Device unallocated: 1.27TiB
Device missing: 0.00B
Device slack: 0.00B
Used: 509.77GiB
Free (estimated): 1.27TiB (min: 652.63GiB)
Free (statfs, df): 1.27TiB
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 512.00MiB (used: 0.00B)
Multiple profiles: no
Data Metadata System
Id Path single DUP DUP Unallocated Total Slack
-- -------------- --------- -------- -------- ----------- ------- -----
1 /dev/nvme0n1p2 509.01GiB 8.00GiB 64.00MiB 1.27TiB 1.77TiB -
-- -------------- --------- -------- -------- ----------- ------- -----
Total 509.01GiB 4.00GiB 32.00MiB 1.27TiB 1.77TiB 0.00B
Used 504.68GiB 2.54GiB 80.00KiB
erlangen:~ #
e-zero
April 2, 2023, 12:28pm
#5
btrfs filesystem usage -T /
Overall:
Device size: 35.00GiB
Device allocated: 9.52GiB
Device unallocated: 25.48GiB
Device missing: 0.00B
Device slack: 0.00B
Used: 7.45GiB
Free (estimated): 26.54GiB (min: 13.80GiB)
Free (statfs, df): 26.54GiB
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 16.75MiB (used: 0.00B)
Multiple profiles: no
Data Metadata System
Id Path single DUP DUP Unallocated Total Slack
-- -------------- ------- --------- -------- ----------- -------- -----
1 /dev/nvme0n1p4 8.01GiB 1.50GiB 16.00MiB 25.48GiB 35.00GiB -
-- -------------- ------- --------- -------- ----------- -------- -----
Total 8.01GiB 768.00MiB 8.00MiB 25.48GiB 35.00GiB 0.00B
I’m not seeing any obvious problem in that output, apart from the “Disk Flags: pmbr_boot”. But I do wonder whether you made some bad boot settings during install.
For your system, the installer should have used “grub2-efi” for booting, and should have cleared that “pmbr_boot” flag. I wonder whether you went to the Boot settings during install, and switched to using “grub2” rather than “grub2-efi”.
You should be able to try that again, with Yast Boot Loader. Make sure it is set for grub2-efi, and the “Protective MBR flag” is set to “remove”.
e-zero
April 2, 2023, 1:33pm
#7
So I set those settings in bootloader and then click ‘OK’ and this is what I get:
“grub2” would not call shim-install
. We do not see filesystem types in any of the provided output, so both blkid
and lsblk -f
would be helpful.
e-zero
April 2, 2023, 2:23pm
#9
blkid
/dev/nvme0n1p5: UUID="aa680359-b601-42b3-99ae-40738f7fefb2" TYPE="swap" PARTUUID="b9009a89-c560-4613-8ba6-1614004dbb33"
/dev/nvme0n1p3: LABEL="OS" BLOCK_SIZE="512" UUID="4638289A38288ACF" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="1e93999f-abb6-4a5b-9d05-e0e246ff7928"
/dev/nvme0n1p1: LABEL_FATBOOT="ESP" LABEL="ESP" UUID="0A26-BEF4" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="b2e4ff0b-e4bd-4a7d-bbdc-ac68d73afcaf"
/dev/nvme0n1p4: UUID="de783ca5-e3b3-42a6-8d37-5873f502d935" UUID_SUB="660bae7d-2c10-45af-9198-7cc318a7225a" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="94071eb4-f8aa-4f2f-8b4a-b0c26f604bde"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="949f2198-17f9-403c-94cf-e2e538a389d3"
lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1
├─nvme0n1p1 vfat FAT32 ESP 0A26-BEF4 139.7M 41% /boot/efi
├─nvme0n1p2
├─nvme0n1p3 ntfs OS 4638289A38288ACF
├─nvme0n1p4 btrfs de783ca5-e3b3-42a6-8d37-5873f502d935 21.8G 35% /var
│ /usr/local
│ /srv
│ /root
│ /opt
│ /home
│ /boot/grub2/x86_64-efi
│ /boot/grub2/i386-pc
│ /.snapshots
│ /
└─nvme0n1p5 swap 1 aa680359-b601-42b3-99ae-40738f7fefb2 [SWAP]
e-zero
April 2, 2023, 10:02pm
#10
I can’t seem to get grub installed. Any help on this?
What output do you get from
fsck -n /dev/nvme0n1p1
This is just to check whether your EFI partition is corrupt. It will probably mention a dirty bit, but you can ignore that. The “-n” option is supposed to tell it to report but not do anything. Best not to do anything when the filesystem is mounted.
Hmm, neither the “man” pages nor “fsck --help” seem to mention the “-n” option. It used to describe it as "answer “n” for every “y/n” prompt.
Perhaps another thing to try. As root:
grub2-install
Perhaps that will give a better error message than the one you are seeing from Yast.
e-zero
April 4, 2023, 10:42pm
#12
You were right. The EFI partition was corrupted. I re-installed everything (including Windows since I am dual-booting) and it works great now!
Thanks for the help.