unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: zloster <more@edno.moe>, david larsson <david.larsson@selfhosted.xyz>
Cc: help-guix@gnu.org,
	Help-Guix <help-guix-bounces+someone=selfhosted.xyz@gnu.org>
Subject: Re: NAS hardware recommendations
Date: Thu, 10 Dec 2020 15:43:11 +0100	[thread overview]
Message-ID: <87zh2lyb5s.fsf@ambrevar.xyz> (raw)
In-Reply-To: <2c2aab7f-3b77-4fbe-c3fd-327c2f8aa58a@edno.moe>

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

Hi zloster!

> https://wiki.kobol.io/helios64/intro/

Neat!  I like it a lot, seems to be ticking all boxes!
Except that I can't buy it :(
Still hunting for a retailer...

> Also for DIY low powered home NAS you could check the mini-ITX 
> motherboards with the embedded CPUs and some computer case like Fractal 
> Design Core 500 (4 3,5" bays + some 2,5" physically separate bays). Of 
> course you will NOT get externally accessible drive bays.
> In fact I use the following components for a home server (4 years 
> currently):
> Motherboard: 
> https://www.gigabyte.com/Motherboard/GA-N3150N-D3V-rev-10/sp#sp - 4 SATA 
> 3.0 ports and 2x1Gbps Ethernet
> Case: Fractal Design Core 500
> RAM: 2x8GB DDR3L (laptop)
> Power supply: Corsair VS400 or VS450 ATX (I don't remember)

This could be an option indeed.
Any idea how much the above would cost?
And what's the power consumption?

Cheers!

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]

  reply	other threads:[~2020-12-10 14:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 15:51 NAS hardware recommendations Pierre Neidhardt
2020-12-09 16:46 ` david larsson
2020-12-10 10:47   ` zloster
2020-12-10 14:43     ` Pierre Neidhardt [this message]
2020-12-11 15:32       ` zloster
2020-12-12 17:26         ` Pierre Neidhardt
2020-12-12 19:21           ` Efraim Flashner
2020-12-12 19:51             ` Pierre Neidhardt
2020-12-13  6:37               ` Efraim Flashner
2020-12-15 16:38           ` zloster
2020-12-19 10:21             ` Pierre Neidhardt
2020-12-20 10:26               ` Dr. Arne Babenhauserheide
2020-12-10 11:53   ` zimoun
2020-12-10 14:41   ` Pierre Neidhardt
2020-12-10 20:57     ` david larsson

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zh2lyb5s.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=david.larsson@selfhosted.xyz \
    --cc=help-guix-bounces+someone=selfhosted.xyz@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=more@edno.moe \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).