From: Stan Hoeppner <stan@hardwarefreak.com>
To: Ross Boylan <ross@biostat.ucsf.edu>
Cc: Chris Murphy <lists@colorremedies.com>,
"linux-raid@vger.kernel.org Raid" <linux-raid@vger.kernel.org>
Subject: Re: How do I tell which disk failed?
Date: Tue, 08 Jan 2013 17:03:00 -0600 [thread overview]
Message-ID: <50ECA5A4.1040400@hardwarefreak.com> (raw)
In-Reply-To: <1357682055.3484.34.camel@markov.biostat.ucsf.edu>
On 1/8/2013 3:54 PM, Ross Boylan wrote:
> I am less excited about that since discovering the message about sdb
> does not mean it's running at over 100 degrees celsius (the raw value is
> around 45).
You must ignore the VALUE and WORST columns for drive temp. These are
"normalized" values only the smartmon idiots understand. The actual
temp of 45C is a bit high, but well within the operating range for that
drive. The WDC drives have a max temp (failure) of 80C IIRC, and a
normal max operating temp of 65C. So you don't need to worry about this
drive's temp.
> The logs from the restart show
> Jan 7 17:19:09 markov kernel: [ 2.928055] ata2.00: SATA link down (SStatus 0 SControl 0)
> Jan 7 17:19:09 markov kernel: [ 2.928102] ata2.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> Jan 7 17:19:09 markov kernel: [ 2.944459] ata2.01: ATA-8: WDC WD2003FYYS-02W0B1, 01.01D02, max UDMA/133
> Jan 7 17:19:09 markov kernel: [ 2.220056] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> Jan 7 17:19:09 markov kernel: [ 2.220103] ata1.01: SATA link down (SStatus 0 SControl 310)
> Jan 7 17:19:09 markov kernel: [ 2.228670] ata1.00: ATA-8: ST3750330NS, SN05, max UDMA/133
> the SATA link down messages
> sound a little odd.
No mystery here. These ports (links) are down because no drives are
connected to them, apparently. Show full dmesg output, and tell us the
SAS/SATA controller and port count on each for the system in question.
--
Stan
next prev parent reply other threads:[~2013-01-08 23:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 2:05 How do I tell which disk failed? Ross Boylan
2013-01-08 5:19 ` Stan Hoeppner
2013-01-08 6:59 ` Ross Boylan
2013-01-08 7:17 ` Chris Murphy
2013-01-08 7:49 ` Ross Boylan
2013-01-08 8:48 ` Chris Murphy
2013-01-08 9:32 ` Ross Boylan
2013-01-08 17:36 ` Chris Murphy
2013-01-08 22:30 ` Stan Hoeppner
2013-01-08 7:59 ` Ross Boylan
2013-01-08 9:10 ` Chris Murphy
2013-01-08 21:54 ` Ross Boylan
2013-01-08 22:38 ` Chris Murphy
2013-01-08 23:13 ` Ross Boylan
2013-01-09 0:43 ` Chris Murphy
2013-01-08 23:03 ` Stan Hoeppner [this message]
2013-01-08 5:55 ` Chris Murphy
2013-01-08 9:55 ` Mikael Abrahamsson
2013-01-08 17:20 ` Ross Boylan
2013-01-08 21:24 ` pg_mh, Peter Grandi
2013-01-08 22:34 ` Stan Hoeppner
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=50ECA5A4.1040400@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=ross@biostat.ucsf.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.