From plug-discuss-bounces@lists.phxlinux.org Wed Dec 30 16:40:19 2020 Return-Path: X-Original-To: lurker@lists.phxlinux.org Delivered-To: lurker@lists.phxlinux.org Received: from phxlinux.org (localhost [127.0.0.1]) by phxlinux.org (Postfix) with ESMTP id 470C732A000F; Wed, 30 Dec 2020 16:40:17 -0700 (MST) X-Original-To: plug-discuss@lists.phxlinux.org Delivered-To: plug-discuss@lists.phxlinux.org Received: from duncanmultimedia.com (cornwallis.duncanmultimedia.com [208.77.223.82]) by phxlinux.org (Postfix) with ESMTPS id DBA7B32A000E for ; Wed, 30 Dec 2020 16:40:15 -0700 (MST) Received: from napita.snaptek.com (ip70-171-219-1.tc.ph.cox.net [70.171.219.1]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: brian) by duncanmultimedia.com (Postfix) with ESMTPSA id 8D2973440069 for ; Wed, 30 Dec 2020 17:40:15 -0600 (CST) Subject: Re: Built for Failure X-Been-There: duncanmultimedia.com To: plug-discuss@lists.phxlinux.org References: Message-ID: <7e3f2377-3e61-433d-9b3e-ce5cb73198e1@SnapTek.com> Date: Wed, 30 Dec 2020 16:40:14 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-BeenThere: plug-discuss@lists.phxlinux.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Main PLUG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Brian Cluff via PLUG-discuss Reply-To: Main PLUG discussion list Cc: Brian Cluff Content-Type: multipart/mixed; boundary="===============7494068014729349466==" Errors-To: plug-discuss-bounces@lists.phxlinux.org Sender: "PLUG-discuss" This is a multi-part message in MIME format. --===============7494068014729349466== Content-Type: multipart/alternative; boundary="------------F4DB568AE4458E8A59B574F1" Content-Language: en-US This is a multi-part message in MIME format. --------------F4DB568AE4458E8A59B574F1 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit How many drives are you talking about using.  If you have a bunch of them, like 6 to 9 drivers, you could combine them into 2 or 3 groups of roughly equal size and then make a each chunk a RAID 0 and then RAID those chunks up with either RAID1 or RAID5/6 depending on how much redundancy you want.   You could also reserve a couple of drives as spares if you wanted then to be able to automatically rebuild the drive if any of the drives fail. Brian Cluff On 12/30/20 3:00 PM, Seabass via PLUG-discuss wrote: > > Weird question: > > I can get a bunch of ancient (~2013) HDDs. Each have varying amounts > of space, and few (if any) are ever the same size. > > These were marked to be disposed, though that is just because of age > or having plenty that are better. Thus I can take them. However, them > being this old, and having found about 3 that eventually broke or > never worked, I'm left with this question: > > Because purchasing new drives takes too long (no idea when/if they > would arrive), I can take as many of the decommissioned drives I'd > like. Seeing as some failed, how does one build a system that is > resilient to drives failing? > > It can be reset as much as wanted, hardware is literally in arm's > reach, and there is not burning need for it to be up immediately. > There is also massive (comparatively) external drive space and as many > live boot USBs as one might desire. > > So how would one build a system that is designed expecting HDD failure > regularly? > > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > https://lists.phxlinux.org/mailman/listinfo/plug-discuss --------------F4DB568AE4458E8A59B574F1 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit How many drives are you talking about using.  If you have a bunch of them, like 6 to 9 drivers, you could combine them into
2 or 3 groups of roughly equal size and then make a each chunk a RAID 0 and then RAID those chunks up with either RAID1 or RAID5/6 depending on how much redundancy you want.   You could also reserve a couple of drives as spares if you wanted then to be able to automatically rebuild the drive if any of the drives fail.

Brian Cluff

On 12/30/20 3:00 PM, Seabass via PLUG-discuss wrote:

Weird question:

I can get a bunch of ancient (~2013) HDDs. Each have varying amounts of space, and few (if any) are ever the same size.

These were marked to be disposed, though that is just because of age or having plenty that are better. Thus I can take them. However, them being this old, and having found about 3 that eventually broke or never worked, I'm left with this question:

Because purchasing new drives takes too long (no idea when/if they would arrive), I can take as many of the decommissioned drives I'd like. Seeing as some failed, how does one build a system that is resilient to drives failing?

It can be reset as much as wanted, hardware is literally in arm's reach, and there is not burning need for it to be up immediately.
There is also massive (comparatively) external drive space and as many live boot USBs as one might desire.

So how would one build a system that is designed expecting HDD failure regularly?

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss

--------------F4DB568AE4458E8A59B574F1-- --===============7494068014729349466== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tClBMVUct ZGlzY3VzcyBtYWlsaW5nIGxpc3QgLSBQTFVHLWRpc2N1c3NAbGlzdHMucGh4bGludXgub3JnClRv IHN1YnNjcmliZSwgdW5zdWJzY3JpYmUsIG9yIHRvIGNoYW5nZSB5b3VyIG1haWwgc2V0dGluZ3M6 Cmh0dHBzOi8vbGlzdHMucGh4bGludXgub3JnL21haWxtYW4vbGlzdGluZm8vcGx1Zy1kaXNjdXNz --===============7494068014729349466==--