Hi Neil, On Fri, Nov 18, 2016 at 09:43:44AM +1100, NeilBrown wrote: > Something you could try, after boot and while the arrays are still not > assembled, is > > echo change > /sys/block/sdc/uevent > echo change > /sys/block/sdd/uevent > > That should cause udev to assemble the array. Nothing appeared to happen. There was nothing interesting in syslog or systemd's journal. Here's the output from "udevadm monitor": $ sudo udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[12376.719100] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/host10/port-10:0/end_device-10:0/target10:0:0/10:0:0:0/block/sdc (block) UDEV [12376.722996] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/host10/port-10:0/end_device-10:0/target10:0:0/10:0:0:0/block/sdc (block) KERNEL[12388.329566] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/host10/port-10:1/end_device-10:1/target10:0:1/10:0:1:0/block/sdd (block) UDEV [12388.333441] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/host10/port-10:1/end_device-10:1/target10:0:1/10:0:1:0/block/sdd (block) > If that doesn't work, the looking over the udev logs, and possibly > turning on extra udev logging, might lead to an answer. I don't know how to do that, but I'll look into it - thanks. Cheers, Andy -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
