From: David Greaves <david@dgreaves.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Erik Mouw <erik@harddisk-recovery.com>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-kernel@vger.kernel.org
Subject: Re: Is my SATA/400GB drive dying?
Date: Tue, 14 Feb 2006 21:50:01 +0000 [thread overview]
Message-ID: <43F25089.2020109@dgreaves.com> (raw)
In-Reply-To: <200602141930.45368.s0348365@sms.ed.ac.uk>
Alistair John Strachan wrote:
>On Tuesday 14 February 2006 10:43, Erik Mouw wrote:
>
>
>>On Mon, Feb 13, 2006 at 08:18:47PM -0500, Justin Piszcz wrote:
>>
>>
>>>Still get the errors:
>>>
>>>[ 2311.980127] ata3: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ
>>>0xb/00/00
>>>[ 2311.980134] ata3: status=0x51 { DriveReady SeekComplete Error }
>>>[ 2311.980138] ata3: error=0x04 { DriveStatusError }
>>>
>>>
>>FWIW, this could be related to smartctl trying to monitor the disk.
>>Try this:
>>
>> smartctl -d ata -a /dev/sdX
>>
>>If that complains about SMART being disabled, enable it with:
>>
>> smartctl -d ata -e /dev/sdX
>>
>>
>
>Are you sure this isn't something obvious like an insufficiently large power
>supply in the system? I've had strange SATA errors before because I was
>running 4 HDs and a 6600GT on a 360W PSU.
>
>
>
I have very similar problems - I spent £70ish on a decent branded,
reviewed 500W PSU and *still* have the exact same problems.
David
--
next prev parent reply other threads:[~2006-02-14 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 11:58 Is my SATA/400GB drive dying? Justin Piszcz
2006-02-13 12:00 ` Justin Piszcz
2006-02-13 13:16 ` Kalin KOZHUHAROV
2006-02-13 15:16 ` David Greaves
2006-02-14 1:17 ` Justin Piszcz
2006-02-14 1:18 ` Justin Piszcz
2006-02-14 10:43 ` Erik Mouw
2006-02-14 19:30 ` Alistair John Strachan
2006-02-14 21:50 ` David Greaves [this message]
2006-02-14 23:53 ` Justin Piszcz
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=43F25089.2020109@dgreaves.com \
--to=david@dgreaves.com \
--cc=erik@harddisk-recovery.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
/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