Mageia forum

Hello

I upgraded my mageia to the last kernel 4.4.55 this evening.
Since that moment, I'm not able to boot using the main mageia launcher in grub.
I thought the kernel was not working, but actually, I can select the 4.4.55 and boot on it in the advanced menu.


I'm getting the following message

Code: Select all

Kernel panic not syncing. VFS unable to block root fs on unkown block

You can see a picture attached.

My option passed to kernel boot :

Code: Select all

root=UUID=dcae4187-2ced-4b42-90ab-3b561fec74f4 ro splash quiet noiswmd resume=UUID=3cdeb580-4b77-43d4-a32f-366323b4ba1d acpi_osi=Linux

Any idea on the reason ?

Pierre

/ and /boot are located on what filesystem type?

Hello

My file system information from drakdisk

Point de montage : /
Périphérique : sda1
UUID : dcae4187-2ced-4b42-90ab-3b561fec74f4
Type : Journalised FS: Btrfs (0x83)
Début : secteur 2048
Taille : 20Gio (6%), 42522007 secteurs
Cylindre 0 à 2646

Thank you,
Pierre

Hmmm, cannot confirm, also installed 4.4.55-desktop-1.mga5 today and rebooted, with / being btrfs and no issues at all. Although kernel options are slightly different here:

Code: Select all

[doktor5000@Mageia5]─[14:57:47]─[~] sudo cat /boot/grub2/grub.cfg

[...]

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Mageia' --class mageia --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-799cdaf8-b6af-4299-a6c9-c934027e3bdc' {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod btrfs
        set root='hd3,msdos5'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos5 --hint-efi=hd3,msdos5 --hint-baremetal=ahci3,msdos5  799cdaf8-b6af-4299-a6c9-c934027e3bdc
        else
          search --no-floppy --fs-uuid --set=root 799cdaf8-b6af-4299-a6c9-c934027e3bdc
        fi
        echo    'Linux desktop wird geladen …'
        linux   /boot/vmlinuz-desktop root=UUID=799cdaf8-b6af-4299-a6c9-c934027e3bdc ro  splash quiet nomodeset
        echo    'Initiale Ramdisk wird geladen …'
        initrd  /boot/initrd-desktop.img
}

Hi,

What about the fact I can boot when I select the kernel 4.4.55 without issue, but that the main "mageia" link doesn't work ?

Any way to just make sure the mageia link in grub is updated to be the same as the backup ?

Regards,
Pierre

PS :my grub config line for the 3 entries (I removed everything that was identical on all menu config

Code: Select all

menuentry 'Mageia' --class mageia --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-dcae4187-2ced-4b42-90ab-3b561fec74f4' {
   echo   'Chargement de Linux desktop…'
   linux   /boot/vmlinuz-desktop root=UUID=dcae4187-2ced-4b42-90ab-3b561fec74f4 ro   splash quiet noiswmd resume=UUID=3cdeb580-4b77-43d4-a32f-366323b4ba1d acpi_osi=Linux vga=788
   echo   'Chargement du disque mémoire initial…'
   initrd   /boot/initrd-desktop.img
}
menuentry 'Mageia, avec Linux desktop' --class mageia --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-desktop-advanced-dcae4187-2ced-4b42-90ab-3b561fec74f4' {
   echo   'Chargement de Linux desktop…'
   linux   /boot/vmlinuz-desktop root=UUID=dcae4187-2ced-4b42-90ab-3b561fec74f4 ro   splash quiet noiswmd resume=UUID=3cdeb580-4b77-43d4-a32f-366323b4ba1d acpi_osi=Linux vga=788
   echo   'Chargement du disque mémoire initial…'
   initrd   /boot/initrd-desktop.img
}
menuentry 'Mageia, avec Linux 4.4.55-desktop-1.mga5' --class mageia --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.55-desktop-1.mga5-advanced-dcae4187-2ced-4b42-90ab-3b561fec74f4' {
   echo   'Chargement de Linux 4.4.55-desktop-1.mga5…'
   linux   /boot/vmlinuz-4.4.55-desktop-1.mga5 root=UUID=dcae4187-2ced-4b42-90ab-3b561fec74f4 ro   splash quiet noiswmd resume=UUID=3cdeb580-4b77-43d4-a32f-366323b4ba1d acpi_osi=Linux vga=788
   echo   'Chargement du disque mémoire initial…'
   initrd   /boot/initrd-4.4.55-desktop-1.mga5.img
}

There have been very infrequent reports of the kernel installation process failing to update the vmlinuz or initrd.img symlinks (in /boot). This may explain why the system failed to boot with the default grub entry but did boot with the entry from the advanced settings, which would have used the appropriate vmlinuz and initrd files directly.

The easiest way to fix this is to re-install the affected kernel.

Jim

Hello,

I did as you suggested and uninstalled the 4.4.55 kernel. Without rebooting I reinstalled it immediately and the situation went back to normal.

IMPORTANT : If you do the same, Check your boot folder. Mine was a mess after I uninstalled the latest kernel, some symlink were not working anymore.

pmithrandir wrote:Check your boot folder. Mine was a mess after I uninstalled the latest kernel, some symlink were not working anymore.

Which exactly? Did you capture an ls -al /boot ?

@pmithrandir
Was grub-customizer installed?

doktor5000 wrote:

pmithrandir wrote:Check your boot folder. Mine was a mess after I uninstalled the latest kernel, some symlink were not working anymore.

Which exactly? Did you capture an ls -al /boot ?

I didn't captured it, but all 4 symlink were broken.

Reg grub-customizer, it's not installed.

but all 4 symlink were broken.

Good to know you've fixed it. But I'm still puzzled as to the broken sym-links.
I've only Mageia 6 (couldron) and I've had problems with older Mageia selecting sym-links as it used (not uses - it's fixed) vmlinuz not vmlinuz-desktop [Mageia has 2 symlinks - don't know why].
You've kernel 4.4.xx-xxx. and that should be M5. If I remembered correctly, the sym-link issue was fixed in/by M5.

That may be a problem only if you installed an older kernel (after a new one) and then did a "urpme --auto-orphans" (which removed older kernels and break sym-links to it).
Was that the case in yours?
Also another cause may be your /etc/grub.d which may be changed.
Can you provide its contents?

Code: Select all

ls /etc/grub.d
cat /etc/default/grub

Thanks.

ps: we can regenerate sym-links by "# ln -sf /boot/<kernel> /boot/<linuz-sym-link>" and its intrd file "# ln -sf /boot/<initrd> /boot/<initrd-sym-link>"