Intrepid: disk drive order changes every boot

[y-man]

I have one PATA and one SATA drives. Both at the first i/f of their kind (IDE is the only/master). In install time GRUB was placed into MBR of SATA drive.
I expect that SATA drives would be devices sda..., and PATA drives would start after the last SATA device. In my case SATA sda, and PATA sdb.
The problem is that, at every boot sda/sdb device name assignment seems randomly flipping around. Approximately 50/50 either way.
My system is fully updated as of Nov 11 2008. Kernel is 2.6.27generic.

For package field: I tried but got '"linux-image-2.6.27-5-generic" does not exist in Ubuntu. Please choose a different package. If you're unsure, please select "I don't know"'.

[Ian Weisser (ian-weisser)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[y-man (yavuz-teksavvy)]

Here is the excerpt from terminal with uname:
yavuz@yoA64x2:~$ uname -a
Linux yoA64x2 2.6.27-8-generic #1 SMP Thu Nov 6 17:33:54 UTC 2008 i686 GNU/Linux

I have attached dmesg.log, and lspci-vvnn.log as requested.

Note that at this instance the drive detection was SATA disk -> sda, PATA disk -> sdb. That is what I think the correct assignment. I will do this again when the assignment is other way around, add the results here.

Thanks.

[y-man (yavuz-teksavvy)]

Today my disk order flipped to PATA->sda, SATA->sdb. As promised here is requested info in this case.yavuz@yoA64x2:~$ yavuz@yoA64x2:~$ uname -a
Linux yoA64x2 2.6.27-8-generic #1 SMP Thu Nov 6 17:33:54 UTC 2008 i686 GNU/Linux

dmsg, and lspci logs are in the new attachment logs_PATA_sda.tar.

Thanks.

[kernel-janitor (kernel-janitor)]

Hi y-man,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/karmic .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 297192

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]