Version-Release number of selected component (if applicable): $ mdadm --version mdadm - v4.2 - 2021-12-30 $ uname -r 6.2.0-0.rc1.20221230gitbff687b3dad6.15.fc38.x86_64 Steps to Reproduce: $ sudo mdadm --create /dev/md/test --run --level=container --metadata=ddf --raid-devices=2 /dev/sdb /dev/sdc -v mdadm: size set to 479232K mdadm: ADD_NEW_DISK for /dev/sdb failed: Invalid argument from journal: Jan 06 12:06:25 fedora kernel: md: could not open device unknown-block(8,16). Additional info: We hit this issue in libblockdev[1] test suite and this is on a system without real BIOS RAID support so it is possible this a cause behind this issue, but it works on older versions of Fedora. [1] https://github.com/storaged-project/libblockdev
I can both create and activate the DDF array on Fedora 37 with the same version of mdadm so I am moving this to kernel. I've also change the title since the DDF container can be created on F37 but cannot be activated on F38 # mdadm --assemble --scan mdadm: failed to add /dev/sdc to /dev/md/ddf: Invalid argument mdadm: failed to add /dev/sdb to /dev/md/ddf: Invalid argument mdadm: Container /dev/md/ddf has been assembled with 0 drives (out of 2) mdadm: timeout waiting for /dev/md/ddf from journal: Jan 23 09:15:14 fedora kernel: md: could not open device unknown-block(8,16). Jan 23 09:15:14 fedora kernel: md: could not open device unknown-block(8,32). Jan 23 09:15:14 fedora kernel: md: md127 stopped. Jan 23 09:15:14 fedora kernel: block device autoloading is deprecated and will be removed. I am also raising the severity because it is blocking the F38 change[1] to switch from dmraid to mdadm for BIOS RAID support. [1] https://fedoraproject.org/wiki/Changes/UseMdadmForBIOSRAIDInAnaconda
This now works with the latest kernel 6.2.0-0.rc5.20230125git948ef7bb70c4.40.fc38.x86_64 in today Fedora.