I’m ok with the ad-supported business model, but when on the screen I find 10 (ten!) advertising for the same computer vendor I feel a strong urge to get some ad-freedom. Often times the ads are not static, but dynamic and this obsoletes older computer faster than strictly needed. This motivates me even further.
Fast forward a few years and I moved to Singapore without bringing the server over, but still needed a baseline level of ad-freedom. For a while I used OPNsense (running on a Kodlix GK45) for this purpose, but after a few (several) months I grew tired of Suricata turning off seemingly randomly on the box (with little useable logs to troubleshoot and no improvement with the OPNsense patches) and sometimes the DNS service doing just the same. The OPNsense box got decommissioned (it is waiting to be repurposed) and a Unifi USG (I had it sitting around unused since in Italy I moved to a Sophos firewall for my dual-wan needs) took over the basic firewall duties leaving me with my ad-invasion problem again.
Sunday last week I thought it was a good idea to get rid of my ad problem leveraging my recently purchased Synology DS120J in tandem with a used DS115J (yes, I did learn from the DS411Slim experience that a NAS is a single point of failure even when is supporting multiple disks). Because I went through the process in the past I thought it was going to be a matter of a few minutes and a good idea to relax a bit during my study session for the AWS Certified Solutions Architect – Professional exam.
After almost 30 years dealing with computers I should have known better that often times “few minutes” becomes “few hours”. In this case the time-stretching happened because I’m running DSM 7.0 instead of DSM 6.x like in my previous NAS and Synology in this major version changed the way some of the built-in services are managed. Because of this change the directory structure changed too and the original script didn’t work out of the box anymore. The former: /etc/zone/data/ in DSM7 becomes: /volume1/@appstore/DNSServer/named/etc/zone/data/
After hammering here and there for a while I got to a hack that seems to be working for me. If someone wants to take a look at it I attached it in the GitHub issue here. The usual disclaimer apply: there is no guarantee implied or expressed that it will work for anyone else, it’s totally unrelated to my current or past job and employers, and if the script is used I bear no responsibility for anything bad happening. You can read at the bottom the full, wordy, detail.
Because I passed my certification exam last Friday (Friday the 17th, what an auspicious day did I pick!) I feel much less guilty now of having subtracted two hours from my study and I hope with this post I will save some time for others trying to follow the same approach.
In this second fix attempt I purchased a thermal adhesive from Akasa and using a filer I adapted a heat sink that I had hanging around so that it would fit with the bolts that keep the heat spreader attached to the electronic board.
High hopes as before, but the file compression test failed again. The interface is working and the heat sink gets very hot.
Unfortunately it seems that the more heat I remove from the CPU the more gets generated.
Indexing videos generated the very same behavior.
I’m running out of ideas and I’m starting to challenge the idea of getting a DS414Slim to make a fail-resistant setup.
I see no point in investing in another Synology as the first one is constantly failing.
It is too bad because the management software is very nice and powerful.
Anyone that has an idea on what to try next is welcome to comment to this post.
Below are a few snapshot of the hack.
Factory fit heat spreader with connecting bolts that require heat sink adaptation.
1st corner of the heat sink filed
2nd corner filed
Interference check with the filed heat sink before bonding
Side view of the bonded heat sink
Side view with the 3 drives in place before the insertion of the empty disk frame.
I’ve reported a problem with my nas a few weeks ago (here) and my plan to get it back to productive work in a reliable way.
As part of this plan I did order a OEM replacement fan: searching an equivalent model with the same small connector proved to be a waste of time.
After a few weeks it finally arrived and yesterday I picked it up at the shop and replaced it in the NAS.
The old fan had some substantial play in the axial direction and at low-speed failed to spin up, for this reason I had high hopes with the replacement.
It was a quick job requiring only 15 minutes and then I was ready to use the NAS.
Mirror rebuild worked fine, compressing a file with the PC CPU with source and destination on the NAS worked fine.
Active disks were at 43C and the CPU at 48C during the rebuild; a few minutes after it was completed the disks were down to 35C and the CPU at 43C.
With 19C of ambient temperature this is not an extraordinary achievement, but are manageable temperatures.
I felt confident, even if not overly confident, that the fix was going to work as desired.
To be sure that this was really the case and that the overheating was not going to hit me unexpected in the future I did a heat torture test by compressing a 140GB file using the NAS CPU instead of the PC CPU.
This time unfortunately the NAS did behave as with the older fan: after some time it died on me.
The latest reported CPU temperature in the web interface was 54C and it survived long enough to put a warning in the web interface telling me that it could not compress the file.
The NAS couldn’t be reached anymore (no web interface, no ping, no Synology assistant) and couldn’t even be restarted using the power button.
Next step will be to mount a heat sink on the current nonremovable stock heatspreader.
I have already found a suitable heat sink, now the challenge is to find the needed adhesive thermal pad.
I will lose the ability to use the 4th disk slot, but it is acceptable because future space expansions will likely come via a DS414slim for additional redundancy and performance.
And I still have the LS220D that can maintain some of the lower value data.
At the end of 2014 my Synology DS411slim decided to abandon me and a couple of weeks ago I have purchased this nas to store the data in the Synology until I could put some more thinking into an appropriate fix/hack/replacement.
I expected that the LS220 would be no match for the higher end brands in the SOHO area, but still I couldn’t help the first thought: cheap plastic.
Once it is filled with the two disks it feels a bit better thanks to the extra weight and reduced flex that they warrant to the device.
The setup was fairly smooth even if the quick startup guide could be better and the UI was all but exciting.
The same feeling as before: cheap.
In the end all I need in the short run is a SMB share to copy as much data as possible from the DS411Slim while it works before overheating.
For this basic use I consider the device as a good fit for a very convenient price, but then comes in the performance in my environment.
The best sustained writing rate I could get so far is 28MB/s on a cabled 1Gbit link while using disk2vhd to backup my notebook (98GB in about 57 minutes).
Compared to the 37-40MB/s that I was getting on the 4 years old DS411Slim (see this old post about encrypted vs. unencrypted writing speed I was experiencing) this is not a good number for this workload and makes the LS220D less suitable for one of my key use cases.
To conclude: if you have a pair of spare 3.5″ drives in a drawer the LS220D is an expensive way (I paid mine 69.99€) to put them to work for the benefit of the entire house.
If you are planning to purchase the drives for the purpose of putting together a NAS you should really shop for a higher class NAS than the LS220D.
It was a while that I was traveling quite a bit and giving little attention to my home NAS.
It was getting stuck from time to time but I was not really worried.
For Christmas I had some spare time and decided to do some much-needed backup: the notebook to the NAS and then the NAS to a USB disk that I usually keep disconnected to be on the safe side.
Things did not work out as planned because the DS411Slim was not running long enough for me to complete even the first step.
Status led a solid blue, network led blinking, but no data movement at all and it will not shutdown using the physical button.
Only way to restart the NAS was plugging the power and as you know this is not the nicest thing to do to a disk with data being written to it.
I did it once.
I did it twice.
I did it one time too many and got the status led blinking nonstop.
One of the disk’s metadata was corrupted and the mirror diskgroup in degraded state.
Situation was bad but not tragic: I decided to reverse the order of activities and do the NAS backup first using the disk still working.
This worked fine.
Then I decided to hack the fan control file to make the fan spin faster as suggested in and then did the notebook backup using from Microsoft.
This worked fine again.
I felt all my problems were fixed, but I was soon proved wrong.
Due to the scarcity of space on the share I decided to let the NAS compress the .vhd file by issuing the command through the web file manager and I got hit by the CPU overheat issue again even if the fan was clearly spinning (relatively) fast.
I did another try at the compression after restarting the NAS and it went down again: cpu in the web interface appeared to be in the 52-53 celsius last time I checked before going to sleep, but in the morning the system was stuck again.
I have almost alternatives: I have to mod the device.
One option is to replace the fan: maybe it just got tired after a few years and can’t spin as fast as it should.
Another option is to use a thermal adhesive to attach a finned heat sink to the CPU: the heat spreader (irreplaceable) is absolutely untouchable (I mean burning) when the system is blocked hence it can clearly benefit from a better heat dissipation.
Before I go down this road I need to have a failsafe solution hence I ordered a cheap Buffalo LinkStation 220 with a pair of 1TB disks where I will copy all the content of the Synology.
Earlier today, after a complete backup of the critical data (300GB) to an external USB drive, I’ve made the upgrade to the latest release.
It took, as is usually the case with the “update” releases, two rounds of firmware upgrade: one to the base version (5.0-4493) and one to the “update 2” version.
The process worked smoothly and without hiccups and now the speed seems slightly improved, but still far from the 4.3 performance.
I keep my finger crossed hoping that future releases will give me back the old performance and that I’ll find no nasty surprises in this new release.
I’ve written in the past a few posts about this small nice NAS: here, here, here and here.
Yesterday I did another test after updating the complete local copy of my gmail messages on Thunderbird.
It took 4 hours 33 minutes to compress 11,548,610,909 bytes (578 Files, 61 Folders) to a single 7zip file of 7,108,652,903 bytes: it is a lot of time.
16.380 seconds of runtime means an average read/write speed of 1.139.027 bytes per second.
Both the NAS and the computer I used are connected with 1Gbit copper ethernet to the same switch: during the process the usage stats on the windows 7 (64 bit) machine indicated almost no load and the same was true for the NAS according to the web interface.
The DS411slim is running version 4.2-3202 with 3 HDDs in a single disk group using SHR (Synology Hibrid RAID)
This is really puzzling. And a bit upsetting.
Any suggestion to recover from this bad performance is welcome.