DS1010+ Upgrade Path

Overview

The Synology DS1010+ is a 5-bay (expandable to 10-bay by connecting two of these devices together) NAS. As of April 2016, the latest supported version of DiskStation Manager for the DS1010+ is 5.2. However, installing DSM 5.2 straightaway on a blank/new DS1010+ is not possible. The Synology Assistant throws an error and says the boot volume is not large enough for DSM 5.2. It suggests getting DSM 2.3-1161.
So I sought to build my own DSM upgrade path to get to the latest version.

DS1010+ DSM Upgrade Path

Start with the DSM 2.3-1161. You can find a link to it in the References heading below.
Upgrade to DSM 3.0-1372..
Once updated to 3.0, the update checker tool in the “DSM Update” page can find the next available version. Use it to go to DSM 4.0-2228.
From there, it will find DSM 4.3-3827.
DSM 5.0-4528.
DSM 5.2-5644

Conclusion

Basically, I needed to manually install the first version, 2.3-1161. I also needed to manually install 3.0. After that, the software had a tool to download and install the update for itself.

The Synology Assistant tool does not mention this, nor did I find any documentation on the Synology site describing that process. I didn’t look very hard, but I was hoping the User Manual or Quick Start guide would mention something similar.

References

  1. Main support page for DS1010+ https://www.synology.com/en-global/support/download/DS1010+
  2. Specific link for DSM 2.3-1161 https://usdl.synology.com/download/DSM/release/2.3/1161/synology_x86_1010+_1161.zip
  3. DSM 3.0 location https://usdl.synology.com/download/DSM/release/3.0/1372/synology_x86_1010+_1372.pat

Configure SELinux to allow Nagios publickey auth

Nagios is a tool for monitoring servers. In a security-minded environment, you need to make allowances for nagios. It operates over ssh using a public key, which SELinux doesn’t like.

One problem that can occur is that the ~nagios/.ssh/authorized_keys file will not have the right selinux context. Fix that with

semanage fcontext -a -t "ssh_home_t" "/var/spool/nagios(/.*)?"
restorecon -RvF /var/spool/nagios

This will make a new rule in selinux for that directory to have a regular ssh-homedir context, so public keys will work properly. If nagios cannot connect passwordlessly, it will throw fits.