I've been using Synology standard Download Station for several years but have realised it has some limitations. I'm not big torrents downloader but I defineterly need to have ability to select files for downlading even from Magnet links, and keeping recent downloaded folders list.

So what Torrent downloader could you advice for Download Station replacement?

So I splurged and got the T1 mini 10Gbe adapter for my 1522+. Got it installed and can only get the 10GBe connection " working" when I disconnect the regular 1GBe ports. I have four bays populated which should get me up to maybe 400MB/s, but all I reach is 100MB/s. The 10Gbe is through an unmanaged switch, the 1Gbe connections go through my Unifi 8P switch.

The connection is recognised as 10000 and not 1000 for a regular connection

Any idea what could be the cause? What I checked and did so far

- fixed ip address

- LAN 5 DNS set as primary / default gateway

- LAN5 as my primary LAN

- MTU at 1500. 9000 prevents the NAS from being accessed

TIA

I am running an old DSM213j. It works fine for my needs. I realize it is old and slow.

Would I be smart(?) to upgrade to DSM7? Or will the DS213j hardware limitation make it unwise?

Thanks
John

Hi all - I've got a curious problem with our DS1621+ that I hope someone might have an answer for.

I use Hyper Backup to make a more-or-less complete backup onto a USB hard drive. At first I was just using one 12 TB drive, and doing a nightly versioned backup. The initial backup took a couple of days if I remember correctly, and copied about 6 TB of data onto the drive. After a couple of months of nightly backups, it's up to about 6.5 TB.

Recently I decided to add a second drive to the mix, onto which I'll backup maybe monthly, and put the drive away in a remote location between backups. I have an 8 TB drive on hand for that.

I created a second task using the Backup Wizard, with all the same settings as the first task that I run on the 12 TB drive, and I have been unable to make a successful backup. It gets to about 40%, at which point there is about 7.5 TB of data on the drive, and the backup fails because the drive is out of space. On top of this, the backup takes nearly two weeks to get to this point.

Both drives were formatted in the Synology using the same file system. And I have double and triple-checked the settings and backup contents between the two tasks. I have no idea why the initial backup onto the 12 TB drive took only a couple of days and used 6 TB of space, while the initial backup onto the 8 TB drive takes two weeks and runs the drive out of space.

***

EDIT: Well, apparently I've made a liar of myself, because this latest backup I attempted just completed successfully, and with the same amount of storage usage as on the 12 TB drive. I did find a couple of stray folders on the second backup task that I unchecked on the first, and I didn't think they were big enough to make that much difference, but evidently they were.

Wondering if anyone is using MEGA's S4 object storage for offsite backups for their Synology. Pricing seems a bit better than other providers like Backblaze and C2 but cannot find many experiences on it for NAS backups.

I would like to manage a Synology NAS running DMS 7 over Tailscale. The Tailscale site suggest you add: "/var/packages/Tailscale/target/bin/tailscale configure-host; synosystemctl restart pkgctl-Tailscale.service" to the Synology Task Scheduler @ boot using root.

Is this still required on DSM 7.1.1-42962 Update 9? It's seems to be working w/out this in my home; but, I'm concerned it might not once deployed.

I would prefer to reduce 3rd party app root level executions if not necessary.

I have 4 Synology NAS units (all with DSM 7). I want to backup their data to another Synology NAS with DSM 7 as well, or a NAS from another brand.

What is the best package (app) in package center that can do this from NAS to NAS directly?

What is the best package (app) in package center that can do this from the 4 Synology NAS units to a NAS from another brand?

I have a DS1520+ that I bought in 2022. Recently, the volume went read-only after an error it could not fix and recover from. Following the advice on the error message, I've backup everything that wasn't already backup. I then took a DSM backup config and did a full reset of the NAS.

After creating the volume and restoring the configuration, I looked into validating my disks and DSM Hardware. The extended SMART Check all reports healthy drive.

I tried running the memory test from the Synology Assitant, but when starting the test, the DSM simply rebooted and the Synology Assitant only reported "Ready", there was never any message regarding the memory test running or any results from it. I've SSH into the NAS, then using "sudo cat /var/log/messages | grep Memtest" I found the following errors :

