Skip to main content

QNAP 459U-RP: first impressions

I recently added a dedicated storage box to my lab environment. After a week these are my first impressions:

Pro:
  • Small. I needed a shallow rack-mountable device, and this one is perfect, only about 50cm deep.
  • Fast. I knew that a NAS device like this wouldn't be the speed king of the storage world, but I'm pleasantly surprised.
  • Open software. It runs Linux, you get SSH access to your device, and you can add packages if you want. Evidently, I added tools like dstat to keep an eye on things.
  • Compatibility. Used it from Windows Vista, VMware vSphere, and Linux (CentOS and others). No problems at all.
  • Cheap. I could have gone for an EMC Symmetrix instead, but decided against it :-)
Con:
  • Fragile. Just a bit. The SATA ports of the disk drives slide directly in sata plugs inside the device. I hope I won't have to re-plug drives all too often.
  • Not all operations happen online. QNAP advertises RAID1 to RAID5 migration, and it does that, by using one of the mirrored drives and the new drive to build the RAID5 array, then moving the data from the broken mirror to the incomplete RAID5 array. You'll be seeing a different filesystem after the data move.
  • Robustness. One of the four drives I bought with the device (WDC-something-FYPS SATA disks) was DOA. The QNAP refused to use the slot that was occupied by the faulty drive, until after a power cycle.
  • Bugs. All software has bugs, and this version of the firmware has a bug in the iSCSI configuration wizard. I'll put my VMs on NFS for now...
  • No VLAN tagging support. I've got a separate IP storage VLAN, and to see the QNAP on both the regular LAN and the IP storage VLAN, I need to use one interface per VLAN. Why not support VLAN trunking ? The 8021q driver is already in the QNAP software, but the vconfig utility isn't, and the web interface would need to support it as well.

Comments

PiroNet said…
Hi Bert, this is a good buy. Not as powerful as an EMC Symmetrix though :)

I've just bought an Intel X25-M to put in my TS-459... I expect crazy perf!

Cheers,
Didier
bert said…
Firmware 3.3.0 solved my problem with the iSCSI config wizard.
And BTW, I have an Intel X25-M in the Linux PC I used for storage before I had the qnap. 1Gbps iSCSI is clearly the bottleneck there...

Popular posts from this blog

How to solve "user locked out due to failed logins" in vSphere vMA

In vSphere 6, if the vi-admin account get locked because of too many failed logins, and you don't have the root password of the appliance, you can reset the account(s) using these steps:

reboot the vMAfrom GRUB, "e"dit the entry"a"ppend init=/bin/bash"b"oot# pam_tally2 --user=vi-admin --reset# passwd vi-admin # Optional. Only if you want to change the password for vi-admin.# exitreset the vMAlog in with vi-admin These steps can be repeated for root or any other account that gets locked out.

If you do have root or vi-admin access, "sudo pam_tally2 --user=mylockeduser --reset" would do it, no reboot required.

Volkswagen UHV bluetooth touch adapter & its problems

My Volkswagen car has the "universal cellphone preparation" UHV built-in. This is the main part of a car kit, but requires an additional adapter for connecting to a cellphone. At first, I was using an adapter for my good old Nokia 6310, even after I changed to the Nokia E71. Connecting was easy: pair the phone with the "VW UHV" bluetooth entity, and done. This has the phone connected to the car kit at all times, so even non-call-related functions use the car audio system (e.g. voice recognition).
But progress will have its way, no matter what happens. So in comes the "bluetooth touch adapter". Instead of a phone-specific adapter, this is a small touchscreen device that slots into the UHV dashboard mount. Connecting a phone is very different now:
the Bluetooth Touch Adapter connects to the "VW UHV" device via bluetooth
the phone connects to "Touch Adapter" device, also via bluetoothThe device doesn't allow step 2 if step 1 didn't s…

Multiple VLANs on a Synology NAS

Synology, like other SOHO/SMB NAS vendors, touts VLAN functionality with their current DSM 4.1 software. However, the web interface just lets you specify one VLAN tag to use over each eth interface (or bond interface).
Manual approachIn the busybox environment that you can ssh into as root (after enabling ssh through the webinterface), there's all the tools you need to use multiple VLANs over one link (eth or bond), however:
First you insert the 802.1q module into the Linux kernel:
 /sbin/lsmod | /bin/grep -q 8021q || /sbin/insmod /lib/modules/8021q.koThen you add each VLAN you need to every interface (bond0 in this example)
 /sbin/vconfig add bond0 4And finally you can configure IP addresses on every interface.vlan combination (bond0.4 in this example)
 /sbin/ifconfig bond0.4 192.168.4.1 broadcast 192.168.4.255 netmask 255.255.255.0The same type of script would work on a QNAP NAS too, by the way. They offer 8021q.ko and vconfig in their commandline environment as well.
Packets from…