Only kernel 5.17 is working besides others installed

hi,

i’m running kernel 5.17.15-1 and have two others installed but i can’t switch to one of them. i have tried some things (update-grub and so on) but no changes. i’ve seen in some other posts the follwing comands for some more info.

sudo mhwd-kernel -li
Currently running: 5.17.15-1-MANJARO (linux517)
The following kernels are installed in your system:
   * linux515
   * linux517
   * linux519
test -d /sys/firmware/efi && echo efi || echo bios
efi

efibootmgr -v
BootCurrent: 0001
Timeout: 5 seconds
BootOrder: 0001
Boot0001* UEFI OS	HD(1,GPT,a13ca544-f3f4-ba44-9680-675980dd8c48,0x1000,0x96000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
      dp: 04 01 2a 00 01 00 00 00 00 10 00 00 00 00 00 00 00 60 09 00 00 00 00 00 44 a5 3c a1 f4 f3 44 ba 96 80 67 59 80 dd 8c 48 02 02 / 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
    data: 00 00 42 4f
sudo update-grub
GRUB-Konfigurationsdatei wird erstellt …
Linux-Abbild gefunden: /boot/vmlinuz-5.19-x86_64
initrd-Abbild gefunden: /boot/amd-ucode.img /boot/initramfs-5.19-x86_64.img
/usr/bin/grub-probe: Error: Unknown file system.
Found initrd fallback image: /boot/initramfs-5.19-x86_64-fallback.img
Linux-Abbild gefunden: /boot/vmlinuz-5.17-x86_64
initrd-Abbild gefunden: /boot/amd-ucode.img /boot/initramfs-5.17-x86_64.img
Found initrd fallback image: /boot/initramfs-5.17-x86_64-fallback.img
Linux-Abbild gefunden: /boot/vmlinuz-5.15-x86_64
initrd-Abbild gefunden: /boot/amd-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Warnung: Zur Erkennung anderer bootfähiger Partitionen wird os-prober ausgeführt.
Dessen Ausgabe wird zur Erkennung bootfähiger Programmdateien und Erzeugen neuer Boot-Einträge verwendet.
Bootmenü-Eintrag für UEFI-Firmware-Einstellungen wird hinzugefügt …
sudo parted -l
Modell: PNY CS3030 250GB SSD (nvme)
Festplatte  /dev/nvme0n1:  250GB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: gpt
Disk-Flags: 

Nummer  Anfang  Ende   Größe  Dateisystem  Name  Flags
 1      2097kB  317MB  315MB  fat32              boot, esp
 2      317MB   250GB  250GB  f2fs         root
lsblk -f
NAME        FSTYPE FSVER LABEL    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1                                                                               
├─nvme0n1p1 vfat   FAT32 NO_LABEL 258C-574D                             299,1M     0% /boot/efi
└─nvme0n1p2 f2fs   1.14           ed344315-2b65-4fa6-a9b1-465a53d737ca  177,7G    24% /
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=258C-574D                            /boot/efi      vfat    umask=0077 0 2
UUID=ed344315-2b65-4fa6-a9b1-465a53d737ca /              f2fs    defaults,noatime 0 1

i hope that anyone can give me a way to go for my problem.

Thanks in advance

fichte

you are using f2fs … check this link:

hi brahma!

thank you, i have rolled back grub to version 2.06-6 and made update-grub now the newer kernel 5.19 is used. should i give somewhere input about this problem?

problem solved so far.

it is a known issue:
"While GRUB supports F2FS since version 2.0.4, it cannot correctly read its boot files from an F2FS partition that was created with the extra_attr flag enabled. "
https://wiki.archlinux.org/title/GRUB#Unsupported_file_systems

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.