FC5 - x86_64 sata_nv problem

Wed Jul 26 14:22:25 UTC 2006

This sounds like either a hardware problem or a BIOS problem.  Have
you verified that you're using the latest BIOS?

On 7/26/06, Philip Trickett (List) <phil-ml at techworks.ie> wrote:
> Hi,
>
> I have an installation of Fedora Core 5 on an Acer PC (Acer Power M6)
> with an Nforce 4 based chipset with integrated graphics.
>
> The motherboard has a single PATA controller on board with Master and
> Slave sockets, as well as 4 SATA headers on the board.
>
> My setup:
>
> PATA - No Drives installed
>
> SATA1 - 80GB SATA
> SATA2 - 320GB SATA
> SATA3 - 320GB SATA
> SATA4 - 320GB SATA
>
> What I am trying to do is install the OS on the 80GB drive, and then use
> the 3 320GB disks in a software RAID5 array for data storage.
>
> The problem I am having is that when the kernel starts to boot, and it
> probes the SATA disks, it always reports the error:
>
> ata4: SATA link up 1.5 Gbps (SStatus 113)
> ata4 is slow to respond, please be patient
> ata4 failed to respond (30 secs)
> scsi3 : sata_nv
>
> If I swap the disk around, the error is always with ata4.
>
> If I remove a disk, it then has an error with ata3.
>
> I have tried different cables, changing the disk positions, but I still
> get the same error.
>
> Below is a PCI listing:
>
> [root at habanero ~]# lspci
> 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
> 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
> 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
> 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
> 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
> 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
> 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
> 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
> 00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
> 00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
> 00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
> 00:05.0 VGA compatible controller: nVidia Corporation C51 PCI Express
> Bridge (rev a2)
> 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
> 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a2)
> 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a2)
> 00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev
> a2)
> 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2)
> 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2)
> 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
> 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller
> (rev a1)
> 00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller
> (rev a1)
> 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
> 00:10.2 Multimedia audio controller: nVidia Corporation MCP51 AC97 Audio
> Controller (rev a2)
> 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1)
> 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> HyperTransport Technology Configuration
> 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> Address Map
> 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> DRAM Controller
> 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> Miscellaneous Control
>
>
> Also, relevant lines from dmesg:
>
> [root at habanero ~]# dmesg | grep ata
> Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 rhgb
> quiet)
>  BIOS-e820: 000000007bef3000 - 000000007bf00000 (ACPI data)
> Memory: 1990924k/2030528k available (2385k kernel code, 39216k reserved,
> 1701k data, 200k init)
> ksign: Installing public key data
> Write protecting the kernel read-only data: 919k
> libata version 1.20 loaded.
> sata_nv 0000:00:0e.0: version 0.8
> ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xE000 irq 209
> ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xE008 irq 209
> ata1: SATA link up 3.0 Gbps (SStatus 123)
> ata1: dev 0 cfg 49:2f00 82:346b 83:7fe9 84:4773 85:3468 86:3c01 87:4763
> 88:407f
> ata1: dev 0 ATA-7, max UDMA/133, 160836480 sectors: LBA48
> ata1: dev 0 configured for UDMA/133
> scsi0 : sata_nv
> ata2: SATA link up 1.5 Gbps (SStatus 113)
> ata2: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4023 85:3468 86:3c01 87:4023
> 88:407f
> ata2: dev 0 ATA-7, max UDMA/133, 625142448 sectors: LBA48
> ata2: dev 0 configured for UDMA/133
> scsi1 : sata_nv
> ata3: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xCC00 irq 217
> ata4: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xCC08 irq 217
> ata3: SATA link up 1.5 Gbps (SStatus 113)
> ata3: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4023 85:3468 86:3c01 87:4023
> 88:407f
> ata3: dev 0 ATA-7, max UDMA/133, 625142448 sectors: LBA48
> ata3: dev 0 configured for UDMA/133
> scsi2 : sata_nv
> ata4: SATA link up 1.5 Gbps (SStatus 113)
> ata4 is slow to respond, please be patient
> ata4 failed to respond (30 secs)
> scsi3 : sata_nv
> EXT3-fs: mounted filesystem with ordered data mode.
> EXT3-fs: mounted filesystem with ordered data mode.
>
>
> What I would like to know, has anyone else come across this, and if so,
> how did you fix it?

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman                                    netllama at gmail.com
LlamaLand                       http://netllama.linux-sxs.org