On Fri, Mar 26, 2010 at 10:23 PM, Stroller
<strol...@stellar.eclipse.co.uk> wrote:
>
> On 26 Mar 2010, at 20:17, Paul Hartman wrote:
>>
>> ...
>> Setting up and testing my new system (after wasting nearly 1 month
>> with bad RAM modules), I got this error today:
>>
>> [48055.741389] ata3.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x6
>> frozen
>> [48055.741393] ata3.00: failed command: READ FPDMA QUEUED
>> [48055.741398] ata3.00: cmd 60/20:08:38:15:03/01:00:18:00:00/40 tag 1
>> ncq 147456 in
>> [48055.741400] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
>> 0x4 (timeout)
>> [48055.741402] ata3.00: status: { DRDY }
>> [48055.741405] ata3: hard resetting link
>> [48056.198746] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> [48056.210514] ata3.00: configured for UDMA/133
>> [48056.210518] ata3.00: device reported invalid CHS sector 0
>> [48056.210523] ata3: EH complete
>>
>> I really don't understand what it means, but the "timeout", "hard
>> resetting link" and "invalid CHS sector 0" look scary to me...
>
> How new is this motherboard? One may see something similar if one connects a
> SATA2 drive to an older SATA motherboard without the jumper (on the drive)
> set to restrict it to 1.5 Gbps.
It is a new motherboard with 8 SATA2 headers, 2 SATA3 (6Gbps) and 2
eSATA. I'm only using the internal SATA2 ports now, not the SATA3. One
floppy and one IDE also unused :)
The drive is 2TB and new as well. No jumpers. Thanks.
