1 |
On Sat, Mar 27, 2010 at 11:56 AM, Paul Hartman |
2 |
<paul.hartman+gentoo@×××××.com> wrote: |
3 |
> On Fri, Mar 26, 2010 at 10:39 PM, Stroller |
4 |
> <stroller@××××××××××××××××××.uk> wrote: |
5 |
>> |
6 |
>> On 26 Mar 2010, at 22:21, Paul Hartman wrote: |
7 |
>>> |
8 |
>>> ... |
9 |
>>> Well, I was thinking more about something like alteriong IOH/ICH |
10 |
>>> voltage, or whichever voltage powers the SATA controllers. It has 12 |
11 |
>>> SATA headers on this motherboard but I don't know how much it can |
12 |
>>> realistically handle at once. Hopefully all of my disks. :) |
13 |
>> |
14 |
>> Honestly, I'm not sure that I'd do that. |
15 |
>> |
16 |
>> If I thought it was a power issue - and that seems quite a reasonable |
17 |
>> possibility - I would replace the PSU first. |
18 |
>> |
19 |
>> What PSU are you using at the moment? Brand / wattage? |
20 |
>> |
21 |
>> I think these are probably overkill: |
22 |
>> |
23 |
>> http://www.bluepoint.net/AKAPSU066 |
24 |
>> http://www.bluepoint.net/AKAPSU071 |
25 |
>> |
26 |
>> However, if you're using a 450W PSU at the moment, you can get an OCZ |
27 |
>> branded 600W for less than £50. I tend to be suspicious of cheap unbranded |
28 |
>> and Wong Fu 350W - 450W PSUs. Often a 350W PSU from a manufacturer with a |
29 |
>> half-decent brand (eg Trust) will be better than a no-name 450W PSU. |
30 |
>> |
31 |
>> It seems important not only the actual wattage that the PSU gives out |
32 |
>> (measured with an analogue-needle multimeter) but also how stable that |
33 |
>> voltage is, how smooth, consistent and reliable it is. Unless your PSU is |
34 |
>> absolute top-notch quality, try to under-utilise it. |
35 |
>> |
36 |
>> With 6 x hard-drives, I would be generous with supplying power - I think a |
37 |
>> 600W PSU would easily be justified. |
38 |
>> |
39 |
>> Stroller. |
40 |
>> |
41 |
> |
42 |
> I have a 750W Corsair 750TX which should be plenty (if not overkill). |
43 |
> Seems to have all the bells and whistles (though I wish I had bought |
44 |
> the modular version). I definitely agree about the cheap no-name PSUs, |
45 |
> I've seen some USD$10 ones go up in smoke after just a few minutes of |
46 |
> use. |
47 |
> |
48 |
> Based on the little info I could find Googling it seems the most |
49 |
> likely explanations are: |
50 |
> |
51 |
> IRQ handling weirdness (but that was more probable in older |
52 |
> motherboards and kernels) |
53 |
> ahci driver issues (I will reboot with the controllers in "legacy" |
54 |
> mode to use the non-ahci drivers and see what happens) |
55 |
> a bad drive, bad cable, bad controller, bad sector, something physically bad. |
56 |
> |
57 |
> Overnight I copied several hundred gigs of data (and still going) and |
58 |
> the error has not been reproduced. Before installing, I did a full |
59 |
> SMART test (a few hours) and a badblocks read-only test (even more |
60 |
> hours) and neither showed any errors. I did not do a full read/write |
61 |
> test, though. |
62 |
> |
63 |
> I haven't heard any unexpected noises coming from the drives (no |
64 |
> clicks of doom), though I have so many fans going it may be hard to |
65 |
> hear. |
66 |
> |
67 |
> Thanks. |
68 |
> |
69 |
|
70 |
I have nothing to add, but almost 5 months on from my original post I |
71 |
just had this same error message for the second time. This time it was |
72 |
on a different physical disk, which -- strangely -- makes me feel |
73 |
better. Different kernel revision (2.6.35.1 now). Still don't know |
74 |
what's the cause... it's an odd one that I'll be keeping my eye on. |
75 |
|
76 |
[ 1435.938398] ata6.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x6 frozen |
77 |
[ 1435.938403] ata6.00: failed command: READ FPDMA QUEUED |
78 |
[ 1435.938409] ata6.00: cmd 60/e8:08:38:a5:86/01:00:01:00:00/40 tag 1 |
79 |
ncq 249856 in |
80 |
[ 1435.938410] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask |
81 |
0x4 (timeout) |
82 |
[ 1435.938412] ata6.00: status: { DRDY } |
83 |
[ 1435.938416] ata6: hard resetting link |
84 |
[ 1436.395618] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) |
85 |
[ 1436.407546] ata6.00: configured for UDMA/133 |
86 |
[ 1436.407552] ata6.00: device reported invalid CHS sector 0 |
87 |
[ 1436.407559] ata6: EH complete |