On Tue, 2020-06-23 at 19:17 -0500, Roger Heflin wrote: > The uuid= I believe requires a link that udev creates when the device > gets created and it scans it. That link may or may not be done when > mdadm returns with 0 as that udev/link creating is not in the mdadm > code path. > > > So wait a second before you mount it. In reality it will probably > happen much faster than 1sec. > > > I think the specific udev rule doing it is in > /lib/udev/rules.d/60-persistent-storage.rules and this happens after > udev processes the event when the device shows up. > > the link will be in /dev/disk/by-uuid/ so if once the mdadm exists do > a ls -l against that dir and then sleep a second and do it again > something new will show up. The journal is showing errors from udisksd immediately after the dock starts up from power-down, which may be because the mdadm check is running before the /sys/devices/... files are populated. I've changed the test to search for [UU] in /proc/mdstat to see if that works better. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
