Greetings! I have a Gigabyte motherboard: https://www.gigabyte.com/Motherboard/Q670M-D3H-DDR4-rev-10#kf With a 12th gen Intel processor: https://ark.intel.com/content/www/us/en/ark/products/134591/intel-core-i712700-processor-25m-cache-up-to-4-90-ghz.html Which I've set up to use dual NVMe drives as IMSM RAID via VMD. And I seem to have run into: https://bugzilla.redhat.com/show_bug.cgi?id=2053593 As I understand it, mdadm is ignoring any IMSM RAID arrays that don't all come from the same SATA controller in order to avoid users accidentally creating such arrays with a selection of devices where they can't manage it via the BIOS menus. Up to now that was sensible. Unfortunately, VMD now lets non-SATA drives use features that used to be SATA only. So systems with NVMe drives can use all the BIOS features for them, including the RAID configuration and monitoring. But then mdadm sees that the drives aren't on a SATA controller and deliberately ignores them. For now I have hacked the workaround from that Redhat bug report into my initramfs (IMSM_NO_PLATFORM=1), but I expect this kind of configuration to get more common in the future. So perhaps it would be a good idea to make using them a little more intuitive. So since I don't manage to find any sign of the upstream bug report mentioned by the Redhat user actually having been filed I'm going to mention it now and ask if there are any plans for what to do with this in future versions. LMP
