This is basically a bug in the installer, IMO. The only thing that orders the drives is the order that the drivers were loaded (something the kernel has no control over).
The difference is that the installer loads in a different order than udev. This inconsistency has been shown before, so this bug is probably a duplicate. From what I can tell, the installer needs to more closely match what udev does.
This is basically a bug in the installer, IMO. The only thing that orders the drives is the order that the drivers were loaded (something the kernel has no control over).
The difference is that the installer loads in a different order than udev. This inconsistency has been shown before, so this bug is probably a duplicate. From what I can tell, the installer needs to more closely match what udev does.