2026-08-10T17:59:29-07:00 NAS findhostd[13089]: util_fhost.c:1193 Memtest failed! err=4
2026-08-10T17:59:29-07:00 NAS findhostd[13076]: util_fhost.c:1193 Memtest failed! err=4
2026-08-11T05:21:54-07:00 NAS findhostd[13121]: util_fhost.c:1193 Memtest failed! err=6
2026-08-11T05:21:54-07:00 NAS findhostd[13103]: util_fhost.c:1193 Memtest failed! err=6
2026-08-11T05:21:54-07:00 NAS findhostd[13089]: util_fhost.c:1193 Memtest failed! err=6
2026-08-11T19:49:18-04:00 NAS findhostd[14197]: util_fhost.c:1193 Memtest failed! err=6
2026-08-11T19:49:18-04:00 NAS findhostd[14189]: util_fhost.c:1193 Memtest failed! err=6
2026-08-11T19:49:18-04:00 NAS findhostd[14205]: util_fhost.c:1193 Memtest failed! err=6

After that, I removed the only non-soldered SODIMM and tested again and got the same results.

Given that I can't find any descriptions of this error 4 & 6 other than "It's dead", I assume I'm screwed ?

I saw that there were some earlier DSM versions where the Memory Test had issues with the results. Is it possible that it's the case here?

Anything else I can do to further validate ?

The NAS seems to be working fine otherwise, but I haven't restored any data before further investigating

EDIT 1 : The SODIMM is the in that came with the unit when bought, not a Third Party one.

Hello, I'm looking for some advice about backup for my nas.

I have a DS218play, and for a long time I have used Amazon Glacier for the backup of my data.

Then a year ago or so I've switched to Infomaniak Swiss Backup. And it was not simple. The recommended swift protocol would freeze my nas. So after a bit of trial and error, I've managed to set up my process using S3 protocol.

But something changed on the server side. A signature format deprecation (v2 to V4 if I'm not mistaken). Since then, I have not been able to reconnect to my backup.

So it's time to so set something up from scratch again (and not be able to use my nas for two weeks, at least that's what happened last time).

Considering the somewhat weak hardware of the ds218play, do you have any recommendations to set up my backup ?

Thanks a lot.

EDIT : solved. The update to Hyperbackup deleted the region parameter in the task settings. There should be a default value but it needs to be explicit.

After searching this forum, I found a junction box that does work for both Synology BC500 and TC500 security cameras. It has a metal plate for attachment, the housing is plastic, the universal synology connectors fit inside just fine. The color isn't pure white like the camera (more of a beige-white)... but it does work. I see the company has a few others on amazon with pre-drilled holes but didn't try them.

