Sata drives not detected by 2.6.35.* kernels

For what it is worth, the live-cds work fine and detect sata drives on another computer with a different sata controller.

Problem has been noticed in other kernel versions as well: 2.6.32.21, 2.6.33 and 2.6.35 . Booting with 2 SATA drives fails

Just to add, I am still not having any luck with having my sata drives detected in Maverick up through 2.6.35.11.
I am going to try Alpha 3 soon and will post results.

Installed Maverick Alpha 3 w/2.6.35.14 kernel on a PATA drive, because the Live-CD/USB still would not recognize my SATA drives. Found out that the Silicon Image 3114 controller is recognized, but the drives are not. There is no raid meta-data showing on the drives which I've read can be an issue.

I'm in the process of clearing all data off the drives and will be zeroing the drives clearing the MBR's and running Hitachi Disk Utilities to see if that may provide any useful info. or solution. Any kernel less than 2.6.35.X still recognizes my drives, (i.e. hardy, karmic, lucid) I am at a loss as to what changed with the .35 kernel. Any insight or information regarding this change would be appreciated.

Did what I said above and no change. Only PATA drives being detected.
Next I guess I will try to find another distro using 2.6.35.X kernel and see if this is Ubuntu Maverick specific.

Did an install of 10.10 beta yesterday and it only finds my PATA drives.

My system is based on an inte SE7505VB2 board with a sata_sil controller.

exerpt fro dmesg follows:-

[ 1.060080] sata_sil 0000:05:04.0: version 2.4
[ 1.060161] sata_sil 0000:05:04.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 1.062457] scsi3 : sata_sil
[ 1.062806] scsi4 : sata_sil
[ 1.062987] ata3: SATA max UDMA/100 mmio m512@0xd8401000 tf 0xd8401080 irq 19
[ 1.062996] ata4: SATA max UDMA/100 mmio m512@0xd8401000 tf 0xd84010c0 irq 19
[ 1.063806] FDC 0 is a post-1991 82077
[ 1.067327] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[ 1.067332] e100: Copyright(c) 1999-2006 Intel Corporation
[ 1.067404] e100 0000:05:03.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 1.092236] e100 0000:05:03.0: PME# disabled
[ 1.093455] e100 0000:05:03.0: eth0: addr 0xd8400000, irq 18, MAC addr 00:04:23:88:14:3f
[ 1.354552] e1000 0000:04:02.0: eth1: (PCI:66MHz:32-bit) 00:04:23:88:14:d7
[ 1.354567] e1000 0000:04:02.0: eth1: Intel(R) PRO/1000 Network Connection
[ 1.385544] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 1.385637] ata3.00: NODEV after polling detection
[ 1.410618] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 1.708051] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 1.708148] ata4.00: NODEV after polling detection

shows the ports are being detected but not the drives on them.

I can't boot with kernels 2.6.35-20 or 2.6.35-21

Having to revert to 2.6.32-24.

I am using Silicon Image, Inc. SiI 3114

I've tested the daily iso 9-16-10 and drives still fail to be detected.
The controller is detected and up
from dmesg log
[ 2.376037] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 2.384049] ata1.00: both IDENTIFYs aborted, assuming NODEV
[ 2.556648] forcedeth 0000:00:04.0: ifname eth0, PHY OUI 0x57d @ 1, addr 00:04:4b:80:80:03
[ 2.556714] forcedeth 0000:00:04.0: timirq lnktim desc-v1
[ 2.556900] pata_amd 0000:00:09.0: version 0.4.1
[ 2.556956] pata_amd 0000:00:09.0: setting latency timer to 64
[ 2.557141] scsi4 : pata_amd
[ 2.557312] scsi5 : pata_amd
[ 2.558221] ata5: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
[ 2.558279] ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
[ 2.704035] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 2.712200] ata2.00: both IDENTIFYs aborted, assuming NODEV

