From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Getting maximum space out of a hard drive
Date: Thu, 25 Aug 2022 17:15:38 -0700 [thread overview]
Message-ID: <CAK2H+eer-5d2g=0kt-0taYbdS1R8aOjmhB_mgYk8UUPgd6G43Q@mail.gmail.com> (raw)
In-Reply-To: <12905e2c-f3ad-b7b9-78e1-4604e38f8a8e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
On Thu, Aug 25, 2022 at 4:59 PM Dale <rdalek1967@gmail.com> wrote:
<SNIP>
> I may do some mobo hunting shortly. See what little thing I can buy
> that is powerful enough. I don't think a Raspberry Pi is enough. It
> gets close tho. Biggest thing, I'd need a lot of SATA ports. LOTS of
> them.
Granted, I had a couple of old cases which lowered the cost but
I went to a local computer store and bought used motherboards
that came with processors and memory. They were both Core i7
but I paid only about $75 each. I needed power supplies and hard drives
so each machine ended up around $350 or so by the time I was done.
Each has 2 4TB drives for storage and a 1TB drive for the OS. A lot
of used motherboards have on-board VGA and Gb/S networking.
These are TrueNAS machines, FreeBSD not Linux, but they have
a Linux version now if that makes you more comfortable.
I'd stick with AMD64 as it's better tested and I don't think you'll
get the network throughput you need to be fast with a Raspberry Pi
[-- Attachment #2: Type: text/html, Size: 1295 bytes --]
next prev parent reply other threads:[~2022-08-26 0:15 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 18:04 [gentoo-user] Getting maximum space out of a hard drive Dale
2022-08-18 18:18 ` Rich Freeman
2022-08-19 2:03 ` Dale
2022-08-19 4:26 ` David Haller
2022-08-24 22:45 ` Frank Steinmetzger
2022-08-25 6:22 ` William Kenworthy
2022-08-25 12:43 ` Dale
2022-08-25 12:52 ` Rich Freeman
2022-08-25 15:10 ` Jack
2022-08-25 18:59 ` Dale
2022-08-25 21:08 ` Rich Freeman
2022-08-25 23:59 ` Dale
2022-08-26 0:15 ` Mark Knecht [this message]
2022-08-26 11:26 ` Dale
2022-08-26 11:55 ` Gerrit Kuehn
2022-08-26 12:07 ` Rich Freeman
2022-08-26 23:07 ` Dale
2022-08-26 14:09 ` Mark Knecht
2022-08-26 14:25 ` Rich Freeman
2022-08-26 14:40 ` Mark Knecht
2022-08-26 23:20 ` Dale
2022-08-26 23:37 ` Mark Knecht
2022-08-27 1:16 ` Mark Knecht
2022-08-27 23:30 ` Dale
2022-08-28 9:27 ` Michael
2022-08-28 21:07 ` Frank Steinmetzger
2022-08-28 21:33 ` Wol
2022-08-28 21:53 ` Mark Knecht
2022-08-28 23:31 ` Wol
2022-08-28 21:34 ` Frank Steinmetzger
2022-08-29 5:49 ` Dale
2022-08-29 14:42 ` Frank Steinmetzger
2022-08-29 21:28 ` Dale
2022-08-30 14:26 ` Frank Steinmetzger
2022-08-25 22:41 ` Wols Lists
2022-08-25 23:56 ` Dale
2022-08-26 7:24 ` Wols Lists
2022-08-26 11:27 ` Dale
2022-08-26 13:35 ` Wols Lists
2022-08-26 4:47 ` David Haller
2022-08-18 18:20 ` Andreas Fink
2022-08-20 19:15 ` Dale
2022-08-20 20:57 ` Rich Freeman
2022-08-25 3:44 ` Dale
2022-08-20 21:46 ` Grant Taylor
2022-08-20 21:57 ` Grant Taylor
2022-08-20 22:45 ` Dale
2022-08-21 4:22 ` William Kenworthy
2022-08-21 5:34 ` Grant Taylor
2022-08-21 9:26 ` William Kenworthy
2022-08-21 10:09 ` Dale
2022-08-21 16:47 ` Dale
2022-08-21 5:27 ` Grant Taylor
2022-08-24 22:39 ` Frank Steinmetzger
2022-08-24 22:50 ` Wol
2022-08-22 14:50 ` Laurence Perkins
2022-08-22 15:02 ` Rich Freeman
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='CAK2H+eer-5d2g=0kt-0taYbdS1R8aOjmhB_mgYk8UUPgd6G43Q@mail.gmail.com' \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.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