Description of problem: I just updated to the new kernel (4.4.68-1.mga5) and when I boot the boot fails with the error: end kernel panic not syncing:VFS: Unable to mount root fs on unknown block (0,0) Version-Release number of selected component (if applicable): How reproducible: every time I try to boot. menu,lst entry is no different from prior kernels except for kernel number. 4.4.65 boots without a problem Steps to Reproduce: 1. 2. 3.
Summary: just updated to this kernel and it fails to boot giving kernel panic => Updated to kernel 4.4.68-1.mga5, it fails to boot giving kernel panicAssignee: bugsquad => kernel
Is there enough free space in /boot ? is there an initrd-4.4.68-desktop-1.mga5.img in /boot ?
CC: (none) => tmb
Yes, there is enough free space in /boot and there is an initrd-4.4.68-1.mga5 Here are the files in /boot related to 4.4.68: lrwxrwxrwx 1 root root 30 May 26 14:55 config -> ./config-4.4.68-desktop-1.mga5 -rw-r--r-- 1 root root 181101 May 14 14:00 config-4.4.68-desktop-1.mga5 -rw------- 1 root root 9383179 May 26 13:17 initrd-4.4.68-desktop-1.mga5.img lrwxrwxrwx 1 root root 32 May 26 13:17 initrd-desktop.img -> initrd-4.4.68-desktop-1.mga5.img lrwxrwxrwx 1 root root 32 May 26 13:17 initrd.img -> initrd-4.4.68-desktop-1.mga5.img -rw-r--r-- 1 root root 255652 May 14 14:00 symvers-4.4.68-desktop-1.mga5.xz lrwxrwxrwx 1 root root 38 May 26 14:48 System.map -> /boot/System.map-4.4.68-desktop-1.mga5 -rw-r--r-- 1 root root 3392266 May 14 14:00 System.map-4.4.68-desktop-1.mga5 lrwxrwxrwx 1 root root 29 May 26 13:17 vmlinuz -> vmlinuz-4.4.68-desktop-1.mga5 -rw-r--r-- 1 root root 4471904 May 14 14:00 vmlinuz-4.4.68-desktop-1.mga5 lrwxrwxrwx 1 root root 29 May 26 13:17 vmlinuz-desktop -> vmlinuz-4.4.68-desktop-1.mga5
Created attachment 9343 [details] menu.lst file This is the grub menu.lst having all the available kernels. I can boot into 4.4.65 and not into 4.4.68
please attach /var/log/dmesg and output of lspcidrake -v
Created attachment 9344 [details] output from dmesg output from dmesg as requested
(In reply to Leon Goldman from comment #5) > Created attachment 9344 [details] > output from dmesg > > output from dmesg as requested I asked for /var/log/dmesg, not the output of dmesg. The difference is that /var/log/dmesg contains info from hardware bootup, whereas dmesg will only show whats currently in dmesg buffer
Created attachment 9345 [details] output from lscpi output of lspcidrake -v as requested
Created attachment 9346 [details] list of drives from lsblk output of lsblk
Created attachment 9347 [details] output from blkid output of blkid
I added the output of lspcidrake -v and dmesg as requested and also added the output of blkid and lsblk in case that would help. Thank you
Created attachment 9348 [details] output from /var/log/dmesg here is the output. Sorry for the error.
Hi Leon, Thank you for having taken the needed time to report this issue and supply all requested information! This bug was filed against Mageia 5. Did it get fixed? If so, please change its status to RESOLVED - FIXED. If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It continued to get limited extended support since then, but that support has now ended, too. As a result we are closing this bug report as OLD. If you still see this issue in a newer Mageia version, then please reopen this report and say so. ==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==
CC: (none) => marja11Status: NEW => RESOLVEDResolution: (none) => OLD