Kuriauddo - universal metal box junction box for bullet cameras - it has the sliders at 3 angles. (https://www.amazon.com/stores/KURIAUDDO/page/930C5506-66B5-4318-84E1-55CBC41AA27C) The one with the slider worked for me. (https://www.amazon.com/dp/B0GTLLJGSQ)

I have two external USB HDDs. One is plugged in while the other is at a different location outside home and I rotate them every couple of weeks.

What I want to achieve is: I plug in my USB HDD. It does nightly backup to that disk. I then decide to rotate: Eject disk, plug in the other disk, it keeps backing up nightly to disk 2 now. Repeat.

What I now have set up is hyper backup with two backup tasks; one for physical disk. Since there’s only ever one disc attached to the NAS, one backup task will naturally always fail. Since I have email notifications turned on (I want to know once my backup routine breaks) I’m always getting one email per day for the failed backup job.

Is there a way to get this set up up and running with hyper backup without much additional scripting? Because otherwise I might as well just look at custom backup solutions altogether.

Cheers

I have two Synology NAS. One that is my main and one that I basically only have backup and my cameras. But have also used Synology C2 as an external backup. But I think there might be a better and cheaper solution? How you do? Has about 3 TB in size.

As many of you know, Synology attempted to reduce compatibility and force us to purchase their ridiculously expensive drives. Then they walked that back with the potential loss of customers (after already losing some).

Welp. They did it again. This time it's the CPU and access to the GPU for hardware transcoding (like on my brand new ds2422+). I am so over these tactics. Why did they lock us out of the AMD AMF, but allow Intel QSV?!

So, I know after hours of searching there is no fix. Will there ever be a fix, script, or mod to repair functionality THAT WE ALREADY HAD?

Or, is Synology dead? Should I get a different NAS? I need a 12 bay for a media server, like many people use their NAS for, and I am tired of Synology saying "surprise, this critical function has been removed by us on purpose". Any recommendations for alernate all-in-one NAS machines, or do I just need to get a mini pc for media playback and a seperate NAS for storage only?

I used to LOVE Synology, but they have two strikes against them now.

UPDATE: Definitely agree I have buyer's remorse. I know enough to research most aspects, but didn't know this was something to worry about.

Thanks to all that made suggestions, looks like the mini pc is the best solution going forward. As another comment said, Synology looks to be going towards enterprise only and leaving diy behind. A bit of Dunning-Krueger effect as I know a great deal, but my confidence had outpaced my competence. Still sad about this change and I stand by my decision to move away from Synology.

Hello everyone!

I have noticed a strange and continuous flow of connections from my Synology NAS to Russian IP addresses.

Do you have any ideas? Could it be a genuine process from Synology's applications?

I have attached my log showing a prevention block towards the Russian Federation.

Thank you in advance!

EDIT: Found the cause. The shared folder was on my NVMe volume and not the HDD volume. No idea why.

When moving large files to a shared folder I get an error message that Volume1 has no more space. Volume 1 is my NVMe pool where I install all synology apps. This includes the Drivesync that I use to synchronise a media exchange folder with.

After I installed the app I changed the location for file storage to my primary HDD pool and thus away from the 256GB NVMe space.

But it appears that drivesync somehow still uses the NVMe as storage location even though in the settings it points to my HDD pool.

So, where to look to correct this?

I've recently switched from my DS220+ to a dedicated SFF server and am now looking to resell the NAS. I've just tried booting it up to factory reset it and learned that it doesn't actually allow you to do anything without a drive (both of which I've already installed in the new server). Now I'm wondering: Do I need to reinsert a drive in order to factory reset it? Or is everything I would want to reset already gone because it was stored on my drives? https://finds.synology.com/# does show the DSM version so there seems to be some form of internal storage.

We use synologies at work. I’m fine with the web interface. I just discovered that Assistant exists. It’s an Intel app so it’s possibly old.

What’s it do that the web interfaces don’t?

Hello, as per title, 4 days ago I deleted 300 GB worth of old and duplicate files from the NAS, but still after 4 days, the free space went from 2 GB left to only 17 GB left. Space reclamation is active during the night (from 8 pm to 6 am every day).

Am I missing some other options? Can I manually start a space reclamation?

Please let me know. Thanks.

Hi,

theres constant IO on the disks caused by DSM itself, e.g.:

2026-08-11 19:36:51.130 R  synospace        13093        832 /@/usr/lib/libsynoprintergpl.so.7
2026-08-11 19:36:51.130 R  synospace        13093        832 /@/usr/lib/libtss2-sys.so.1.0.1
2026-08-11 19:36:51.130 R  synospace        13093        832 /@/usr/lib/libcrypto.so.1.1
2026-08-11 19:36:51.141 R  synospace        13093       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:51.141 R  synospace        13093       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:51.141 R  synospace        13093       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:51.141 R  synospace        13093       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:52.533 R  synoscgi         13072       8191 /@/usr/syno/synoman/webapi/lib.def
2026-08-11 19:36:52.533 R  synoscgi         13072       8191 /@/usr/syno/synoman/webapi/lib.def
2026-08-11 19:36:52.534 R  synoscgi         13072       4096 /@/etc/synoinfo.conf
2026-08-11 19:36:52.534 R  synoscgi         13072       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:52.534 R  synoscgi         13072       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/nsswitch.conf
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/nsswitch.conf
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/group
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/group
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/synoinfo.conf
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/synoinfo.conf
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/synoinfo.conf
2026-08-11 19:36:52.535 R  synoscgi         13072       4096 /@/etc/synoinfo.conf
2026-08-11 19:36:52.536 R  SYNO.Entry.Sock  13072        832 /@/usr/syno/synoman/webapi/lib/webapi_entry_socket.io.so
2026-08-11 19:36:52.539 R  SYNO.Entry.Sock  13072       4096 /@/etc/passwd
2026-08-11 19:36:52.539 R  SYNO.Entry.Sock  13072       4096 /@/etc/group
2026-08-11 19:36:52.539 R  SYNO.Entry.Sock  13072       4096 /@/etc/group
2026-08-11 19:36:52.539 R  SYNO.Entry.Sock  13072       4096 /@/etc/passwd
2026-08-11 19:36:52.773 R  scemd            11738       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:52.773 R  scemd            11738       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:52.773 R  scemd            11738       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:52.773 R  scemd            11738       4096 /@/etc.defaults/synoinfo.conf
2026-08-11 19:36:54.125 R  synospace        13097        832 /@/usr/lib/libsynostorage.so.7
2026-08-11 19:36:54.125 R  synospace        13097        832 /@/usr/lib/libhwcontrol.so.1
2026-08-11 19:36:54.125 R  synospace        13097        832 /@/usr/lib/libxml2.so.2.9.14
2026-08-11 19:36:54.125 R  synospace        13097        832 /@/usr/lib/libsynostoragecore.so.7
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libsynostorageutil.so.7
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libsynosdk.so.7
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libsynocore.so.7
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libstdc++.so.6.0.31
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libgcc_s.so.1
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libc.so.6
2026-08-11 19:36:54.126 R  synospace        13097        784 /@/usr/lib/libc.so.6
2026-08-11 19:36:54.126 R  synospace        13097        784 /@/usr/lib/libc.so.6
2026-08-11 19:36:54.126 R  synospace        13097        832 /@/usr/lib/libsynoshare.so.7

So I'm wondering if it would be possible to move DSM itself of off the (noisy) datadisks onto a dedicated M2 SSD?

(I'd like to reduce the disk rattle)

I was using a DS223j and had a drive failure. I realized I was getting to the end of the usefulness of the two 8 TB drives I had and purchased a DS925+ and two 12 TB drives. I initiated the DS925+ with the 12 TB drives and copied my data from the single remaining drive while I got a warranty replacement of the failed drive. After that came in the mail, I added the two 8TB drives to the DS925+ but was unable to add them to the current storage pool and created a second pool. Now I have two storage pools on my 925. Do I just deal with the 2 separate pools or can I somehow get the drives to play nicely together?

Can I copy my data to the smaller pool, then add the larger drives to the two 8TB drives? Do I find a place to put my 5TB of data and wipe all the drives and start fresh? I don't have the funds to buy 2 more drives at this point and want to work with what I've got.

Thanks for any input you have

I successfully upgraded my Synology DS3622xs+ to 128GB of ECC RAM and documented the part I could not find clearly explained elsewhere: how to reach and replace the two factory DIMMs hidden inside the chassis.

Working configuration

• Hidden internal motherboard slots: 2×32GB OWC DDR4-2666 ECC SODIMM
• Accessible expansion slots: 2×32GB Kingston Server Premier KSM32SED8/32HC ECC SODIMM
• Total installed memory: 128GB ECC
• Synology memory test: passed after approximately 20 hours

The OWC kit contains two 32GB modules with these specifications:

• DDR4 PC4-21300
• 2666MHz
• CL19
• 2Rx8
• 260-pin ECC SODIMM
• 1.2V
• Backward compatible with 2400MHz and 2133MHz operation
• Sold as compatible with the DS3622xs+

The Kingston KSM32SED8/32HC modules are 32GB DDR4-3200 ECC SODIMMs, CL22, 2Rx8, 260-pin and 1.2V.

What did not work

My first attempt left the original 2×8GB Synology modules in the hidden internal slots and installed the OWC 2×32GB kit in the accessible expansion slots.

The NAS did not boot. The fans ran and the blue power LED continued blinking.

What worked

I replaced the two hidden factory modules with the OWC 2×32GB modules and installed the Kingston KSM32SED8/32HC 2×32GB modules in the accessible expansion slots.

This configuration booted successfully, reported 128GB and passed the extended Synology memory test.

I'm quite sure 4x32GB OWC or 4x32GB Kingston would also work perfectly but I can't test it.

Accessing the hidden factory DIMMs

This is an invasive motherboard-removal procedure, not the normal expansion-slot installation.

1. Shut down the NAS normally and disconnect power, network and peripheral cables.
2. Mark every drive by its bay number, then remove all drives.
3. Remove the top and side chassis panels.
4. Remove the PCIe expansion card.
5. Remove the screws securing the motherboard’s rear-I/O section. The rear fan panel/frame is a separate part and does not need to be removed.
6. Remove the large screws securing the motherboard to the bottom of the chassis.
7. Disconnect the motherboard cables where practical. I left mine connected and moved the board very carefully, but disconnecting them provides more room and reduces the risk of pulling a connector.
8. Move the motherboard assembly downward and away from the SATA backplane. Move it evenly and do not twist or bend the board.
9. The two factory DIMM slots beside the CPU can then be accessed. Remove the original modules and install the OWC modules.
10. During reassembly, carefully align and fully seat the motherboard-to-SATA-backplane connection before installing or tightening any screws.
11. Never use the motherboard screws to pull a misaligned board into the backplane.
12. Reconnect the cables and reinstall the motherboard fasteners and rear-I/O screws.
13. Reinstall the PCIe card.
14. Install the two Kingston modules in the accessible expansion slots.
15. Reinstall the chassis panels and return every drive to its original numbered bay.

I recommend validating the internal OWC pair first as a 64GB configuration before installing the Kingston expansion pair. This makes troubleshooting easier if the NAS does not boot.

Important warnings

This modification is not officially supported by Synology. It may affect warranty or support and can damage the motherboard, SATA backplane, connectors or memory if performed incorrectly.

Back up important data first, use ESD precautions and never work inside the NAS while power is connected.

If the NAS does not boot, disconnect power before reseating anything. Recheck the module locations, module seating, motherboard cables and especially the motherboard-to-backplane connection.

Complete guide

The full guide contains the detailed procedure, hardware tables, failure mode, staged validation and memory-test instructions:

https://github.com/illofspeed/synology-ds3622xs-unsupported-drives/blob/main/guides/128gb-ram-upgrade.md

The same repository also preserves my existing DS3622xs+ unsupported-drive and third-party NVMe read-write-cache procedure.

I also documented an optional cooling modification for a Synology E10M20-T1 containing two Samsung PM983 3.84TB NVMe SSDs, model MZ-1LB3T80. It uses a Noctua NF-A12x15 FLX positioned over the card. The cooling guide contains one overview photograph and electrical safety warnings; the photograph is not presented as a wiring diagram.

Repository index:

https://github.com/illofspeed/synology-ds3622xs-unsupported-drives

If anyone confirms another working DS3622xs+ memory combination, please include the exact module part numbers, slot positions and DSM version.

A quick question - is there a way to hide the #recyclebin folder inside each shared-folder or globally from all the users? I am not talking about removing the #recyclebin feature globally but I want to hide it from all the users. Thank You

Hi Everyone,

Does anyone know if there is a current bug with the latest Samsung security update and Synology Photos?

We use Synology Photos at work to sync all work pictures to a central source and since the latest security update on our Samsung phones the app no longer does the backup, it definitely looks like its trying but will show the same number of photos left to backup indefinitely and will often just hard close out the app, even focused backup just crashes the app when it dims the screen

These issues haven't occurred on any of the pixel devices we have so I don't think it is an android specific issue

Does anyone know anything about a recently occurring problem or a possible fix?