From: Wols Lists <antlists@youngman.org.uk>
To: o1bigtenor <o1bigtenor@gmail.com>,
Adam Goryachev <mailinglists@websitemanagers.com.au>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Questions
Date: Tue, 16 Feb 2016 14:32:49 +0000 [thread overview]
Message-ID: <56C33311.2040707@youngman.org.uk> (raw)
In-Reply-To: <CAPpdf598JjWbDFs93XU=Ph2EehNkw2qjXthUnGH+8cFs4N=64Q@mail.gmail.com>
On 16/02/16 11:46, o1bigtenor wrote:
> A major reason as to why the drives are getting replaced. Back in early 2012
> when I setup the machine there was no obvious information that the ERC
> type drives were needed so I just bought vanilla drives.
This is just what I've got a gut feel for, it seems to make sense of
what I've seen on the list ...
"new" drives of 2TB or more have the crippled drive firmware unless you
specifically buy raid.
The original release date of 1TB and less drives predates the crippling,
and the manufacturers haven't bothered to go back and "fix" this.
So 1TB drives - even desktop ones - seem usually to be okay. Anything
over that is suspect.
Cheers,
Wol
Incidentally, any reason for sticking with the same size drives? I'm
looking at replacing my Barracudas and might well upgrade from 3TB to
4TB, just because the price difference is minimal. That's despite /home
only being half full even though I have a 24MP camera ...
next prev parent reply other threads:[~2016-02-16 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 4:28 Questions o1bigtenor
2016-02-14 6:34 ` Questions Adam Goryachev
2016-02-14 11:53 ` Questions o1bigtenor
2016-02-14 12:24 ` Questions Adam Goryachev
2016-02-15 12:12 ` Questions o1bigtenor
2016-02-15 19:50 ` Questions Wols Lists
2016-02-15 21:01 ` Questions o1bigtenor
2016-02-15 22:05 ` Questions Adam Goryachev
2016-02-16 11:46 ` Questions o1bigtenor
2016-02-16 14:00 ` Questions Adam Goryachev
2016-02-16 18:33 ` Questions o1bigtenor
2016-02-16 14:32 ` Wols Lists [this message]
2016-02-16 18:37 ` Questions o1bigtenor
2016-02-15 22:09 ` Questions Wols Lists
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=56C33311.2040707@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox