Red Hat Bugzilla – Bug 458138
anaconda switches the sda and sdb names
Last modified: 2010-06-17 22:54:24 EDT
Description of problem:
as reported here
drive names are not consistent to the bios order, and they are not even consistent between reboots.
in bios, the first is the PATA hard disk and the second is the SATA harddisk.
same thing i've seen in x86 and x86_64.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.boot one livecd
2.start the installer
the drive order is sometimes changed and different from the bios order as well as the installed fedora order.
drive order is always the same with the bios order.
As mentioned in other bug reports, this isn't really a bug. There's no way for the drive order to be consistently detected.
tha's not exactly computer science, imho.
where is the limit coming from? kernel or bios?
i don't understand why the drive order can not be consistently detected.
Hi Cornel, I won't claim to be a computer scientist, but according to Chris Lumens from your bug 431638: "We get the drives in the order we get them from the underlying kernel and hardware detection layers, and that order is not guaranteed to be consistent across reboots."
I don't know how the HAL works either so I can't give you much better of an answer. However, what are you trying to do that this is causing you problems?
However, what are you trying to do that this is causing you problems?
i am trying to install fedora, sometimes (alfa,beta,rc,release,etc).
you can find the details in the old reports.
the problem i see here (except the lack of available time to fix the bug) is that fedora+"standard" pc-compatible-hardware is a system wich behaves randomly: starting always from the same state, we can not predict the next state. maybe the bios/mobo manufacturers are not perfect but i believe that the main unpredictable system is the linux kernel (or maybe anaconda?). however, it's just a belief, only i've not found a better explanation for the inconsistency _before_ install versus the consistency after install of fedora .....
meanwhile it seems that the same bug affects some other distros, like ubuntu:
they pretend to have fixed it.
just a thing i've noticed: i've added another disk drive to my system (the second sata) and, sometimes, the installed fedora (13, now, and 12 previously) uses (R)another disk order. hence, my partitions (/dev/sdX) are no longer mounted and, this is interesting, it seems that i no longer have the hibernate option when selecting shutdown from the menu. same thing happened when there was only one pata and one sata disk drive in the computer. i wonder why these two things go together ...
(In reply to comment #5)
> just a thing i've noticed: i've added another disk drive to my system (the
> second sata) and, sometimes, the installed fedora (13, now, and 12 previously)
> uses (R)another disk order. hence, my partitions (/dev/sdX) are no longer
That's why we use mount-by-UUID:
UUID=93b5994b-1fa1-4474-a875-d7316b2b04dd /boot ext3 defaults 1 2
You can also try to load the edd driver which will tell you what devices correspond to which PCI slots, if your BIOS supports EDD properly.