Qnap HS-210

As you all remember (you do, Blanche!  You do!), I was fussing around with some RAID stuff over USB3.  I had found a solution that worked (a Silverstone cabinet), but then somebody told me about the Qnap HS-210 RAID thingie.  It takes two disks and is fanless.  It seemed perfect, so I bought one to try out.

I had sworn off consumer NAS appliances years ago, because (in my experience) they always suck.  They have weirdnesses in their interfaces, and they’re generally slow.  But now they must surely work, right?  Right?

IMG_0340

So today it arrived.  It looks pretty sleek.  Installation of two 6TB WD Red disks is nice and easy.  If you have a screwdriver.

The instruction sheet only describes how to install the disks and doesn’t say anything about, like, using it.  But I guessed it would just DHCP me, and it did.

So it came up, and I pointed a Firefox from Debian Stale at it.

IMG_0322

And the only possible thing to do was to install firmware on it.  After downloading it manually.

IMG_0320

WTF.  I gave it a try, but it failed.

So I thought that perhaps it just had too many JS-ey items in it an perhaps required a newer browser.  I routed a Fedora laptop to the network…

IMG_0324

And then it started downloading the firmware.

IMG_0325

Of course, I hadn’t really thought it was going to talk to the Interwebs directly, so I hadn’t given it a router address via DHCP, so it just stood like that for 15 minutes until I guessed that that might be the problem.

I switched the thing off and then on again, and then it downloaded stuff successfully.

IMG_0326

And configured itself…

IMG_0327

And…  er…  ok…  it’s…  doing something?

IMG_0332

Hey, it’s up!

IMG_0333

Yeah, that’s what I want to see on the configuration screen of my NAS.

IMG_0334

So social.

Anyway, once you get past the obnoxious bits, the interface isn’t that bad.  Configuring the NFS bits was easy enough, and guessing what the paths were going to end up like was easy enough.

And you can ssh to it.

So I started copying over the DVD files…

IMG_0339

Yeah.  30 MB/s.  And down to 25MB/s later.

IMG_0338

With a load of 8 when it’s working.

 

So, in conclusion:

Like all consumer NAS things, it’s slow as molasses, and it probably works fine out of box if you put it into another box just where it expects to be.  If not, there’s going to be some head scratching to get it to work.

IMG_0341

But the Qnap HS-210 seems better than many devices in this class.  It actually seems to, like, work, and that’s quite something in itself.

Well.  Sort of.  I just go this when rsyncing over to it:

rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: write failed on "/qnap/Beasts of the Southern Wild/Beasts_Of_The_Southern_Wild_t04.mkv": Input/output error (5)
rsync error: error in file IO (code 11) at receiver.c(322) [receiver=3.0.9]
rsync: connection unexpectedly closed (11074 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]

I restarted the rsync, and it seems to be continuing.  Binging a bit seems to suggest that this may be because of network timeouts; i.e., that the NAS is just responding too slowly.  However, I’m not seeing any NFS timeout messages in the log on the client, which you’d expect…

Anyway, it’s a bit sad that I’ve put two disks that, natively, have a writing speed of about 120MB/s.  And I’m running the device in RAID0, so there’s no write amplification.  The theoretical write speed should be 240MB/s.  But it’s a 1Gbps network, which limits stuff a bit.

But a writing speed of one quarter of the wire speed is kinda depressing.  That’s what you get when you put an underpowered CPU into these things.

Oh, well. At least it doesn’t have a fan.

 

2 thoughts on “Qnap HS-210”

  1. You could install Debian onto the HS-210. No specific reason to believe that it would significantly alter the performance, but at least it would then be running known firmware.

    1. True. But it doesn’t seem like it’s worth the bother. Qnap doesn’t seem to have fucked up anything in particular — it seems to be running a pretty stock Linux 3.4 kernel and a Busybox userland. The rather pitiful performance is due to the pathetic CPU in this thing…

Leave a Reply to larsmagne23 Cancel reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s