From: David T-G <davidtg-robot@justpickone.org>
To: Linux RAID list <linux-raid@vger.kernel.org>
Cc: Phil Turmel <philip@turmel.org>
Subject: Re: disks & prices plus python (was "Re: failed disks, mapper, and "Invalid argument"")
Date: Thu, 21 May 2020 08:30:59 -0400 [thread overview]
Message-ID: <20200521123059.GN1415@justpickone.org> (raw)
In-Reply-To: <5EC66C2E.90901@youngman.org.uk>
Wol, et al --
...and then Wols Lists said...
%
% On 21/05/20 12:01, David T-G wrote:
% >
% > ...and then Wols Lists said...
% > %
...
% > %
% > % Seagate Barracudas :-(
% >
% > Yep. They were good "back in the day" ...
%
% Still are. Just not for raid..
Oh! Well, that's nice to know. Of course, I had been hoping to move
these out to another system after upgrading to larger, but maybe that's
not an option :-( They are going to be worlds better than the existing
crap drives in there now, though, so here's hoping I can put them to use.
% >
...
% > % recovery. Plan to replace them with ones that do ASAP!
% >
% > That would be nice. I actually have wanted for quite some time
% > to grow these from 4T to 8T, but budget hasn't permitted. Got any
% > particularly-affordable recommendations?
%
% 8TB WD Reds are still CMR and okay AT THE MOMENT. I wouldn't trust them
% though (or make sure you can RMA them if they've changed!)
Thanks!
%
% I haven't heard of Ironwolves using SMR (yet).
%
% Looking quickly on Amazon
% WD Red 8TB £232
% Toshiba N300 8TB £239
% Seagate Ironwolf 8TB £260
% Seagate Ironwolf 8TB Silver £263 (optimised for raid it claims)
% WD Red 8TB Pro £270
% Seagate Ironwolf 8TB Pro £360
Ouch. I sure hope they're cheaper over here! Unfortunately, when I was
shopping I was looking at ... Barracudas :-/
%
% Given that the Red and the N300 are similar in price, I'd go for the
% N300. Bear in mind that I *never* see those drives mentioned here, I
% really don't know what they're like.
Thanks; I'll have a look.
%
...
% >
% > % rebuild, but I would VERY STRONGLY suggest you download lsdrv and get
% > % the output. The whole point of this script is to get the information you
% >
% > You mean the output that is some error and a few lines of traceback?
% > Yeah, I saw that, but I don't know how to fix it. Another problem in the
% > queue.
%
% Last time I ran it, it was Python 2.7. I needed to edit the shebang
% line. I think Phil's fixed that.
I checked and I have 2.7 on this box, so I figure it would work. But I
can barely spell Python, much less understand it.
Thanks again & HAND
:-D
--
David T-G
See http://justpickone.org/davidtg/email/
See http://justpickone.org/davidtg/tofu.txt
next prev parent reply other threads:[~2020-05-21 12:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 20:05 failed disks, mapper, and "Invalid argument" David T-G
2020-05-20 23:23 ` Wols Lists
2020-05-20 23:53 ` David T-G
2020-05-21 8:09 ` Wols Lists
2020-05-21 11:01 ` David T-G
2020-05-21 11:55 ` Wols Lists
2020-05-21 12:30 ` David T-G [this message]
2020-05-21 13:07 ` disks & prices plus python (was "Re: failed disks, mapper, and "Invalid argument"") antlists
2020-05-21 13:17 ` disks & prices plus python David T-G
2020-05-21 13:42 ` Wols Lists
2020-05-21 13:46 ` David T-G
2020-05-21 11:01 ` failed disks, mapper, and "Invalid argument" David T-G
2020-05-21 11:24 ` David T-G
2020-05-21 12:00 ` Wols Lists
2020-05-21 12:33 ` re-add syntax (was "Re: failed disks, mapper, and "Invalid argument"") David T-G
2020-05-21 13:01 ` antlists
2020-05-21 13:15 ` re-add syntax David T-G
2020-05-21 18:07 ` David T-G
2020-05-21 18:40 ` Roger Heflin
2020-05-21 22:52 ` David T-G
2020-05-21 23:17 ` antlists
2020-05-21 23:53 ` David T-G
2020-05-21 8:13 ` failed disks, mapper, and "Invalid argument" Wols Lists
2020-05-21 11:04 ` David T-G
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=20200521123059.GN1415@justpickone.org \
--to=davidtg-robot@justpickone.org \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).