Synology

 

Introduction

Recently I retired my DroboFS and replaced it with a Synology 1812+ (link). I was able to scrounge up 4x2TB and 4×1.5TB drives to get it started with. I opted for the RAID-5 configuration for performance and expansion reasons (This way the 4×1.5TB can be replaced with 4x2TB and the array will grow).

In this section of the blog, I will be covering the basic things that I’ve done to get my synology 1812 in good working order.

 Package Management – ipkg

By default BusyBox comes with minimal package management features. As such, we can easily add ipkg.


Then when that finished downloading…


Okay now its installed, you can remove the script:


Now if using DSM 4.0 or greater, you need to comment out the PATH and EXPORT statements in /root/.profile (so vi /root/.profile and put a # infront of those two lines)

First we need to update ipkg


 

 

Installing the basics

Everytime I’m going to be using a *nix machine for more than a couple logins, I always install a few tools that I routinely use:


rtorrent + ruTorrent

After removing ipkg’s wget, ipkg fails to work any longer


To fix this you need to get two files:

  1. libidn_1.25-1_i686.ipk
  2. wget-ssl_1.12-2_i686.ipk

Then install them


 

Additional Ram

The unit I purchased came with 1GB of RAM, so I decided to max this out (the max is 3GB, I read a report somewhere of someone who tried putting 4GB total, and while the system recognized it, it create stability issues).

The RAM from Synology seemed over-priced, so I picked up some comprable memory from amazon (link).

Installation was simple (remove a couple screws and there’s a RAM slot right there easy to access). Less than 5 minutes over all.

Highly recommend a RAM upgrade, no point in spending $1000 on a NAS and then not spending the extra $50 on RAM.

 

Synoogy 1812 + VMWare ESXi iSCSI

I started migrating my iSCSI targets over to Synology, and noticed a few things right away. First off, unless you are going to dedicate your entire raid volume to iSCSI, you have to do file system based iSCSI, which is alot slower.

It also appears that you can only map one datastore in ESXi per LUN, so that begs the question, is it better to use 1 datastore in ESXi located on 1 iSCSI target / LUN on the Synology for each virtual machine? Or is it better to use a datastore + iSCSI target + LUN for each virtual machine?

For simplicity sake, I’m going to give the former a try initially, that is I’m going to setup one big datastore and then create all my VMs within that one datastore. That way only one iSCSI target and LUN are needed.

Leave a Reply