From: Tim Moore <tim.moore@nsr500.net>
To: linux-raid@vger.kernel.org
Subject: Re: 3Ware on 64bit Linux.
Date: Sun, 19 Jun 2005 08:57:45 -0700 [thread overview]
Message-ID: <42B595F9.9020207@nsr500.net> (raw)
In-Reply-To: <200506100836.20625.hjm@tacgi.com>
Harry Mangalam wrote:
>
> On Friday 10 June 2005 1:25 am, Tim Moore wrote:
>
>
>>The SD's are 100% duty cycle, 24x7, 1M hour MTBF commercial SATA II drives,
>>whereas the JD's are SATA I with a "desktop" rating and a 'designed for
>>Microsoft Windows' cert. Why WD would trade a commercial drive for a
>>desktop drive?
>
>
> Dunno, but they did, altho the disks back were 'recertified', not new. As to
Interesting. Maybe there were serious mfg problems with the JDs.
> the 1M MTBF rating, I also dunno. I got 9 're-certified SD drives' back from
> WD and 2 of them (oops, make that 3 of them) have failed in the past 24
> hours, which points to some underlying problem in the system. It's on a UPS
> which should condition the voltage. The drives that went out were on
> different ports and one of them was direct-connected, not via a hotswap cage
> (due to previous suspicions about the hotswap cage).
>
> Any insight into this failure rate would be appreciated. About to open
> another support call to 3ware...
I've also taken "failed" WD drives on production hardware which have passed
WD's own check program and found that badblocks -n will force remapping the
bad sectors.
>
>
>>Besides that I've used 3Ware controllers since the 6400 and have had zero
>>problems with anything.
>
>
> I guess I'm the reason they say YMMV. :)
Fair enough.
prev parent reply other threads:[~2005-06-19 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 17:09 3Ware on 64bit Linux Jason Leach
2005-06-08 18:49 ` Mike Hardy
2005-06-08 18:56 ` Harry Mangalam
2005-06-08 19:58 ` Dan Stromberg
2005-06-08 21:36 ` Konstantin Olchanski
2005-06-08 21:56 ` Harry Mangalam
2005-06-10 8:25 ` Tim Moore
2005-06-10 15:36 ` Harry Mangalam
2005-06-19 15:57 ` Tim Moore [this message]
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=42B595F9.9020207@nsr500.net \
--to=tim.moore@nsr500.net \
--cc=linux-raid@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 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.