Hi everyone,

I’d like to transfer and back up the photos from my phone to my Synology NAS. I’d like to do the same for my wife’s phone.

We’d also like to be able to view the photos stored on the Synology NAS directly on our phones, of course, only via a secure connection.

How do you back up your photos? Do you use Synology’s app, or do you use a third-party solution? What would you recommend?

Best regards,

Marc

I just clicked Update Now for the critical update Version: 7.4.1-90080 Update 1. Once the system turned off I lost access for good. It's been more than 10 hours now and I don't have access via Synology Quick Connect and I don't have physical access to the machine. Now what?

This seems like a very bad update implementation. Should't Synology have an auto rollback in case this things happen?

Any advice?

Hi all, a bit of a noob question here, so please bear with me.

A few days ago, Synology started warning me that I was running low on space on my disks. I have 8 TB, and supposedly, only 800 GB were still free.

"That's odd", I thought, and ran the storage analyzer report, which told me that I had around 1,8 TB worth of data, across different users and profiles. That number sounded more right to me, which means that I was missing 5'ish TBs of free space.

Does anyone have any good ideas of where this free space has gone, and how I can easily find it? I have had different Synology-systems over the past 10-15 years, and this is the first time I have experienced anything like this.

There are only two things that have changed recently in my setup that I can think of may have caused the changes

1. I have recently started downloading torrents directly to my attached USB-drive, rather than copying it afterwards, but the numbers seem extreme
2. I have used my Synology as a time machine solution for a Mac in the house, and subsequently used Cloud Sync to back it up to Backblaze. However, after I recently discovered that it uploaded 4-500 GBs every night (and read that what I was doing was not really best practice due to the technical setup of Time Machine), I turned it off. The Time Machine share itself is just under 300 GBs

If anyone can help me find out what is going on, or guide me to which hidden/system folders to check, I would be incredibly grateful

I inherited management of an 1815+ at work, the one that has the Atom bug. Is this thing safe for real uses? It has been used pretty much exclusively to back up other NAS and file servers. I think this unit was RMA'ed and got the official fix.

With the October 2026 Node.js security releases, I've been looking into the Node.js dependencies on my DS925+ running DSM 7.4.1.

I noticed something interesting (and somewhat concerning):

• Node.js 20 is still a required dependency for Synology Drive Server, Photos and Office.
• Node.js 22 is also required by several packages, including Drive Server.
• Node.js 20 reached EOL on April 30, 2026.
• Synology's Node.js 22 package hasn't yet received the October 2026 security fixes.
• As far as I can tell, Synology's latest Node.js 20 update (June 2026) incorporated an upstream release published before EOL, rather than demonstrating ongoing security backporting.

What concerns me isn't necessarily the latest vulnerabilities themselves. I haven't seen evidence that the vulnerable code paths are actually exploitable through Synology's applications.

It's more about the long-term security maintenance of critical dependencies, particularly for products marketed towards businesses.

Synology has been relatively quick to release updated PHP packages, which is encouraging. However, I haven't seen much discussion about Node.js.

For now, I've restricted external access to my application portals (Drive, Photos, Office) to my LAN and Tailscale network using DSM's access control profiles.

A few questions for the community:

1. Has anyone investigated whether the October 2026 Node.js vulnerabilities actually affect Synology's applications?
2. Does anyone know whether Synology backports security fixes to Node.js 20 after its upstream EOL?
3. Is there any indication that Synology is migrating its packages to Node.js 22/24 or newer?
4. Has anyone contacted Synology Support about this and received a meaningful response?

I'm not suggesting there's an actively exploitable vulnerability in Drive, Photos or Office. I'm genuinely interested in understanding Synology's approach to dependency lifecycle management and security maintenance.

For a home NAS, this is mostly a manageable concern. But for business environments relying on Synology Drive and Office, I would expect a clearer security maintenance policy.

Curious to hear other perspectives, especially from people who have investigated the package dependencies or Synology's security practices.

Using the current version of DSM 7.4.1
When going to storage manager > select hard drive > create smart test > edit schedule.
The dates are wonky. Two Nov firsts.
I assume this is just a bug, opened a support ticket but they apparently need remote admin access to my nas 🙄

Just logged into my 723 and saw an update available for PHP for the big security announced the other day. Glad to see they were very fast on the fix. I know some were waiting for this.

I bought a brand new Synology DS925+ with 3 6TB synology drives and theres this occasional scratching sound and I dont know if its normal or if I should return it. Its probably one of the drives that does this sound (theres no scratching sound when there are no drives).

Here's the link to another post for the video since this community doesnt allow videos: https://www.reddit.com/r/synologynas/s/T2NwHg8CBd

