Anaconda (or libata?) device detection order
Alan Cox wrote:
installed. I can get around this by pointing grub.conf to the UUID of
the disk to which it installed. However, I'm surprised that /dev/sda
seems to be a SATA disk during installation, and a PATA disk during boot.
Any thoughts as to why this might be? What decides the device detection
order? Is it libata or something else?
Module load order. That would imply that your different setups are
loading drivers in a different order which is moving the devices around.
It ought not to matter to grub because grub uses the BIOS interfaces and
the first hard disk the BIOS finds is what defines that interface - at
least as far as finishing loadind grub and hunting for kernels .
It has been my experience, that different version of BIOS determine
which drive controller comes first.
I would happily accept a correction to this proposition.
I do not think that there is any way for anaconda, given the constraints
of libata and the BIOS, to determine if the first drive offered is PATA.
Please, prove me wrong!
fedora-list mailing list
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list