Comment 14 for bug 1751813

That order is exactly what happens automatically, so it's not an ordering bug. I suspect it's that the driver is taking more time to detect disks than it used to, and the "workaround" is really just the equivalent of adding a "sleep 10" between modprobe and enumeration. I wonder if something on the kernel side switched from being sync to async and we need to paper over that in userspace.