There are a lot of threads on unofficial RAM upgrades that work or don’t work on the Synology ds920+.
Just for context, the Synology ds920+ comes built in with 4GB RAM soldered in and has one expansion slot. The official maximum is 8GB, and Synology sells an official 4GB RAM stick (model: D4NESO-2666-4G) for this. However, there are many anecdotal reports that adding 8GB and 16GB RAM also work.
By running a handful of applications and Docker containers, I was maxing out the built in 4GB of RAM and spilling into swap space which slowed down the entire NAS to almost a standstill.
However, the NAS seems to be pretty finicky in what RAM it accepts or not. My first attempt was with a Kingston Fury Impact 8GB, but I could not get it stable. The system would lock up after a few minutes, if it booted up at all. I suspected that it was incompatible, although it is possible it was just the stick was bad.
Not wanting to spend more time, I went for Crucial CT16G4SFD8266 16GB upgrade. Crucial. This was recommended on other sites as well. Lo and behold, it worked the first time I put it in, and also the Synology DSM did not have any notifications that the RAM was unsupported.
So if you’re looking for an upgrade for your ds920+, go for the recommended Crucial ones, even if it’s slightly more expensive. It will save you time and headache.
Some of the links above may be Amazon Associate links and I may earn from qualifying purchases.
I’ve had my Synology Diskstation ds415+ network attached storage device since late 2015, replacing my custom FreeNAS box. It came with 2GB of RAM, which is fine for basic file serving, but limited when running multiple applications, including Docker containers. Once applications start swapping onto the hard disks, everything starts grinding to a halt. I finally reached the breaking point on this last night when I had to reboot the NAS once more.
I have a Virtual Private Network (VPN) setup so that I can connect to my home network and use things such as my Synology file server when I’m not at home. This works most of the time when the IP address network of the local (e.g., Wi-Fi hotspot, etc.) doesn’t conflict with my home’s IP address network (10.x.y.0/24). However, I have come across some Wi-Fi hotspots which use a subnet of 10.0.0.0/8. The default route through the hotspot network is then used when I try to access my home resources, instead of going through the VPN.
My apartment building has an old hard-wired Enterphone intercom to buzz visitors in. This poses a slight annoyance since the dependency of the phone line in conjunction with a conventional corded telephone means I have to walk to the phone in order to answer the intercom.
Given the low rate of visitors and the small size of my apartment, in retrospect, this isn’t really a big deal. Most normal people would just buy a cheap cordless phone and call it a day.
But that only helps if I’m in the apartment. What if I wanted to be able to buzz myself in if I somehow got locked out?