On Fri, Nov 18 2016, Andy Smith wrote: > > Am I right in thinking this is not incremental assembly by udev, but > kernel auto-assembly? That isn't kernel auto-assembly, but it doesn't look like incremental assembly either. /usr/share/initramfs-tools/scripts/local-block/mdadm runs mdadm -q --assemble --scan --no-degraded to start all the arrays that the initramfs can find. So it is mdadm-based auto-assembly. > > Also, in the previous configuration, mpt3sas was being loaded once > the root filesystem had been mounted. All the drives on the SAS > controller were then available, so udev should have assembled md5 at > that point, right? So I think there is still a problem here, just > one which I have worked around in some other way. Yes, I think there is still a problem. When the mpt3sas is loaded udev should trigger the arrays to be created. > > If that is the case, would you like me to continue debugging udev? Up to you, but I have an idea. The udev rules files depends on 'blkid' having been run. /lib/udev/rules.d/60-persistent-storage.rules does this, but not for KERNEL=="fd*|mtd*|nbd*|gnbd*|btibm*|dm-*|md*|zram*|mmcblk[0-9]*rpmb" ... though that wouldn't apply to you. what does udevadm info /dev/sdc report? NeilBrown
Attachment:
signature.asc
Description: PGP signature
