From: Tejun Heo <htejun@gmail.com>
To: Jonas Lundgren <jonas@local.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: Scary Intel SATA problem: "frozen"
Date: Thu, 7 Dec 2006 10:25:46 +0900 [thread overview]
Message-ID: <20061207012546.GA15219@htj.dyndns.org> (raw)
In-Reply-To: <457704BA.7090001@local.se>
On Wed, Dec 06, 2006 at 06:58:18PM +0100, Jonas Lundgren wrote:
> Here's the relevant part, if you want the whole dmesg look at:
> http://pastebin.ca/269581
>
[--snip--]
> [89585.740245] ata2: hardreset failed, retrying in 5 secs
> [89590.736978] ata2: hard resetting port
> [89598.081854] ata2: port is slow to respond, please be patient (Status
> 0x80)
> [89617.604742] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [89617.611034] ata2.00: configured for UDMA/100
> [89617.611042] ata2: EH complete
> [89617.623426] SCSI device sdb: 145226112 512-byte hdwr sectors (74356 MB)
> [89617.633551] sdb: Write Protect is off
> [89617.633553] sdb: Mode Sense: 00 3a 00 00
> [89617.637765] SCSI device sdb: write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
EH went okay although your harddrive is responding sluggishly.
> > 1. swap the two. you'll probably have to dance a little bit with boot
> > loader but md should handle that fine once the kernel is loaded. does
> > the errors persist? on which device do they occur? do they follow the
> > drive or stay on the mobo port?
>
> It follows the drive. (Hardware problem?)
Yeap, probably.
[--snip--]
> I guess it could only be a hardware problem since the error follows the
> drive, and both the drives are identical, so it can't be a firmware
> problem. Correct me if I'm wrong.
Firmware? Could be a firmware bug on the drive but not
controller/driver problem.
[--snip--]
> 9 Power_On_Hours 0x0032 076 076 000 Old_age Always
> - 18117
That's two year's worth of spinning. I wouldn't be surprised if the
drive gives out.
> 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always
> - 639
And quite some number of reallocations. Reallocation itself doesn't
necessarily indicate critical condition but if you've got 639 of them,
you gotta throw that thing away.
--
tejun
next prev parent reply other threads:[~2006-12-07 1:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 22:24 Scary Intel SATA problem: "frozen" Jonas Lundgren
2006-11-28 22:59 ` Linus Torvalds
2006-11-28 23:22 ` Jeff Garzik
2006-11-28 23:43 ` Linus Torvalds
2006-11-29 0:38 ` Jeff Garzik
2006-11-29 0:51 ` Linus Torvalds
2006-11-29 2:51 ` Mark Lord
2006-11-29 0:57 ` Tejun Heo
2006-11-29 7:14 ` Jonas Lundgren
2006-11-29 7:29 ` Tejun Heo
2006-11-29 14:11 ` Mark Lord
2006-11-29 16:19 ` Linus Torvalds
2006-12-06 17:58 ` Jonas Lundgren
2006-12-06 18:45 ` Andrew Lyon
2006-12-07 1:25 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-14 15:04 [git patches] libata fixes Jeff Garzik
2006-11-28 17:31 ` Scary Intel SATA problem: "frozen" Linus Torvalds
2006-11-28 17:37 ` Mark Lord
2006-11-28 17:55 ` Sergei Shtylyov
2006-11-28 20:12 ` Eric D. Mudama
2006-11-28 20:36 ` Sergei Shtylyov
2006-11-29 1:12 ` Tejun Heo
2006-11-28 18:05 ` Alan
2006-11-28 18:33 ` Linus Torvalds
2006-11-28 21:03 ` Jeff Garzik
2006-11-28 21:45 ` Linus Torvalds
2006-11-28 22:18 ` Jeff Garzik
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=20061207012546.GA15219@htj.dyndns.org \
--to=htejun@gmail.com \
--cc=jonas@local.se \
--cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).