Description of problem: Got an upgrade message for the Kernel, but on rebooting, it panics and does not boot the system. Old Kernel: 3.10.24-2 New Kernel: 3.10.28-1 For x86_64 After the boot loader, the booting Linux page says "error: file 'initrd-desktop.img' not found. Press any key to continue..." Which gets a Kernel panic not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Version-Release number of selected component (if applicable): Kernel desktop 3.10.28-1 How reproducible: Install latest kernel, if uninstalled then re-installed (after required reboots), the problem is the same every time. Reproducible: Steps to Reproduce:
Summary: Kernal 3.10.28-1 update does not install properly => Kernel 3.10.28-1 update does not install properly
can you paste the output of ll /boot and fdisk -l ? (booting on a old kernel should work)
This disc has (only) Mageia on it, rest of drives not relevant to issue. Disk /dev/sdd: 240.1 GB, 240057409536 bytes, 468862128 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x2128bbc5 Device Boot Start End Blocks Id System /dev/sdd1 * 2048 16370234 8184093+ 83 Linux /dev/sdd2 16373700 103394339 43510320 5 Extended /dev/sdd5 16373760 22507064 3066652+ 82 Linux swap / Solaris /dev/sdd6 22509568 83939624 30715028+ 83 Linux /dev/sdd7 83943424 94173029 5114803 83 Linux /dev/sdd8 94175232 102350114 4087441+ 83 Linux /dev/sdd9 102352896 103394339 520722 83 Linux total 23620 -rw-rw-r-- 1 root root 440 Mar 16 2013 boot.backup.sda lrwxrwxrwx 1 root root 29 Feb 9 22:03 config -> config-3.10.24-desktop-2.mga3 -rw-r--r-- 1 root root 144521 Dec 13 20:35 config-3.10.24-desktop-2.mga3 -rw-r--r-- 1 root root 144490 Feb 1 16:16 config-3.10.28-desktop-1.mga3 drwxr-xr-x 2 root root 1024 May 5 2013 dracut/ -rwxr-xr-x 1 root root 549888 May 23 2013 gfxmenu* drwxr-xr-x 6 root root 1024 Feb 9 22:01 grub2/ -rw------- 1 root root 9930844 Dec 19 10:34 initrd-3.10.24-desktop-2.mga3.img lrwxrwxrwx 1 root root 33 Feb 9 22:01 initrd-desktop.img -> initrd-3.10.28-desktop-1.mga3.img drwx------ 2 root root 12288 Mar 16 2013 lost+found/ -rw-r--r-- 1 root root 197480 Dec 13 20:35 symvers-3.10.24-desktop-2.mga3.xz -rw-r--r-- 1 root root 197504 Feb 1 16:16 symvers-3.10.28-desktop-1.mga3.xz lrwxrwxrwx 1 root root 33 Dec 21 09:00 System.map -> System.map-3.10.24-desktop-2.mga3 -rw-r--r-- 1 root root 2775606 Dec 13 20:35 System.map-3.10.24-desktop-2.mga3 -rw-r--r-- 1 root root 2775908 Feb 1 16:16 System.map-3.10.28-desktop-1.mga3 -rw-r--r-- 1 root root 3725984 Dec 13 20:35 vmlinuz-3.10.24-desktop-2.mga3 -rw-r--r-- 1 root root 3724592 Feb 1 16:16 vmlinuz-3.10.28-desktop-1.mga3 lrwxrwxrwx 1 root root 30 Feb 9 22:01 vmlinuz-desktop -> vmlinuz-3.10.28-desktop-1.mga3
I think I found the problem, but it's not something I can fix. in /boot/ partition, The old kernel exists as: initrd-3.10.24-desktop-2.mga3.img (a 9.5MB file) There is NO file for the latest kernel, that is, there's NO: initrd-3.10.28-desktop-1.mga3.img The problem is reproducable every time you try to install the latest (3.10.28-desktop-1) kernel.
Priority: Normal => High
Found a method to create an image file, but did not help the boot which still kernel paniced. While the kernel install did not create the image file, strangely removing the kernel did remove the image file that my using mkinitrd created. > mkinitrd /boot/initrd-3.10.28-desktop-1.mga3.img 3.10.28-desktop-1.mga3 I: dracut module 'network' will not be installed, because it's in the list to be omitted! I: dracut module 'network' will not be installed, because it's in the list to be omitted! I: *** Including module: bootchart *** dracut-install: ERROR: installing 'accton' E: /usr/lib/dracut/dracut-install -D /var/tmp/initramfs.ot3tEk -a bootchartd bash /lib/bootchart/bootchart-collector /etc/bootchartd.conf accton echo grep usleep I: *** Including module: dash *** I: *** Including module: i18n *** I: *** Including module: drm *** I: *** Including module: plymouth *** I: *** Including module: kernel-modules *** I: *** Including module: resume *** I: *** Including module: rootfs-block *** I: *** Including module: terminfo *** I: *** Including module: udev-rules *** I: *** Including module: usrmount *** I: *** Including module: base *** I: *** Including module: fs-lib *** I: *** Including module: shutdown *** I: *** Including modules done *** I: *** Installing kernel module dependencies and firmware *** I: *** Installing kernel module dependencies and firmware done *** I: *** Resolving executable dependencies *** I: *** Resolving executable dependencies done*** I: *** Stripping files *** I: *** Stripping files done *** I: *** Creating image file *** I: *** Creating image file done *** I: Wrote /boot/initrd-3.10.28-desktop-1.mga3.img: I: -rw------- 1 root root 9794915 Feb 17 00:12 /boot/initrd-3.10.28-desktop-1.mga3.img
I noticed there was a new kernel available, so tried to install it, hoping that it would install successfully and bypass the one that started this original bug report, but the install created the EXACT SAME problems as the original bug report. Any suggestions, something has been changed in compile that is causing this problem, for two kernels now. Latest kernel attempted to install is 3.10.40-desktop-1.mga3
Summary: Kernel 3.10.28-1 update does not install properly => Kernel 3.10.40-desktop-1 does not install properlySource RPM: Kernel 3.10.28-1 => 3.10.40-desktop-1.mga3
Please check ll /boot again and ensure the relevant symlinks point to the correct kernel version. From comment 2 it appears you have.. System.map -> System.map-3.10.24-desktop-2.mga3 When the rest point to 3.10.28. Of course with the newer kernel it should link to that one instead.
CC: (none) => eeeemail, tmb
Also config -> config-3.10.24-desktop-2.mga3
OK, I tried your suggestions, and it worked, but after following this method, and the bug still stands as it should all be done automatically on install, not messing around in the bash prompt. I removed all the kernels etc that did not install, as mentioned in this bug. I then installed the latest one (3.10.40-desktop-1.mga3), but it did NOT create a initrd file in /boot, so I had to create that first using.. mkinitrd /boot/initrd-3.10.40-desktop-1.mga3.img 3.10.40-desktop-1.mga3 Then I looked at your suggesions in comment 6 to change the symlinks which were all pointing to the current kernel I was running (3.10.28) .. to 3.10.40. I then checked using "grub-customiser" as root, the boot entries for the kernel (removing an entry for "RESUME UUID" in Linux which was pointing to linux-swap partition (which I disabled months earlier). On reboot, the system then booted to the newest kernel (3.10.40). So despite me having the new kernel running, the install of the new kernel (I did via MCC) did not install everything automatically. I have not found out why this is the case. I will leave this bug open if there is anything to test, if not, you may close it as the new kernel is running for a few days without problems. Thanks for your help Claire.
Thomas, any idea what may have caused the /boot symlinks to get out of sync? If there is no obvious cause we can probably close the bug and ask DariuszSki to reopen it if the same occurs with the next kernel update.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD