SATA not recognized by Hardy

[Dan Lambert]

Motherboard is an ASUS M2R23 with an AMD 580X Crossfire chipset. During reboot after network upgrade from Feisty to Hardy Beta, system hangs and can not locate SATA drives.

Tried installing from Hardy Beta LiveCD, and same effect. Turned off splash and quiet options, and messages indicate that the IDE DVD is found, but the kernel is unable to initialize the SATA drives.

I have a digital photo of the screen, but it appears to be too large to upload to launchpad.

[Dan Lambert (danlambert)]

Minor typo in my previous post. The motherboard is an ASUS M2R32, not M2R23.

[Leann Ogasawara (leannogasawara)]

Hi Dan,

Would you maybe be able to write down the exact messages you are seeing when you remove the "quiet" and "splash" boot options? Also maybe try booting with "all_generic_ide" and see if that helps? Thanks.

[Dan Lambert (danlambert)]

The messaging scrolls by so quickly that I'm having a hard time
capturing enough of the messages exactly as presented to be of value.
I'll work on getting that done ASAP, though.

Removing the "quiet" and "splash" options, and replacing them with
"all_generic_ide" doesn't change a thing. I get exactly the same type of
failure, and it appears to be the same messaging.

As soon as I can capture enough of the messaging to be useful, I'll post
that.

Dan

On Fri, 2008-04-04 at 22:55 +0000, Leann Ogasawara wrote:
> Hi Dan,
>
> Would you maybe be able to write down the exact messages you are seeing
> when you remove the "quiet" and "splash" boot options? Also maybe try
> booting with "all_generic_ide" and see if that helps? Thanks.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>

[leach (leach17)]

I have the same chipset (AMD 580X Crossfire) and am experiencing the same problem. Both the i386 and x64 versions of the live cd don't detect the SATA drives connected. My motherboard is an Elitegroup KA3-MVP.

[Kevin_b_er (ktbvz2)]

After you end up in the BusyBox terminal, can you try "dmsg | more" without quotes. Just press Enter to scroll downward until you reach the errors about SATA to see what they are.

[leach (leach17)]

Here's the relevant output of dmesg | more

ata1: SATA max UMDA/13 abar m12@0xfe0f00 port 0xfe0f10 irq 58
ata2: SATA max UMDA/13 abar m12@0xfe0f00 port 0xfe0f10 irq 58
ata3: SATA max UMDA/13 abar m12@0xfe0f00 port 0xfe0f20 irq 58
ata4: SATA max UMDA/13 abar m12@0xfe0f00 port 0xfe0f20 irq 58
ata1: SATA link up 3.0 Gbps (SStatus 13 SControl 30)
ata1.0: qc timeout (cmd 0xec)
ata1.0: failed to identify (I/O error, errmask=0x4)
ata1: failed to recover some devies, retrying in 5secs
ata1: SATA link up 3.0 Gbps (SStatus 13 SControl 30)
ata1.0: qc timeout (cmd 0xec)
ata1.0: failed to identify (I/O error, errmask=0x4)
ata1: failed to recover some devies, retrying in 5secs
ata1: SATA link up 3.0 Gbps (SStatus 13 SControl 30)
ata1.0: qc timeout (cmd 0xec)
ata1.0: failed to identify (I/O error, errmask=0x4)
ata1: failed to recover some devies, retrying in 5secs
ata1: SATA link up 3.0 Gbps (SStatus 13 SControl 30)
ata2: SATA link up 1.5 Gbps (SStatus 13 SControl 30)
ata2.0: qc timeout (cmd 0xec)
ata2.0: failed to identify (I/O error, errmask=0x4)
ata2: failed to recover some devies, retrying in 5secs
ata2: SATA link up 1.5 Gbps (SStatus 13 SControl 30)
ata2.0: qc timeout (cmd 0xec)
ata2.0: failed to identify (I/O error, errmask=0x4)
ata2: failed to recover some devies, retrying in 5secs
ata2: SATA link up 1.5 Gbps (SStatus 13 SControl 30)
ata2.0: qc timeout (cmd 0xec)
ata2.0: failed to identify (I/O error, errmask=0x4)
ata2: failed to recover some devies, retrying in 5secs
ata2: SATA link up 1.5 Gbps (SStatus 13 SControl 30) ================================30
ata3: SATA link down (SStatus 0 SControl 30)
ata4: SATA link down (SStatus 0 SControl 30)
ACPI: PCI Interrupt 00:0:0.[A] -> GSI 1 (level, low) -> IRQ 1
ahci 00:0:0.0: AHCI 00.00 3 slots 2 ports 3 Gbps 0x3 imp1 SATA mode
ahci 00:0:0.0: flags: 6bit ncq pm led clo pmp pio slum part
PCI: Setting latency timer of device 00:0:0.0 to 6
scsi4: ahci
scsi5: ahci
ata5: SATA max UMDA/13 abar m89@0xfdbfe00 port 0xfdbfe10 irq 1
ata6: SATA max UMDA/13 abar m89@0xfdbfe00 port 0xfdbfe10 irq 1
ata5: SATA link down (SStatus 0 SControl 30)
ata6: SATA link down (SStatus 0 SControl 30)
ACPI: PCI Interrupt 00:1:0.[A] -> GSI 1 (level, low) -> IRQ 1

[leach (leach17)]

I just noticed a typo, ignore '================================30'

[Dan Lambert (danlambert)]

That pretty closely approximates mine. Same messaging, with very few
variations. I think that's mostly due to the specific hardware that it's
loading on.

I built another computer using an MSI K9A Platinum (MS-7280 v 1.0)
mainboard, using one of the BE2300 AMD cpus, and it loaded and ran 8.04
with no problems. The only issue I had was that it wouldn't load GRUB,
and I ended up having to use LILO instead.

Dan

[Leann Ogasawara (leannogasawara)]

Care to test the Intrepid Ibex 8.10 kernel? It was most recently rebased with the upstream 2.6.25 kernel (which contains the patch you've referenced) and is currently available in the following PPA:\n\nhttps://edge.launchpad.net/~kernel-ppa/+archive\n\nIf you are not familiar with how to install packages from a PPA basically do the following . . .\n\nCreate the file /etc/apt/sources.list.d/kernel-ppa.list to include the following two lines:\n\ndeb http://ppa.launchpad.net/kernel-ppa/ubuntu hardy main\ndeb-src http://ppa.launchpad.net/kernel-ppa/ubuntu hardy main\n\nThen run the command:\n\nsudo apt-get update\n\nYou should then be able to install the linux-image-2.6.25 kernel package. After you've finished testing you can remove the kernel-ppa.list file and run 'sudo apt-get update' once more. Please let us know your results. Thanks.

[Leann Ogasawara (leannogasawara)]

bah, sorry for the bad formatting, let me try that again:

Care to test the Intrepid Ibex 8.10 kernel? It was most recently rebased with the upstream 2.6.25 kernel (which contains the patch you've referenced) and is currently available in the following PPA:

https://edge.launchpad.net/~kernel-ppa/+archive

If you are not familiar with how to install packages from a PPA basically do the following . . .

Create the file /etc/apt/sources.list.d/kernel-ppa.list to include the following two lines:

deb http://ppa.launchpad.net/kernel-ppa/ubuntu hardy main
deb-src http://ppa.launchpad.net/kernel-ppa/ubuntu hardy main

Then run the command:\n\nsudo apt-get update\n\nYou should then be able to install the linux-image-2.6.25 kernel package. After you've finished testing you can remove the kernel-ppa.list file and run 'sudo apt-get update' once more. Please let us know your results. Thanks.

[Billy Kwong (tuppa)]

I have the same problem on an ASUS A8V-MX motherboard. Tried the 2.6.25 kernel from the PPA above as well, but same error occurs.

[Jordan (jordanroy)]

Same problem here for the ASUS A8V-MX, with 250GB SATA drive.

[js1 (sujiannming)]

Using the Asus A8V-MX as well. Worked without any issues with the Gutsy kernel. But, Hardy kernel is having a lot of problems with ata1. Trying "irqpoll" on the kernel boot option did not help.

ata1: SATA link up 3.0 Gbps (SStatus 13 SControl 30)
ata1.0: qc timeout (cmd 0xec)
ata1.0: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1: failed to recover some devices, retrying in 5 secs

That repeats three times before moving on to ata[2-4] where it recognizes quickly the SATA link is down. Eventually I get dumped into the (initramfs) prompt.

Strange that the newer release is less functional than the prior.

[Servilio Afre Puentes (servilio)]

Another ASUS A8V-MX motherboard, same issue. Tried stock 2.6.25.4 kernel before starting searching in internet for the problem, but didn't change the situation.

[PaulAntoine (pma-launchpad)]

I can confirm the same error on my Gigabyte EP35DS3R with ICH9 and JMicron JMB386 sata controllers. Searching the web shows the same errors with multiple drive types and motherboards since at least 2.6.24.

I have done extensive testing (my client is getting grumpy as they need their 8TB server) and believe it has something to do with NCQ. I have yet another 4 hour test underway and will report back.

I'm running Hardy AMD64 - 2.6.24-17 and 2.6.24-18 show no difference.

Paul
Western Australia

[Moraes Junior (moraesjunior)]

Same problem here for the ASUS A8V-MX, with 250GB SATA drive, like Jordan.
I have an 40GB ATA drive with the system installed, so I can boot. I was Using the sata with an external USB case without problem, but I need to put inside (to increase the speed) and neither the partition editor (gparted) can see that. Only the ata HD (sda).

[Moraes Junior (moraesjunior)]

Let me explain better:
with sata connected, to haryd boot get reeealy slow! And after booting there is no sata device.
So I did try to boot with those options:
all_generic_ide noapic pci=nomsi irqpoll

The boot is normal again, but still not recognizing sata.

[btherio (btherio)]

I'm having this exact problem on an asus a8v-mx.
I read here: http://lkml.org/lkml/2008/3/18/103
I changed sata to ahci in the bios, added only the line pci=nomsi to the kernel boot line, and it seems to be working.

[sebastien teyssier (steyssier)]

Can you identify your sata controller (lspci -vvnn)
SATA controller: VIA Technologies, Inc. VT8251 AHCI/SATA 4-Port Controller
I think it is a duplicate from : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/190492

[Stefan Bader (smb)]

It would be highly appreciated if (lspci -vvnn) would be supplied. There has been a fix for certain revisions of MCP65 upstream which should be in Intrepid alpha2.

commit e297d99e103f951a71fcb1534f1ff3480dd3a851
Author: Tejun Heo <email address hidden>
Date: Tue Jun 10 00:13:04 2008 +0900

    ahci: workarounds for mcp65

    MCP65 ahci can do NCQ but doesn't set the CAP bit and rev A0 and A1
    can't do MSI but have MSI capability. Implement AHCI_HFLAG_YES_NCQ
    and apply appropriate workarounds.

    Signed-off-by: Tejun Heo <email address hidden>
    Cc: Peer Chen <email address hidden>
    Signed-off-by: Jeff Garzik <email address hidden>

[btherio (btherio)]

This is my output of 'lspci -vvnn'. I hope it's not kernel specific; I might have been running a kernel that worked.

[Stefan Bader (smb)]

This at least shows this is about a vt8251 and the above patch doesn't help. I found at least two bugzilla reports that seem to go into the same direction but without a final resolution.
http://bugzilla.kernel.org/show_bug.cgi?id=7589 and
http://bugzilla.kernel.org/show_bug.cgi?id=7811
So if the problem still persists with the Intrepid 2.6.25/26 kernels which Leann gave instructions on how to get them, then it might be best to step up in one of those reports and try to get some resolution. The question seems to be whether this problem applies to all vt8251 controllers or just a subset of them.

[Cesar Corzo (cesarcorzo)]

Hi!
I am new to UBUNTU but I think I partially solved the problem.

My pc specs:

ASUS M2R32-MVP
AMD 64 x2 6000+ & 2 GB of RAM
IDE Maxtor 120Gigs & SATA WD 640Gigs

I partitioned my SATA drive as follows:

sda1: ntfs ->100 GB for windows xp sp3
sda2: ext3 -> 50 GB for Ubuntu Hardy Heron
sda3:ntfs -> storage

When Booting I changed the kernel initialization script and added the "pci=nomsi".

After I boot for the first time in ubuntu I changed the menu.lst file.

Hope that helps. My SATA drive seems to work fine.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Pedro Valente (pedro-valente)]

I have 2 SATA HDs and one SATA cd/dvd reader on an Asus P5Q-E motherboard and Intel quad-core processor.

The installation dind't recognize the Hardy cdrom, but with Intrepid Ibex alpha 5 it worked flawlessly.

If you need any additional info please tell me.

[Richard (richard-singletons)]

The alpha 5 live cd works fine for me as well. Hardy didn't recognise my sata drives on a Asus M2R32-MVP and AMD Athlon 64x2 4800. I can't install it though there is a file error on the iso file, I've tried downloading it twice.

[Leann Ogasawara (leannogasawara)]

Dan, since you are the original bug reporter, care to confirm if this is resolved for you with the newer Intrepid 2.6.27 kernel? Thanks.

[Craig Silk (csilk)]

This problem was recently discussed on IRC. We discovered a workaround, when installing add pci=nomsi as a kernal parameter.
Once installed add the same parameter to the kernal from grub, this will enable you to boot, you can then add the same parameter to your menu.lst in the /etc/grub folder to make it permanent.

This worked on Hardy. Not tested anywhere else.

[Alexandre JABORSKA (alexandre-jaborska)]

The problem was apparently solved for me using the pci=nomsi kernel parameter for a week, but it suddenly occurs again this morning when doing a e2fsck on my main partition.

Was not capable to pass the e2fsk stage (even with -c option)

The e2sfck prog seems to be quite aggressive with SATA links...

I'll try to test the Intrepid 8.10 later, but there is a other bug that make it unusable for me (not Intel GigaE support for now...).

using up-to-date Hardy Heron 8.04 (kernel 2.6.24) on a Laptop HP Compaq 8710p

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[jimav (james-avera)]

Hardy is supposed to get "Long Term Support", so if there is a fix in Intrepid, please back-port it. It does not seem reasonable to just not support SATA out of the box.

Note: Intrepid is unsuitable for many people because of several major regressions (session mgmt, bluetooth,...).
Therefore keeping Hardy useful on current hardware seems essential.

P.S. Does the previous post mean that nobody is looking at this bug any longer?

[Jon Ogilvie (svtdragon)]

I'm running Jaunty, and I still have this issue. The relevant output from lspci -vvnn is:

00:09.0 SATA controller [0106]: nVidia Corporation Device [10de:0584] (rev a2) (prog-if 01)
 Subsystem: nVidia Corporation Device [10de:cb84]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0 (750ns min, 250ns max)
 Interrupt: pin A routed to IRQ 2299
 Region 0: I/O ports at a480 [size=8]
 Region 1: I/O ports at a400 [size=4]
 Region 2: I/O ports at a080 [size=8]
 Region 3: I/O ports at a000 [size=4]
 Region 4: I/O ports at 9c00 [size=16]
 Region 5: Memory at f3f76000 (32-bit, non-prefetchable) [size=8K]
 Capabilities: <access denied>
 Kernel driver in use: ahci

I can boot up with or without pci=nomsi, but only because I have a PCIe RAID controller that I'm using to run my OS off of. The system will only recognize my SATA drives with pci=nomsi and the drives in AHCI mode, but I'd like to be able to use msi for PCI passthrough with KVM.

I haven't yet tried the Karmic kernel because I've got a very fragile system configuration that doesn't adapt well to change. :)

Is there a fix out there for this?

[Babassu (babassu)]

I started to have this problem with the upgrade to Ubuntu 8.04 (64bit) on a ASUS A8V-MX motherboard ( VT8251 SATA controller in ahci mode). Still present in 9.04 with kernel 2.6.28-16. Last kernel that works for me (even now in 9.04) is 2.6.22-16 so I intend to keep it till this problem is solved. I believe it is not a hardware problem since every kernel from Ubuntu 6.10 up to the 7.10 has worked for me. My suggestion is to look around the ahci module code.
The few lines I could write down before it drops to busybox shell look very similar with what was posted prior to me:
  ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  ata1.00: qc timeout (cmd 0xec)
  ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
I could not save more from dmesg since not even my floppy can be mounted at the busybox prompt (shows "invalid arguments" with an ext2 formatted floppy disk). The busybox "more" does not work either so I could not look too close into the dmesg output.
For reference this is what the "good" kernel shows when it works:
===========normal boot ahci section================
[ 28.709134] scsi0 : ahci
[ 28.709390] scsi1 : ahci
[ 28.709543] scsi2 : ahci
[ 28.709695] scsi3 : ahci
[ 28.710323] ata1: SATA max UDMA/133 cmd 0xffffc200001a2d00 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq
 21
[ 28.710328] ata2: SATA max UDMA/133 cmd 0xffffc200001a2d80 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq
 21
[ 28.710332] ata3: SATA max UDMA/133 cmd 0xffffc200001a2e00 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq
 21
[ 28.710337] ata4: SATA max UDMA/133 cmd 0xffffc200001a2e80 ctl 0x0000000000000000 bmdma 0x0000000000000000 irq
 21
[ 29.195349] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 29.196212] ata1.00: ATA-7: ST3300831AS, 3.03, max UDMA/133
[ 29.196215] ata1.00: 586072368 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 29.197082] ata1.00: configured for UDMA/133
[ 29.510744] ata2: SATA link down (SStatus 0 SControl 300)
[ 29.822153] ata3: SATA link down (SStatus 0 SControl 300)
[ 30.133562] ata4: SATA link down (SStatus 0 SControl 300)
===========================================================
A bit dissapointing that this kind of critical failure in my opinion introduced some time ago can stay around for so long.

[madbiologist (me-again)]

Official support for Ubuntu 8.04 "Hardy Heron", 8.10 "Intrepid Ibex" and 9.04 "Jaunty Jackalope" has ended. If you are still experiencing this issue on a supported version of Ubuntu please run ubuntu-bug to file a new bug report so that we can get a fresh set of log files and system information.