Created attachment 11982 [details] Log Output On Bug 27559, user complained about a system peripheral not been recognized by Mageia operating system but Windows can. It appears that at this time "uname -r" returned "5.1.14-desktop-1.mga7", which as Martin W. pinpointed that is the Classical Iso Installer Kernel. This system appeared to not been updated but user claimed the opposite. $ ls /boot returned: total 46156 -rw-r--r-- 1 root root 218186 Jun 22 2019 config-5.1.14-desktop-1.mga7 -rw-r--r-- 1 root root 236770 Aug 27 15:28 config-5.7.19-desktop-1.mga7 -rw-r--r-- 1 root root 236770 Oct 18 09:20 config-5.7.19-desktop-3.mga7 drwxr-xr-x 2 root root 4096 Mar 26 2019 dracut/ drwxr-xr-x 6 root root 4096 Nov 3 21:58 grub2/ -rw------- 1 root root 13247978 Nov 4 06:15 initrd-5.1.14-desktop-1.mga7.img lrwxrwxrwx 1 root root 32 Nov 3 21:49 initrd.img -> initrd-5.1.14-desktop-1.mga7.img -rw-r--r-- 1 root root 186052 Jun 22 2019 symvers-5.1.14-desktop-1.mga7.xz -rw-r--r-- 1 root root 195324 Aug 27 15:28 symvers-5.7.19-desktop-1.mga7.xz -rw-r--r-- 1 root root 195324 Oct 18 09:20 symvers-5.7.19-desktop-3.mga7.xz -rw-r--r-- 1 root root 3978900 Jun 22 2019 System.map-5.1.14-desktop-1.mga7 -rw-r--r-- 1 root root 4755771 Aug 27 15:28 System.map-5.7.19-desktop-1.mga7 -rw-r--r-- 1 root root 4755463 Oct 18 09:20 System.map-5.7.19-desktop-3.mga7 lrwxrwxrwx 1 root root 29 Nov 3 21:49 vmlinuz -> vmlinuz-5.1.14-desktop-1.mga7 -rw-r--r-- 1 root root 6252928 Jun 22 2019 vmlinuz-5.1.14-desktop-1.mga7 -rw-r--r-- 1 root root 6486112 Aug 27 15:28 vmlinuz-5.7.19-desktop-1.mga7 -rw-r--r-- 1 root root 6483264 Oct 18 09:20 vmlinuz-5.7.19-desktop-3.mga7 [root@localhost ~]# And user said: "That is odd. When I boot using grub, I just select 'mageia' There are the usual options, mageia, mageia recovery (paraphrasing), and windows." Later in this previous report, user mentioned a RAID array on his system: While updating Kernel and RAID array plugged in: See Attachment Log Output. User comment: "the message about /dev/sdb is because I have a 4 disk mdadm raid array. I reported a bug about some tools getting confused by a mdadm raid array. I can pull the drives if needed, because they are in hot swap trays". ----------------------------------------------------------------------------------------- While updating Kernel and RAID array unplugged: He pulled the raid array drives and did it again: urpme kernel-desktop-5.7.19-3.mga7-1-1.mga7 To satisfy dependencies, the following 2 packages will be removed (70MB): kernel-desktop-5.7.19-3.mga7-1-1.mga7.x86_64 kernel-desktop-latest-5.7.19-3.mga7.x86_64 (due to missing kernel-desktop-5.7.19-3.mga7) Remove 2 packages? (y/N) y removing kernel-desktop-5.7.19-3.mga7-1-1.mga7.x86_64 kernel-desktop-latest-5.7.19-3.mga7.x86_64 removing package kernel-desktop-5.7.19-3.mga7-1-1.mga7.x86_64 1/2: removing kernel-desktop-5.7.19-3.mga7-1-1.mga7.x86_64 ########################################## removing package kernel-desktop-latest-5.7.19-3.mga7.x86_64 2/2: removing kernel-desktop-latest-5.7.19-3.mga7.x86_64 ########################################## [root@localhost text]# urpmi kernel-desktop-latest To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Core Updates (distrib3)") kernel-desktop-5.7.19-3.mga7 1 1.mga7 x86_64 kernel-desktop-latest 5.7.19 3.mga7 x86_64 70MB of additional disk space will be used. 62MB of packages will be retrieved. Proceed with the installation of the 2 packages? (Y/n) y $MIRRORLIST: media/core/updates/kernel-desktop-latest-5.7.19-3.mga7.x86_64.rpm $MIRRORLIST: media/core/updates/kernel-desktop-5.7.19-3.mga7-1-1.mga7.x86_64.rpm installing kernel-desktop-5.7.19-3.mga7-1-1.mga7.x86_64.rpm kernel-desktop-latest-5.7.19-3.mga7.x86_64.rpm from /var/cache/urpmi/rpms Preparing... ########################################## 1/2: kernel-desktop-latest ########################################## 2/2: kernel-desktop-5.7.19-3.mga7 ########################################## Creating: target|kernel|dracut args|basicmodules remove-boot-splash: Format of /boot/initrd-5.7.19-desktop-3.mga7.img not recognized You should restart your computer for kernel-desktop-5.7.19-3.mga7 /boot looks ok now: ls -l /boot total 60212 -rw-r--r-- 1 root root 218186 Jun 22 2019 config-5.1.14-desktop-1.mga7 -rw-r--r-- 1 root root 236770 Aug 27 15:28 config-5.7.19-desktop-1.mga7 -rw-r--r-- 1 root root 236770 Oct 18 09:20 config-5.7.19-desktop-3.mga7 drwxr-xr-x 2 root root 4096 Mar 26 2019 dracut/ drwxr-xr-x 6 root root 4096 Nov 5 08:06 grub2/ -rw------- 1 root root 13247978 Nov 4 06:15 initrd-5.1.14-desktop-1.mga7.img -rw------- 1 root root 14390205 Nov 5 08:06 initrd-5.7.19-desktop-3.mga7.img lrwxrwxrwx 1 root root 32 Nov 5 08:06 initrd-desktop.img -> initrd-5.7.19-desktop-3.mga7.img lrwxrwxrwx 1 root root 32 Nov 5 08:06 initrd.img -> initrd-5.7.19-desktop-3.mga7.img -rw-r--r-- 1 root root 186052 Jun 22 2019 symvers-5.1.14-desktop-1.mga7.xz -rw-r--r-- 1 root root 195324 Aug 27 15:28 symvers-5.7.19-desktop-1.mga7.xz -rw-r--r-- 1 root root 195324 Oct 18 09:20 symvers-5.7.19-desktop-3.mga7.xz -rw-r--r-- 1 root root 3978900 Jun 22 2019 System.map-5.1.14-desktop-1.mga7 -rw-r--r-- 1 root root 4755771 Aug 27 15:28 System.map-5.7.19-desktop-1.mga7 -rw-r--r-- 1 root root 4755463 Oct 18 09:20 System.map-5.7.19-desktop-3.mga7 lrwxrwxrwx 1 root root 29 Nov 5 08:06 vmlinuz -> vmlinuz-5.7.19-desktop-3.mga7 -rw-r--r-- 1 root root 6252928 Jun 22 2019 vmlinuz-5.1.14-desktop-1.mga7 -rw-r--r-- 1 root root 6486112 Aug 27 15:28 vmlinuz-5.7.19-desktop-1.mga7 -rw-r--r-- 1 root root 6483264 Oct 18 09:20 vmlinuz-5.7.19-desktop-3.mga7 lrwxrwxrwx 1 root root 29 Nov 5 08:06 vmlinuz-desktop -> vmlinuz-5.7.19-desktop-3.mga7 Links to good new Kernel appear to be updated.
@Jeff, Can you provide these files: /etc/fstab
Keywords: (none) => NEEDINFO
/etc/fstab: # Entry for /dev/sda5 : UUID=c33317eb-1f71-4c61-ab6d-0238cc2a4aef / ext4 relatime,acl 1 1 # Entry for /dev/sda3 : UUID=66F02E2AF02E00C3 /media/win_ ntfs-3g defaults,nofail,umask=000 0 0 # Entry for /dev/sda2 : UUID=DCF060DEF060C07E /media/win_d ntfs-3g defaults,nofail,umask=000 0 0 none /proc proc defaults 0 0 /dev/md/FileOne:alpha /data ext4 acl,relatime,nofail 1 3 There was no newline at the end of the file; I added one just now. Also, here is my mdadm.conf file: PROGRAM /usr/sbin/mdadm-syslog-events ARRAY /dev/md/FileOne:alpha level=raid5 num-devices=4 metadata=1.2 name=FileO ne:alpha UUID=931da4a4:152ea3c3:f93d4cb2:867d2601 devices=/dev/sdb,/dev/sdc,/dev/sdd,/dev/sde
Hi, thanks for reporting this bug. Assigned to the maintainers. CC'd Mageia Tools group. (Please set the status to 'assigned' if you are working on it)
Assignee: bugsquad => kernelKeywords: NEEDINFO => TriagedSource RPM: (none) => mdadm-4.1-5.mga8.src.rpmCC: (none) => mageiatools
Source RPM: mdadm-4.1-5.mga8.src.rpm => mdadm-4.1-4.mga7.src.rpm
The root cause is the same as bug 26707. fsedit::get_hds() fails with a fatal error when inspecting the mdadm array. This causes /sbin/bootloader-config to exit with an error, which means the remaining kernel post-install actions are not executed.
Source RPM: mdadm-4.1-4.mga7.src.rpm => drakxtools-18.21-1.mga7.src.rpmAssignee: kernel => mageiatoolsSee Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=26707CC: mageiatools => kernel, mageia
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi bug reporter and hi assignee and others involved, Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly. This report is being closed as OLD because it was filed against Mageia 7, for which support ended on June 30th 2021. Thanks, Marja
Status: NEW => RESOLVEDResolution: (none) => OLD