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: Sat, 12 Dec 2020 18:26:46 +0100 [thread overview]
Message-ID: <87lfe3kka1.fsf@ambrevar.xyz> (raw)
In-Reply-To: <d0becfef-5d1f-876c-c218-d114608d7082@edno.moe>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
Hi zloster!
Thanks for the detailed report and the resourceful links! :)
After some investigation, I think I'll go for one of the ASRock.
I could find them at the following price:
- ASRock J3455-ITX: 98€
- ASRock J4105-ITX: 100€
- ASRock J5005-ITX: 120€
- ASRock J5040-ITX: 150€
I'll go for the cheapest option.
No the j3455 and the j4105 are basically the same, the main difference
being memory.
j3455 has SO-DIMM 204 pins (DDR3)
j4105 has SO-DIMM 260 pins (DDR4)
Any recommendation regarding memory? Has DDR3L a lower power consumption?
For the rest, I'll just get a second hand computer for 30-50€ that has a
4GB of RAM, so I can get the whole thing to run on 130-150€. In that
sense, it's cheaper than any NAS I can find on the market! :)
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2020-12-12 18:37 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
2020-12-11 15:32 ` zloster
2020-12-12 17:26 ` Pierre Neidhardt [this message]
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=87lfe3kka1.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).