Last week, a drive in my server died. These drives weren’t really that old, but were Seagate’s from the drive failing epidemic a few years back. I bought 6 drives around this time, 4 for the server in a RAID 10 array, 2 for my workstation. I lost 1 to the failure problem, and the rest I managed to get updated firmwares installed in time.
Since then, I have been extremely leery of Seagate drives. My server ran Windows XP (yes), and used the on-board Intel SATA RAID controller of this MOBO. On several occasions, the RAID integrity would fail for no good reason upon bootup, that I simply stopped turning my server off.
My brother the “professional network admin” has been reminding me for years that Software Linux RAID is the best RAID. So after this tragic failure (no data lost, just some hair), it was time for something different.
My brother and I have been talking NAS (Network Attached Storage) devices for a while, he himself trying a few over the years, to really sub-par results. Generally, the prices were terrible for completely sub par hardware that couldn’t perform. Popular NAS like the Drobo start at like $700, yuck! The best bang for buck always seemed to be building a server.
Actually, bang for buck wise, building your own file server is still cheaper. But Linux is a delicate mistress. I am a coder, and dealing with game console development tools and Linux setups over the years has taught me how to live comfortably in Linux. I work on Windows though, just I do it with Cygwin and MinGW/MSys.
That aside, there is still too much sh*t to learn about Linux. Time is money. Building and maintaining another server, I’ll be honest, I don’t want to do it (FreeNAS was suggested on my Twitter, for anyone in a more adventurous mood).
It’s 2011, give me a drop in solution that’s cheap, small, fast and good!
Blam! Hello Synology DS211j!
This 2 drive consumer model rakes in at around $200, size not much larger than an eternal casing, and sporting a 1.2 GHz ARM processor. ARM! Hey! I know those!
It runs a breed of Linux, interfaces via gorgeous fast HTML UI, and support fancy Linux favorites like SSH out-of-the-box. Well not quite out-of-the-box, as you do need to download the latest firmware and a setup tool for your OS, but that’s easy.
Mine I filed with a pair of 3TB Hitachi Deskstar drives, spinning at 7200 RPMS with 64 MB of cache. Western Digital Caviar Green drives were $40 cheaper each, but are known to be slow and problematic on RAIDs (though there are fixes, a tool WDidle3 seems to address this). Again, time is da mon-nay, and wanted something I could just drop in. Benchmarks said these drives were better overall performers too, so hey, why not!
Hardware setup was a matter of unboxing, opening it (sliding case sides front and back to unlock), plugging my drives in, screwing them in, and closing the casing (opposite of opening). I think I had this done in 5 minutes, max. Didn’t even need a manual.
Building the array I wanted (MODE 1) was extremely straightforward, that I wont both talking about it.
What I will talk about is some of the advanced stuff I wanted from it, and the configuring done to make it act accordingly. After all, this blog post is actually for me, so I can know what I did in case I need to reproduce it.
* * *
The main thing I wanted was to move my SVN repository over. I enabled SSH, connected to it using putty, then followed the instructions here:
The subversion guide sends you to the bootstrapping guide, which explains how to get the ipkg package manager installed, which you need to get other standard nix tools. Save yourself minutes of reading and go right to the bootstrap section.
Omitted from that guide is the obvious question of what CPU is inside? It seems Synology has changed processor types a few times over the years (was even PowerPC for a while), but here is a complete list. The 2011 models, specifically the j “Budget” models feature a “Marvell Kirkwood mv6281 1.2Ghz ARM Processor” (i.e. the 2nd last option).
Following the subversion guide, once I got up to the reboot stage, I was done. I was able to copy my existing repository over to the device, and it worked almost immediately. Fantastic!
* * *
For no good reason, I also wanted development tools installed.
As it turns out, /opt/ maps to part of the /volume1/ partition. The packages are set-up in such a way that anything not firmware should be stored inside opt.
So to get development tools, you ask for the optware development package.
ipkg install optware-devel
Anything you build should be built from the opt directory.
More details here.
I ran in to problems getting optware-devel installed. wget-ssl was complaining about the existence of wget. No problem! Uninstall it, then manually install wget-ssl.
`ipkg remove wget</p>
ipkg install libidn
ipkg install wget-ssl` Actually, both of these operations will fail (WUHT!). But what they will still do is download the respected packages. You can then invoke manual installation of both with the package names (tip, use your tab key to autocomplete). `ipkg install libidn_1.19-1_arm.ipk
ipkg install wget-ssl_1.12-2_arm.ipk` Again, those package names should reflect the actual versions you downloaded in the prior step, as they will be newer. Now optware-devel should safely finish. `ipkg install optware-devel` Congratz! You now have GCC installed on your NAS! Cool! \* \* * Since getting that working, I’ve moved some more important files over. My FLAC encoded music collection for one. I’ve been streaming FLAC music CDs for a couple hours now as I worked on migrating more important data over. So far so good.
mv S88synomkflvd.sh _S88synomkflvd.sh` The stupid processes make @eaDIR folders under all directories containing JPG’s and video files. Now if I had a process to delete all the @eaDIR contents, I’d be in luck. Oh, and thumbs.db’s should go too. That Mac one as well.