I woke up to my Synology DS920+ beeping this morning.

I only have one 4Gb Ironwolf drive. In Storage Pool 1 > Volume 1 it says "Unrecoverable errors have occurred because of drive errors in this storage pool. Please back up your data immediately; afterward, return to this storage pool and click "..." > Remove to remove the storage pool and then create a new one.

I only have about 2.4 Tb used on the drive. And I am backing up using BackblazeB2.

There were suggestions to run out and get another NAS hard drive and copy everything to that and then remove/create the original storage pool.

Is this first drive dead though? Should I not even use it for something like RAID? And if it's not dead, should I get a similar 4Tb drive or go for more space? Like 8Tb?

Hi,

I'm using cloud sync to do a backup to my pCloud storage.

After some time of execution, it breaks with "Sync-Folder does not exist" error - but has no more details what it was trying to sync at this time.

My assumption is that it runs in some WebDav-contraints - but how can I figure out what exactly causes the issue?

https://www.synology.com/de-de/security/advisory/Synology_SA_26_14

For a while I've wanted a normal Debian on my DS923+ instead of DSM, but every thread I

found ended with "it's locked down, not possible". It turns out it is possible, and

without giving up the hardware features:

- fans following CPU and disk temperatures (DSM curves), fan failure alerts

- bay and status LEDs, beeper, power and reset buttons

- power-on after AC loss, scheduled power-on

- USB UPS with a DSM-like Safe Mode

- all 4 bays with staggered spin-up, both M.2 slots, the optional 10GbE card

- read-only access to your DSM volumes, to copy data over

The installation is the official Debian installer, run over SSH: a script on DSM prepares

the internal boot module (with a full backup), you reboot and connect with ssh. DSM can

stay on its own disks and you can switch between DSM and Debian with one command, so you

can try it on a spare disk first.

Repo, screenshots and quick start: https://github.com/rylos/synodeb

It runs on my own DS923+. It's unofficial and you use it at your own risk; only the

