Kernels 2.6.24 and newer cannot find ide hard disk

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!

Dear Alessio,

I will do so when I get back to that computer, which does not happen
until the next week-end.

Olof

Alessio Igor Bogani wrote:
> 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!
>

Dear Alessio,

Here is the data that you requested. Thanks for looking into this. As
I said, the same error appears both in the i386 kernel and in the amd64
kernel.

staffans@lady:~$ dmesg > dmesg.log
staffans@lady:~$ sudo lspci -vvnn > lspci-vvnn.log
[sudo] password for staffans:
staffans@lady:~$ uname -a
Linux lady 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686
GNU/Linux
staffans@lady:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 10317860 4296308 5497432 44% /
varrun 1037716 168 1037548 1% /var/run
varlock 1037716 0 1037716 0% /var/lock
udev 1037716 60 1037656 1% /dev
devshm 1037716 0 1037716 0% /dev/shm
lrm 1037716 39780 997936 4%
/lib/modules/2.6.24-21-generic/volatile
/dev/sda1 10317828 2059584 7734128 22% /media/hem_sda1
/dev/sda3 10317860 2127772 7665968 22% /media/sda3
/dev/sda6 279024920 249763492 29261428 90% /media/data_sda6
staffans@lady:~$

Alessio Igor Bogani wrote:
> 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!
>

This problem seems to have been solved in the newest interpid kernel
2.6.27. (But that does not make me happy, because my intrepid
installation cannot find the internet.)

Alessio Igor Bogani wrote:
> 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!
>

I forgot to tell that also my kernals 2.6.22 have some problems with the
ide disk: They start up OK if no one of the disks need to be checked.
However, the disk checking program runs very slowly on the ide disk, and
sometimes it even seems to hang. When this happens I start up a 2.6.20
kernel, which does not seem to have this problem. Unfortunately, before
noticing this problem I uninstalled the 2.6.20 kernel in the i368
partition. Fortunately I have one 2.6.20 kernel left in the amd64
partition. (By the way, it is still possible to reinstall a 2.6.20 kernel?)

Alessio Igor Bogani wrote:
> 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!
>

I have now solved this problem by upgrading to intrepid ibix. The new
intrepid kernels have no problems reading the ide disk.

Olof Staffans wrote:
> Public bug reported:
>
> I have a computer with two hard disks, one ide, and one sata, with many
> partitions and different kernels. Windows XP runs fine (from an ide
> partition). I have two active kubuntu partions, one i386, the other
> amd64. Starting from kernels 2.6.24 kubuntu has not been able to
> properly mount the ide hard disk, which makes it impossible to boot the
> amd64 kernel (it is on a partition of the ide disk). I can start the
> i386 with the newer kernel, but then it mounts only those partitions
> that are on the sata disk.
>
> Kernels 2.6.22-14 and below have no problems on either partition.
>
> I suppose that I should dig up data on the motherboard etc, or is this
> data supplied automatically? (This is my first bug report.)
>
> ** Affects: apport
> Importance: Undecided
> Status: New
>

This bug report is being closed due to your last comment regarding this being fixed in Intrepid Ibex release. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.