public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  homemade nas setup
Date: Fri, 30 Jan 2009 23:00:22 +0000	[thread overview]
Message-ID: <49E33303-F36B-490F-AFEA-E42962D1E318@stellar.eclipse.co.uk> (raw)
In-Reply-To: <87y6wtlksy.fsf@newsguy.com>


On 30 Jan 2009, at 00:06, Harry Putnam wrote:
> ...
> A few I can think of are space and noise.. but having never been
> around our run a nas setup... I'm not sure if that is really true.

Power consumption, too. I think some of the off-the-shelf mini-NAS use  
a low-power MIPS processor.

I like a "real Linux" server rather than an off-the-shelf mini-NAS  
because you can do so much more with it. I rip DVDs & download  
torrents on the headless server, as this saves me having to leave my  
workstation on overnight.

Unfortunately "all the other stuff" is a considerable reason I had to  
rule out Solaris, which I would like to have used for its ZFS file- 
system. I felt I probably wouldn't like the package manager, and I  
didn't seem to be able to find supported hot-swap controllers. There's  
just loads of stuff I know I'm more easily going to be able to find  
help with on Linux.

But mini-NAS does really well for many people. I found the problem  
with going it myself to be feature creep - I want room for plenty of  
drives and once you've got a server running 24/7 there's always  
something else you can "usefully" run on there. I ended up buying one  
of these <http://www.tstcom.com/product_details.asp?id=4> and a 3ware  
9500 RAID controller - this has turned out pretty expensive but I  
think worth it to me, as it should last me a long time. I am just  
about to build.

3ware's customer support, BTW, is second-to-none - if buying one of  
their controllers on eBay ask the vendor to check the serial, as many  
are still under 3ware's no-quibble 3-year warranty. My experience with  
their tech support has been excellent, and will make them first choice  
for hardware in the future.

Stroller.




      parent reply	other threads:[~2009-01-30 23:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30  0:06 [gentoo-user] homemade nas setup Harry Putnam
2009-01-30  0:44 ` Matt Harrison
2009-01-31  1:29   ` [gentoo-user] " Harry Putnam
2009-01-31  8:36     ` Matt Harrison
2009-01-31 15:37       ` Harry Putnam
2009-01-31 16:05         ` Matt Harrison
2009-01-30 10:43 ` [gentoo-user] " Peter Humphrey
2009-01-30 18:30   ` [gentoo-user] " Harry Putnam
2009-01-31 11:39     ` Peter Humphrey
2009-01-30 11:56 ` [gentoo-user] " Norman Rieß
2009-01-30 12:05   ` Neil Bothwick
2009-01-30 18:33   ` [gentoo-user] " Harry Putnam
2009-01-30 22:48     ` Norman Rieß
2009-01-30 23:24       ` Harry Putnam
2009-01-31 11:22         ` Norman Rieß
2009-01-30 23:39     ` Stroller
2009-01-30 23:00 ` Stroller [this message]

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=49E33303-F36B-490F-AFEA-E42962D1E318@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --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