From: Wols Lists <antlists@youngman.org.uk>
To: o1bigtenor <o1bigtenor@gmail.com>
Cc: Adam Goryachev <mailinglists@websitemanagers.com.au>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Request for assistance
Date: Wed, 6 Jul 2016 22:31:34 +0100 [thread overview]
Message-ID: <577D78B6.1070104@youngman.org.uk> (raw)
In-Reply-To: <CAPpdf5-bdvWwp3pSTFgoL++avt-8=3VvzL-Psk2qR7rHRZUBtQ@mail.gmail.com>
On 06/07/16 19:28, o1bigtenor wrote:
> SCT Error Recovery Control:
> Read: 70 (7.0 seconds)
> Write: 70 (7.0 seconds)
As soon as you said WD Red, that said the drives are good. The SCT says
the drives will wait at most 7 seconds before returning a problem, so
that's what you want (My Barracudas can't do that - a problem waiting to
happen).
I'll let someone who knows more comment on the rest of the output, but
that SCT stuff tells us your problem is not the usual one of someone
using the wrong drives.
Cheers,
Wol
next prev parent reply other threads:[~2016-07-06 21:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 0:13 Request for assistance o1bigtenor
2016-07-06 1:55 ` Adam Goryachev
2016-07-06 12:14 ` o1bigtenor
2016-07-06 12:51 ` Wols Lists
2016-07-06 18:28 ` o1bigtenor
2016-07-06 21:31 ` Wols Lists [this message]
2016-07-07 2:05 ` Brad Campbell
2016-07-07 3:28 ` o1bigtenor
2016-07-06 7:39 ` keld
2016-07-06 12:15 ` o1bigtenor
-- strict thread matches above, loose matches on Subject: below --
2022-10-22 8:11 request " Tanju Brunostar
2022-10-22 8:13 ` Julia Lawall
2022-10-22 8:20 ` Tanju Brunostar
2022-10-20 11:00 Request " Ubuntu
2022-10-20 11:10 ` Greg KH
2022-10-20 11:14 ` Tanju Brunostar
2022-10-20 11:59 ` Julia Lawall
[not found] ` <CAOkYk0iU0B98JsH77avky--AS19V=GhQox2f_b4PAG3ZBB+SVQ@mail.gmail.com>
2022-10-20 11:34 ` Tanju Brunostar
2022-10-20 12:10 ` Greg KH
2022-10-20 14:39 ` Theodore Ts'o
[not found] ` <Y1Hby38PE/QVlRhF@Slackware>
2022-10-21 6:11 ` Tanju Brunostar
2021-04-12 1:17 o1bigtenor
2010-03-12 14:04 Aditya Pendyala
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=577D78B6.1070104@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
--cc=o1bigtenor@gmail.com \
/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.