from debug log
Sep 17 09:51:51 maverick kernel: [ 2.042014] sata_sil 0000:01:0b.0: version 2.4
Sep 17 09:51:51 maverick kernel: [ 2.042318] alloc irq_desc for 19 on node -1
Sep 17 09:51:51 maverick kernel: [ 2.042320] alloc kstat_irqs on node -1
Sep 17 09:51:51 maverick kernel: [ 2.384049] ata1.00: both IDENTIFYs aborted, assuming NODEV
Sep 17 09:51:51 maverick kernel: [ 2.556900] pata_amd 0000:00:09.0: version 0.4.1
Sep 17 09:51:51 maverick kernel: [ 2.556956] pata_amd 0000:00:09.0: setting latency timer to 64
Sep 17 09:51:51 maverick kernel: [ 2.712200] ata2.00: both IDENTIFYs aborted, assuming NODEV

Still no problems with previous kernels installed or booted from iso.
I have been digging in change logs of all kinds of packages and cannot seem to find the culprit.
What other information can I provide to help track down the cause of this?

I appear to have fixed my problem using this patch.

Building it in my ppa now.

@ Andrew Betts You Sir are a Gentleman, Scholar and a Geek!
The patched kernel in your ppa works like a charm.

All drives detected and functional... Thank You!
Now if this can be incorporated into the main kernel that would be great.
I would like to be able to install onto my SATA drives.

Thanks again.

It is disappointing that a so called 'performance' patch has made the default 10.10 simply not work for me. I'm not sure why it wasn't immediately reverted for the ubuntu release. Upstream has already reverted it.

Perhaps Ubuntu ought to simply ignore patches that only address performance for a release or two.

Just a 'me too' comment, to say that Andrew Betts' patch fixes the issue. I'm now using the kernel from his PPA on a machine that would not boot with the stock kernel (due to using a SiI 3114 Raid array).

Another me too! I have an SiI 3112 controller and Andrew's patch worked for me.

Finally the upstream fix has got into an ubuntu kernel:

https://launchpad.net/ubuntu/maverick/+source/linux/2.6.35-23.36

Hello.
Thanks for that bug hanting and fix and glade to know that it is into ubuntu kernel.
But I have just dist-upgrade to Maverik I am hint by this bug and the 2.6.35-23.36 kernel is not yet in feed.
How can I can do to upgrade to this kernel ? (and/or if you know when it will be in feed..)
Thanks by advance!

Sylvain

This issue was reported a while ago, but comment #20 mentions that updating the Maverick kernel should fix it.
Is anyone still affected by this bug?

Marking Fix Released per comment #20. If this is not the case, feel free to reopen. Thanks.

I think I have a scenario to reproduce this issue in Ubuntu-13.04

I'm trying to upgrade my Toshiba Satellite A135-S2246 laptop, running Windows 7, to Ubuntu-13.04, but my internal SSD (http://www.amazon.com/gp/product/B007ZWLRSU/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1) is not recognized. From dmesg:

[ 9.100085] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 9.100215] ata3.00: NODEV after polling detection

From syslogs:

May 17 07:31:28 ubuntu kernel: [ 9.100085] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May 17 07:31:28 ubuntu kernel: [ 9.100215] ata3.00: NODEV after polling detection

Please note I've already tried installing 10.04, 10.10, & 12.10 with same results. Let me also note that SSD is brand new and Windows-7 installation from scratch works perfectly fine.

I have this problem with Sandisk SSD on a 2 port SATA/PCI card. Works fine with a standard SATA drive but fails with the above error with the SSD. Ubuntu 14.04.1 32-bit.

Hi, I've got the same problem like Paul. Ubuntu 14.04.1 32-bit, laptop with ATI 4379 Serial ATA Controller (designed by Silicon Image) and a SanDisk SSD.
I already inserted a SiI3512A in a Desktop-PC with the same results, HDD works fine, SSD can't be accessed in any way.
My Thread on ubuntuusers.de: http://forum.ubuntuusers.de/topic/ubuntu-14-04-1-kann-nicht-auf-ssd-installiert-/ where I posted all details I've tried.