1 |
On 26 Mar 2010, at 20:17, Paul Hartman wrote: |
2 |
> ... |
3 |
> Setting up and testing my new system (after wasting nearly 1 month |
4 |
> with bad RAM modules), I got this error today: |
5 |
> |
6 |
> [48055.741389] ata3.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action |
7 |
> 0x6 frozen |
8 |
> [48055.741393] ata3.00: failed command: READ FPDMA QUEUED |
9 |
> [48055.741398] ata3.00: cmd 60/20:08:38:15:03/01:00:18:00:00/40 tag 1 |
10 |
> ncq 147456 in |
11 |
> [48055.741400] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask |
12 |
> 0x4 (timeout) |
13 |
> [48055.741402] ata3.00: status: { DRDY } |
14 |
> [48055.741405] ata3: hard resetting link |
15 |
> [48056.198746] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) |
16 |
> [48056.210514] ata3.00: configured for UDMA/133 |
17 |
> [48056.210518] ata3.00: device reported invalid CHS sector 0 |
18 |
> [48056.210523] ata3: EH complete |
19 |
> |
20 |
> I really don't understand what it means, but the "timeout", "hard |
21 |
> resetting link" and "invalid CHS sector 0" look scary to me... |
22 |
|
23 |
How new is this motherboard? One may see something similar if one |
24 |
connects a SATA2 drive to an older SATA motherboard without the jumper |
25 |
(on the drive) set to restrict it to 1.5 Gbps. |
26 |
|
27 |
Stroller. |