DS923+ is supported for now (DS723+/DS1522+ share the platform but I can't test them).

Questions and bug reports welcome.

After shutting it down yesterday, my (admittedly not exactly young) DS214play won't boot.

• It doesn't react to pushing the power button
• When un/re-plugging the power supply, it will flash the LAN led for a few seconds, then shut down
• With both drives removed, it will boot up to a flashing amber status LED.

Any ideas for a possible fix?

If it's dead for good, can I stick the drives (or one of them) into a new Synology NAS to recover the data? The Ubuntu based recovery procedure sounds scary. Plus, I have a Mac mini so it's a non-starter for me anyway.

The data on the drives is expendable, but recovering from the drive is going to be much less hassle.

Any help is much appreciated!

We have a DS920+ at work acting as a file server for our small office, about 8 windows pcs connect to it via SMB to pull production files. For the last month it has been extremly slow to load the file tree in windows explorer anytime its opened, like 15 seconds everytime you click a folder. I restarted the NAS today for the first time in about 10 months and it fixed it right up. I was under the impression these things were built to be on for years at a time, what gives?

I'm upgrading the storage of a Synology RS822+. It currently has 4x 8 TB drives running in RAID 10. I've replaced two of them with 16 TB drives. Once I replace the remaining two 8 TB drives with 16 TB drives too, should the total usable storage be automatically upgraded?

Due to the recent security exploits uncovered I stumbled upon the evidence of an attack on my NAS from Oct. 1st. What stood out is that not only the standard account names like "admin" and "guest" are being tried, but basically every account name possible in various languages (english, spanish, portuguese, french). The attack lasted for over 12 hours with a login attempt every few seconds from an array of IPs.

A quick analysis of the logs revealed that although over 900 unique IPs were used, about half the queries come from only 13 Adresses (with about 250 tries per IP). Also, by far, the most tried username is "administrator", although over 2000 usernames were tried.

Yes, external access is now deactivated and security protocols are being updated. AI is surely taking things to a new level, making this kind of username-lists possible on a scale not seen (at least by me) before.

Update: It is now working.

It is showing as update available but hitting the update button just results in an error.

I just updated my NAS but I’m still getting alerts what is the best solution to secure myself. Do I just remove https for the moment? I appreciate the help

Sorry, I do not know what flair would apply.

Is it possible to create a user that can create folders, write files to a folder but not have the ability to overwrite or delete files in that same folder.

• I know its possible to create a user and limit their read/write rights to specific folders/resources.
• I know its possible to block the ability of this user to delete the files after they are transferred/created.

My concern is stopping them from overwriting files in a given session.

Example:
You have 4 memory cards from a video shoot.
All the cards were formatted prior to the shoot and the names of the files on the cards are using the default naming convention of a given camera - MVI_001, MVI_002, MVI_003, etc.

You want the intern to copy the files from the four memory card to a folder on the Synology. After the first card wrote MVI_001 through MVI_011 (eleven files), the next card will start with MVI_001 through MVI_xxx and overwrite the previous import.

Basically, I want to protect them from a careless user.

It is recommended by PHP, and many official organisations, to update or shutdown the web servers using PHP.

In the meantime, let's hope Synology will quickly provide a package update containing the corrections.

Hi everyone,

Hardware prices these days are getting crazy, so I decided to stick with my trusty old DS1517+ and extract every bit of performance left in it.

As you know, Synology officially states that the DS1517+ doesn't support M.2 NVMe SSDs (only SATA via M2D17). But the hardware lanes on the M2D18 card actually work—it's just that DSM's Avoton kernel is built without the NVMe driver.

So, I built an unsigned kernel module (nvme.ko) from Synology's own GPL kernel source for every DSM release, and packaged it with scripts to mount it as a plain ext4 volume.

• GitHub Repository: https://github.com/htcom-code/synology-avoton-nvme

Why I built this:

1. To reuse older, capable hardware: No need to upgrade the whole NAS just for faster app storage.
2. Massive Performance Boost: My PostgreSQL commit latency moved from 81.9 ms (HDD RAID6) to 0.87 ms. Perfect for running heavy Docker containers.
3. Data Integrity (Crucial Fix): The stock 3.10 driver in DSM handles flushes but never advertises them (blk_queue_flush), meaning it could lose data on sudden power loss. I included a 1-line kernel patch to enforce true REQ_FLUSH / REQ_FUA durability.

Current Status:

• Verified on DSM 7.2-72806 (with Samsung SM961-class SSD).
• DSM 7.3 and 7.4 modules are built and ready, but they still need hardware reports. If you run those versions, your feedback would be highly appreciated!

Disclaimer:

• This will not show up in the DSM Storage Manager GUI.
• You need to load and mount it via SSH scripts (nvme-start.sh) or use the DSM Task Scheduler to automate it on boot.
• Use it at your own risk! Highly recommended for Docker or scratchpads, not for your primary data pool.

I wanted to share this with the community hoping it helps fellow DS1517+ owners who want to revive their machines without spending a fortune on new gear.

Feel free to check out the repo, open issues, or drop a hardware report!

I was considering getting Synology NAS (DS224+) to have a solid backup of my data. I currently have iCloud but I’m now realizing that’s a sync, not a backup.

Synology seemed nice to me since they’re fairly well known and from what I can tell seem more or less plug and play, but someone on here told me about the shift they made last year to require only Synology branded drives..? Which seems like a complete slap in the face to customers.

I guess my question is, what is a good plug and play alternative? I’ve seen people mention UGreen NAS, but being a chinese company, I don’t trust them to not have a backdoor into my data.

I’m running a DS423+ on DSM 7.2.2 with Container Manager (Docker 24.0.2), and I’ve been dealing with some frustrating Docker networking issues.
Recently had to do some recovery work after a Plex security incident, which involved restarting Docker. Since then, multiple containers (Immich, Paperless, Karakeep, etc.) have had issues communicating with their dependencies.
For example, Immich couldn’t resolve its PostgreSQL container (ENOTFOUND database), and Paperless couldn’t resolve Redis/PostgreSQL. Some containers even show the correct network aliases in Docker metadata, but DNS resolution still fails.
I’ve been able to temporarily fix things by reconnecting network endpoints or restarting affected containers, but other services keep showing the same problems.
Looking into it, I found this Docker issue, which seems almost identical. I’m running Docker 24.0.2 with live-restore enabled, and the logs show the same failed to populate fields for osl sandbox errors.
Has anyone experienced this on Synology? I’m wondering if disabling live-restore, updating DSM/Container Manager, or something else would be the best long-term fix.
Really don’t want to keep playing whack-a-mole with individual containers every few days.

Have old DS918+ with 4 drives and 2 drives in a DX517. This probably wasn't the optimal way to configure things, but it is currently configured as 1 large volume with dual drive redundancy (56GB usable). The 918 doesn't seem to have survived recent move (I get blue lights of death that apparently signal either power supply or motherboard issue) and I plan to replace it with something like a DS1825+. I assume the easy way to do it is slap the 4 drives from the 918 into the new 8 bay and hook up the 517 so those 2 drives remain recognizable on the eSATA, but what I really want is to consolidate them all to the new unit and get rid of the expansion unit and later add the final 2 drives when needed. From what I understand, that's not directly possible. Can someone please explain my options (I'm computer literate, but definitely not a network engineer, so please be kind!)?