All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tudor Holton <tudor@smartguide.com.au>
To: "Timothy D. Lenz" <tlenz@vorgon.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Mixing WD red with older seagates
Date: Mon, 09 Sep 2013 13:50:21 +1000	[thread overview]
Message-ID: <522D457D.1000900@smartguide.com.au> (raw)
In-Reply-To: <522D4369.80404@vorgon.com>

Completely anecdotal evidence, but I was mixing WD Reds and Seagates in 
a QNAP RAID 6 each 3TB for a total of 6TB, and the Seagates kept making 
sounds like they were about to hurl.  Testing each drive individually 
with badblocks and smart came up with all drives OK.  But it kept 
chucking the WDs one by one.  Eventually I removed the Seagates and 
replaced them with WDs and since then no drives have been thrown out.

I can only theorise that there may be a timing issue between WD Reds and 
Seagate.

On 09/09/13 13:41, Timothy D. Lenz wrote:
> well, another drive going down. This time sdc. I have a vdr system 
> with 2 pairs of seagate 500Gb drives set up as mirrors. a/b are boot, 
> swap, and data. c/d are single partition data. I have done at least 4 
> rma's on these drives and warranty was nearly up on the last one to go 
> down just 6 months ago. So warranty or not, I'm done with seagate. I 
> only have about $100 saved up (was saving for something else:( ). I'd 
> like to get a WD red 1Tb drive and set it up to act as a 3rd for a/b 
> and replace sdc mirroring sdd. Then at some point remove sda or b 
> (maybe in another 6 months when one of them goes).
>
> I read that the red line WD's had some problems with the 1Gb drives 
> when they first come out. Anyone get any lately know if they are 
> reliable now? Also, any problems pairing one of these with the seagates?
>
> Any red flags in these that will cause problems? I have to refigure 
> all this stuff out each time.
>
> ------------------------------------------------
> menu.lst: http://pastebin.com/7WWHajsc
> ------------------------------------------------
> device.map:
>
> (fd0)    /dev/fd0
> (hd0)    /dev/disk/by-id/ata-ST3500413AS_Z3T69GCE
> (hd1)    /dev/disk/by-id/ata-ST3500418AS_5VMJ49P1
> (hd2)    /dev/disk/by-id/ata-ST3500320AS_9QM35MY5
> (hd3)    /dev/disk/by-id/ata-ST3500820AS_9QM6V6JF
> ------------------------------------------------
> I know there was some command to auto update device.map, but I forget 
> what it was.
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2013-09-09  3:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09  3:41 Mixing WD red with older seagates Timothy D. Lenz
2013-09-09  3:50 ` Tudor Holton [this message]
2013-09-09 14:38   ` Jonathan Wilson
2013-09-09 14:56     ` Mathias Burén
2013-09-09 21:35       ` Timothy D. Lenz
2013-09-10  8:53       ` Andrew Brooks
2013-09-10 12:24     ` Drew

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=522D457D.1000900@smartguide.com.au \
    --to=tudor@smartguide.com.au \
    --cc=linux-raid@vger.kernel.org \
    --cc=tlenz@vorgon.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.