Description of problem: I invoked in a fresh Mageia-6-sta1-x86_64-DVD install the script # bootloader-config --action rebuild-initrds It generates several initrd-files referring to long gone kernels. Version-Release number of selected component (if applicable): How reproducible: I have seen this issue before. It should be reproducible. Best regards, Ulrich Beckmann
Created attachment 7849 [details] Log from testcase
Created attachment 7856 [details] CLI output with rpm -qa, ls -l /boot before and after Confirmed here in a rolling Cauldron installation - see attached.
CC: (none) => zen25000
I cannot reproduce this, but I saw Ulrich has an EFI system, I have legacy BIOS I have 3 kernels (removed about 6 of them earlier today) and get only get initrd images for those three. Besides, the line "Creating: target|kernel|dracut args|basicmodules" only appears once Is there any chance this only happens on EFI systems?
Source RPM: draktools => drakxtoolsCC: (none) => marja11Assignee: bugsquad => thierry.vignaud
Barry, do your grub.cfg list those missing kernels?
Comment on attachment 7849 [details] Log from testcase Those are the kernels of other installation in a multi-boot system, probably extracted from grub.cfg. And not any extinct kernels. Thanks, Marja! Ulrich
(In reply to Thierry Vignaud from comment #4) > Barry, do your grub.cfg list those missing kernels? Update-grub2 output is still the same, finding only the installed kernels and not any of the newly created 'old' initrds Generating grub configuration file ... Found theme: /boot/grub2/themes/maggy/theme.txt Found linux image: /boot/vmlinuz-4.6.0-desktop-1.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-1.mga6.img Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc7.1.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-0.rc7.1.mga6.img Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc6.2.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-0.rc6.2.mga6.img Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc6.1.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-0.rc6.1.mga6.img Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc5.2.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-0.rc5.2.mga6.img Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc5.1.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-0.rc5.1.mga6.img Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc4.1.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-0.rc4.1.mga6.img Found linux image: /boot/vmlinuz-4.4.6-desktop-1.mga6 Found initrd image: /boot/initrd-4.4.6-desktop-1.mga6.img Found linux image: /boot/vmlinuz-4.4.5-desktop-1.mga6 Found initrd image: /boot/initrd-4.4.5-desktop-1.mga6.img Found linux image: /boot/vmlinuz-desktop Found initrd image: /boot/initrd-desktop.img Found Mageia 5 (5) on /dev/sda4 Found Mageia 6 (6) on /dev/sda5 done
What I meant is wether those removed kernels were still listed in grub.cfg _before_ you issued the rebuild command?
Severity: normal => minorKeywords: (none) => NEEDINFOPriority: Normal => Low
Ah, I see your point - I cannot be 100% sure. I remember cleaning out a lot of old kernels a week or so ago, however with the bug that fails to run update-grub on kernel removal still with us, it is just possible that I did not check, or run it manually.
Created attachment 7862 [details] test repeated Hi, Thiery I cleared /boot and repeated the test. Best regards, Ulrich
So it read back grub2 config and tries to build initrds for other distros' kernels...
Summary: Bootloader-config generates stand-alone initramdisk files => Bootloader-config generates stand-alone initramdisk files for other distros (on grub2)
Created attachment 8400 [details] test repeated Just found out that the valid initrds are *not* rebuild. This is a regression, and therefore I set the state to critical. Ulrich
Priority: Low => NormalSeverity: minor => critical
Set severity to "normal". The script obviously is not used in any tools. Users may use the command mkinitrd to recreate their initramfs.
Severity: critical => normal
Keywords: NEEDINFO => (none)
Created attachment 12845 [details] Test on an actual Cauldron system I repeated the test on an actual Cauldron efi system. Note that /boot is located on a btrfs subvolume and LVM, which is inhibited by the Mageia installer. The error message 'Failed to find physical volume "/dev/sda7".' can be neglected, no regression. It shows also in post install script of kernels. /dev/sda7 is a LUKS container. As to the initramdisks, it does absolutely nothing. Regards, Ulrich