From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel2.6.33: ATA failed command: READ FPDMA QUEUED, hard resetting link
Date: Sat, 27 Mar 2010 11:56:52 -0500 [thread overview]
Message-ID: <58965d8a1003270956x432e0c77jc59ab07041293c85@mail.gmail.com> (raw)
In-Reply-To: <F0E03A38-B82F-4B31-9984-FEE853FF246F@stellar.eclipse.co.uk>
On Fri, Mar 26, 2010 at 10:39 PM, Stroller
<stroller@stellar.eclipse.co.uk> wrote:
>
> On 26 Mar 2010, at 22:21, Paul Hartman wrote:
>>
>> ...
>> Well, I was thinking more about something like alteriong IOH/ICH
>> voltage, or whichever voltage powers the SATA controllers. It has 12
>> SATA headers on this motherboard but I don't know how much it can
>> realistically handle at once. Hopefully all of my disks. :)
>
> Honestly, I'm not sure that I'd do that.
>
> If I thought it was a power issue - and that seems quite a reasonable
> possibility - I would replace the PSU first.
>
> What PSU are you using at the moment? Brand / wattage?
>
> I think these are probably overkill:
>
> http://www.bluepoint.net/AKAPSU066
> http://www.bluepoint.net/AKAPSU071
>
> However, if you're using a 450W PSU at the moment, you can get an OCZ
> branded 600W for less than £50. I tend to be suspicious of cheap unbranded
> and Wong Fu 350W - 450W PSUs. Often a 350W PSU from a manufacturer with a
> half-decent brand (eg Trust) will be better than a no-name 450W PSU.
>
> It seems important not only the actual wattage that the PSU gives out
> (measured with an analogue-needle multimeter) but also how stable that
> voltage is, how smooth, consistent and reliable it is. Unless your PSU is
> absolute top-notch quality, try to under-utilise it.
>
> With 6 x hard-drives, I would be generous with supplying power - I think a
> 600W PSU would easily be justified.
>
> Stroller.
>
I have a 750W Corsair 750TX which should be plenty (if not overkill).
Seems to have all the bells and whistles (though I wish I had bought
the modular version). I definitely agree about the cheap no-name PSUs,
I've seen some USD$10 ones go up in smoke after just a few minutes of
use.
Based on the little info I could find Googling it seems the most
likely explanations are:
IRQ handling weirdness (but that was more probable in older
motherboards and kernels)
ahci driver issues (I will reboot with the controllers in "legacy"
mode to use the non-ahci drivers and see what happens)
a bad drive, bad cable, bad controller, bad sector, something physically bad.
Overnight I copied several hundred gigs of data (and still going) and
the error has not been reproduced. Before installing, I did a full
SMART test (a few hours) and a badblocks read-only test (even more
hours) and neither showed any errors. I did not do a full read/write
test, though.
I haven't heard any unexpected noises coming from the drives (no
clicks of doom), though I have so many fans going it may be hard to
hear.
Thanks.
next prev parent reply other threads:[~2010-03-27 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 20:17 [gentoo-user] Kernel2.6.33: ATA failed command: READ FPDMA QUEUED, hard resetting link Paul Hartman
2010-03-26 21:31 ` Neil Walker
2010-03-26 22:21 ` Paul Hartman
2010-03-27 3:39 ` Stroller
2010-03-27 16:56 ` Paul Hartman [this message]
2010-08-12 5:50 ` Paul Hartman
2010-08-13 7:11 ` Mick
2010-03-27 3:23 ` Stroller
2010-03-27 16:41 ` Paul Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58965d8a1003270956x432e0c77jc59ab07041293c85@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox