Bug 458138
Summary: | anaconda switches the sda and sdb names | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | cornel panceac <cpanceac> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | medium | ||
Version: | 13 | CC: | quantumburnz |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-18 02:54:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
cornel panceac
2008-08-06 16:40:07 UTC
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. thnx 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? [quote] However, what are you trying to do that this is causing you problems? [/quote] 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: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/8497 they pretend to have fixed it. thanks. 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 > mounted 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. |