Bug 2280699 - Some software RAID arrays incorrectly assembled on boot after Fedora 40 upgrade
Summary: Some software RAID arrays incorrectly assembled on boot after Fedora 40 upgrade
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mdadm
Version: 40
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jonathan Wright
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-05-15 19:21 UTC by Chris Siebenmann
Modified: 2025-05-20 08:44 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-05-20 08:44:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Chris Siebenmann 2024-05-15 19:21:04 UTC
I have a pair of HDDs in my system (among other disks) that are used for four mirrored software RAID arrays. The HDDs are GPT partitioned and because the software RAID arrays are old, they use 0.90 format superblocks. In Fedora 39, all software RAID arrays assembled properly on boot, which is good because one holds a LVM logical volume. After an upgrade to Fedora 40, the arrays do not assemble correctly in a dangerous way.

The working configuration is (from /proc/mdstat):
md50 : active raid1 sdd1[1] sdc1[0]
      4891648 blocks [2/2] [UU]
      
md52 : active raid1 sdd3[1] sdc3[0]
      4891648 blocks [2/2] [UU]
      
md51 : active raid1 sdd2[1] sdc2[0]
      20514880 blocks [2/2] [UU]
      
md53 : active raid1 sdd4[1] sdc4[0]
      2878268800 blocks [2/2] [UU]
      bitmap: 0/22 pages [0KB], 65536KB chunk

The incorrect assembly has 'md53' on 'sdc' and 'sdd' (the *whole disks*), no other software RAID arrays, and no /dev/sd[cd]* partitions visible in /dev. md53 is the software RAID array with my LVM logical volume on it, but the logical volume was not seen. Stopping the incorrectly assembled md53 and using partprobe on sdc and sdd caused all four RAID arrays to be correctly assembled and the LVM volume to be brought up.

The kernel definitely sees the sdc and sdd partitions on boot. I can't see any messages logged about this in journalctl. Other disks on this system have other software RAID arrays with superblock formats 1.0 and 1.2, and they were correctly assembled. However, none of them are on partitions that are at the end of the disk.

I am guessing that this is mdadm instead of udev or some other system component that may be involved in boot time software RAID assembly, so I may be wrong about the component.

Reproducible: Always

Steps to Reproduce:
Well, it happened on several boots as I tried to make the system stop hanging on boot because it couldn't find old filesystems on the old LVM volume, and then one final time when the system booted all of the way up and I could actually examine things in a decent environment.

Comment 1 Aoife Moloney 2025-04-25 10:44:27 UTC
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '40'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 40 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Aoife Moloney 2025-05-20 08:44:01 UTC
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 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 Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.