Disk device order wrong - Grunty beta

Bug #146599 reported by syg00
8
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

BIOS/grub see IDE disk as zero, SATA as disk one. Grunty AMD64 beta reverses this order - SATA as /dev/sda, IDE as /dev/sdb. udev rules issue maybe ???
This causes grub-install to fail during install. If corrected at this point, menu.lst is built wrong, and (re-)boot fails.

Archlinux sees the disks in the order expected (IDE=/dev/sda, SATA=/dev/sdb)

Revision history for this message
David Portwood (dzportwood) wrote :

Its Gusty by the way.

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested at [WWW] https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments.

Revision history for this message
syg00 (sginnane) wrote :

D'oh - sorry ...
Attachments as requested.

Revision history for this message
syg00 (sginnane) wrote :
Revision history for this message
syg00 (sginnane) wrote :
Revision history for this message
syg00 (sginnane) wrote :
Revision history for this message
syg00 (sginnane) wrote :
Revision history for this message
syg00 (sginnane) wrote :
Revision history for this message
syg00 (sginnane) wrote :

Maybe I should have mentioned this was the "alternate" CD.

Revision history for this message
Jan Kunder (jan-kunder) wrote :

2 syg:
Next time, save your and our time and do:
cd /tmp; mkdir `mydate`; cd `mydate`;pwd; uname -a > uname-a.log; cat /proc/version_signature > version.log; dmesg > dmesg.log; lspci -vvnn > lspci-vvnn.log; lspci -v > lspci-v.log; cp /var/log/syslog .; cp /var/log/daemon.log . ; tar cvvf ../`mydate`.tar .
*
add in your /etc/zsh/zshrc:
alias mydate="%Y-%m%d_%H%M"
***
2 Ubuntu guys:
Can I ask you why IDE0!=/dev/hda, but=/dev/sda like in Etch? Why all old 20GB IDE/EIDE/PATA drives are sdX not hdX?
When did it change? (Did happen this already in SID? I'm using Gutsy Beta and Debian Etch)

Revision history for this message
Jan Kunder (jan-kunder) wrote :

Next time, save your and our time and do:
cd /tmp; mkdir `mydate`; cd `mydate`;pwd; uname -a > uname-a.log; cat /proc/version_signature > version.log; dmesg > dmesg.log; lspci -vvnn > lspci-vvnn.log; lspci -v > lspci-v.log; cp /var/log/syslog .; cp /var/log/daemon.log . ; tar cvvf ../`mydate`.tar .
*
add in your /etc/zsh/zshrc:
alias mydate="%Y-%m%d_%H%M"
but THIS ^^^^^^^^^^^^^^^^^^^^^^^ is just a workaround.
Can you, please, launchpad guys, add possibility to ATTACH more than one files?
(It may be automatically tarred and gzipped).
*
Why I can not attach report when reporting bug? I need to attach after that in comments.

Revision history for this message
syg00 (sginnane) wrote :

Jan, you might like to note I was specifically asked for the data as separate attachments ...
As for the hda vs. sda change, have a look at the changes for libata at 2.6.19

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Device ordering is not guaranteed since it can be affected by your hardware controllers taking more time on one boot to warm up than on the other.

When you have multiple controllers like this, swapping drive ordering is quite common.

(Laptop users often see the same when their wired and wireless ethernet cards often swap around).

This is why we use UUID= to mount your disks everywhere, so they're located by a property of the filesystem on the disk rather than a transient name.

Changed in udev:
status: Incomplete → Invalid
status: Invalid → Won't Fix
Revision history for this message
Chris Wagner (chris-wagner) wrote :

@Scott: But, isn't the UUID stuff only relevant after grub hands things off to the kernel? It's my understanding that the original reporter's problem is with grub, and how it detects and/or names devices.

I am having this problem, and have had it for some time, but I've not yet upgraded to Gutsy. I'll upgrade and try to remember to report back...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.