The two are in different buildings that are networked via fiber optic lines, in case one building burns down. I have a second 1812+ that automatically mirrors the first. Six of the drives are configured as a Synology Hybrid RAID, allowing two drives to fail without data loss and the seventh drive is designated as a hot spare, which the Synology will utilize if any of the other drives fail.
My DiskStation is currently loaded with seven 3 TB disks from the Western Digital Red line (with firmware optimized for NAS use). Then in 2012, I bought my first Synology DiskStation DS1812+, an 8-bay NAS appliance that supports multiple RAID configurations with hot-swappable, usersupplied drives. Meanwhile, I repurposed my retired, rack mount “Franken-Mac” into an iTunes and general media server by installing a RAID card and OS X Server software. Over the years, I upgraded the Dell’s disks until I hit the controller’s hard limit of 3 TB total.
#Synology os x server windows
A few years later, as my storage needs outgrew the Snap, I installed a Dell rackmount RAID running Windows Server, with a SCSI tape drive for additional backup. My first NAS appliance was a 10 GB Quantum Snap Server that I purchased for $499 back in 2000. I would be very grateful to hear whether others have experienced this issue, and whether my workaround resolves it for them.For almost two decades now, a crucial component of my cross-platform file-sharing and backup strategies in my home and personal studio has been Network Attached Storage (NAS). As the fix involves clearing the SMB cache on the Synology box, I can only assume that it is almost certainly not a macOS issue as such.
#Synology os x server how to
At least I now know how to resolve it, but it is really annoying that I have to do so. This is very frustrating as it is the only thing that causes any issues with my Macintosh and Synology combination. The task that needs to be created in the Task Scheduler is (DSM 7+) synosystemctl restart rvice, which needs to be run as root.įor DSM 6.2 it is /usr/syno/sbin/synoservice -restart samba, again run as root. If I either clear the SMB cache or restart Samba then these tasks complete instantly, and accessing files from the SMB share continues to be fast until the next time that the problem develops.Ī workaround that I have employed is to create a scheduled job to restart Samba every 30 mins during work hours, and that seems to have resolved the issue for the moment, but I would prefer that Synology address this problem. It could simply be the length of time that the share has been mounted, or the number of files that have been saved to the share.Īnother symptom once the problem occurs is that browsing from the Finder takes a long time to list files in folders. I imagine there is something that triggers it but if so I do not know what it is. Note that this does not happen until the share has been mounted for a while.
#Synology os x server pdf
As above, once the problem occurs I can resolve it instantly by either clearing the SMB cache using the button within File Services->SMB->Advanced Settings->General, or restarting Samba from an SSH session.įor an example of what happens once the problem has started, if I simply try to save a file from Preview (specifically a PDF in my case, but I think this happens with other file types as well) to a SMB share on my NAS, Preview stalls with a beachball. Basically it seems that after a very short while a problem develops linked to the SMB cache. However if anything the problem is worse. DSM7 has a much more up-to-date version of Samba (4.10.18) than used to be the case with DSM6.2 (4.4.16 at last count). I updated my NAS (a DS418Play, as detailed above) to DSM7.0-41890, hoping that would resolve the issues I have been experiencing with SMB shares from a Macintosh (running Big Sur 11.5).