From: Ram Ramesh <rramesh2400@gmail.com>
To: John Stoffel <john@stoffel.org>, Roger Heflin <rogerheflin@gmail.com>
Cc: Wols Lists <antlists@youngman.org.uk>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Linux raid-like idea
Date: Tue, 15 Sep 2020 14:34:35 -0500 [thread overview]
Message-ID: <f677f8d6-a831-7a85-3089-221723f021c5@gmail.com> (raw)
In-Reply-To: <24417.718.670043.535084@quad.stoffel.home>
On 9/15/20 1:07 PM, John Stoffel wrote:
>>>>>> "Roger" == Roger Heflin <rogerheflin@gmail.com> writes:
>>> I've been looking at them for a while now, but hesitating
>>> because... not sure why. I'm using a CoolerMaster case with five
>>> 5.25" bays, plus a 3.5" bay external, and another three or four
>>> internal 3.5" bays. Works great. Nice and plain and not flashing
>>> lights or other bling. And not too loud either. Which is good.
>>>
>>> But I've used crappy drive cages before, crappy hot swap ones. Not
>>> good. And I think it's time I just went with a 4U rack mount with a
>>> bunch of hot swap bays, if I could only find one that wasn't an arm
>>> and a leg.
>>>
> Roger> I have had good luck with the ICY DOCK brand how swap I have 4
> Roger> different 4 bay-3bay ones spanning 6+ years and they all seem
> Roger> to just work. And each newer version seemed to have improved
> Roger> design from the prior ones (plugs easier to get to, and such).
>
> Thanks for the recommendation! I'll be looking at these for
> sure. Just wish my case could hold two of them. It would be nice if
> they made a 2.5 x 5.25" to 4 x 3.5" disk carrier, so I could stuff two
> of them into my 5 exposed 5.25" bays. *grin*
John,
Drive cages come in varity of sizes. You have 1 to 1, 2 to 3, 3 to 4
and 4 to 5. Mix and match to fill all 5 bays with best density of 3.5
inch bays. Here is one example and I am sure you can find many.
https://www.newegg.com/p/pl?d=hot+swap+bay&N=100007599%20600551589&name=SSD+%2F+HDD+Accessories&Order=4
I have three cages, two istar and 1 icy doc. My icy dock lost one bay.
The others are holding a bit better. So, YMMV. However, expect them to
have noisy fans. You may want to change to quieter/reliable ones.
Regards
Ramesh
next prev parent reply other threads:[~2020-09-15 19:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1cf0d18c-2f63-6bca-9884-9544b0e7c54e.ref@aim.com>
2020-08-24 17:23 ` Linux raid-like idea Brian Allen Vanderburg II
2020-08-28 15:31 ` antlists
2020-09-05 21:47 ` Brian Allen Vanderburg II
2020-09-05 22:42 ` Wols Lists
2020-09-11 15:14 ` Brian Allen Vanderburg II
2020-09-11 19:16 ` antlists
2020-09-11 20:14 ` Brian Allen Vanderburg II
2020-09-12 6:09 ` Song Liu
2020-09-12 14:40 ` Adam Goryachev
2020-09-12 16:19 ` antlists
2020-09-12 17:28 ` John Stoffel
2020-09-12 18:41 ` antlists
2020-09-13 12:50 ` John Stoffel
2020-09-13 16:01 ` Wols Lists
2020-09-13 23:49 ` Brian Allen Vanderburg II
2020-09-15 2:12 ` John Stoffel
[not found] ` <43ce60a7-64d1-51bc-f29c-7a6388ad91d5@grumpydevil.homelinux.org>
2020-09-15 18:12 ` John Stoffel
2020-09-15 19:52 ` Rudy Zijlstra
2020-09-15 2:09 ` John Stoffel
2020-09-15 11:14 ` Roger Heflin
2020-09-15 18:07 ` John Stoffel
2020-09-15 19:34 ` Ram Ramesh [this message]
2020-09-14 17:19 ` Phillip Susi
2020-09-14 17:26 ` Wols Lists
2020-09-15 11:32 ` Nix
2020-09-15 18:10 ` John Stoffel
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=f677f8d6-a831-7a85-3089-221723f021c5@gmail.com \
--to=rramesh2400@gmail.com \
--cc=antlists@youngman.org.uk \
--cc=john@stoffel.org \
--cc=linux-raid@vger.kernel.org \
--cc=rogerheflin@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;
as well as URLs for NNTP newsgroup(s).