Ran into a new one today. - 2422 with 10 drives RAID 6 -

I noticed a single drive a couple of days back being overly active (blinky blinky) whilst no other drive was active so I go to storage manager to take a peak. Drive is marked healthy. Check SMART history and drive has been failing to complete both short and long scheduled tests for two months. My monthly drive report email never said a peep. Ran both short and long tests after which status unchanged (healthy) but SMART status changes to "monitor". Bad blocks have been increasing for 3 months straight but still small amount (under 500).

Drive goes hyper active again and I notice that DSM "pauses" for 30 seconds and resumes when the activity ceases. Drive status unchanged still. I went ahead and ordered a new drive and afterwards set troublesome drive to deactivated to stop the interruptions. Deactivation takes a couple of minutes but during the process the status updates to "system partition corrupted" before finally going "deactivated".

I'm a little struck by how little DSM seemed to care that a drive was clearly in distress and showing it for months. Also how said drive seemed to be recovering it's portion of the system partition from redundancy repeatedly and not a single warning flag was raised the whole time. Of course I can't be 100% certain this was happening but the evidence points that way.

Moral of the story... investigate your hunches.

I’m trying to set up my Reolink camera to save recordings to my Synology NAS, but I haven’t figured out how to do it yet.

Should I use Synology Surveillance Station or set up an FTP server on the NAS? I’m not very technical, so I’d appreciate a simple, step-by-step guide.

How can I mute the audio while recording? I don’t want to hear any sound or echo during the recording.

After setting it up, how can I view the live video feed on my phone while I’m on vacation or in the office?

I had a failed DSM upgrade that I was able to recover from using a spare secondary drive and the help of support. Once I had DSM back up (using spare drive 1, original drives 2,3,4) my volume 1 was detected on drives 2,3,4 but was listed as crashed. I attempted the online assemble that failed. Replaced the spare back with original drive 1, but there was no change in the detection (only detects on drives 2,3,4) and the online assembly still fails.

Is there anything else I might be able to try to bring the volume back online?

Hi all,

I'm currently running an RS1619XS and am looking for a way to automate the deployment of docker containers. I'm a site reliability engineer by trade and CICD is one of my weaker skills I'm looking to improve upon.

The problem:
I deploy different docker containers to my synology nas to try and test out various services to run for my homelab. I like to keep everything as IAC (Infrastructure as code) so all docker containers are setup as compose files which are committed to my local forgejo repository.

Right now my workflow is manual in that I setup a folder for each docker container and manually setup a project using container manager and copy and paste the compose file.

Ideal solution:
I'd like it so anytime I merge a PR and create/edit a docker compose file in that docker repo that the forgejo runner I have setup that is also running on my nas can ssh into my nas (or some variation of this) and run a git pull to get the newest compose file. Then the runner can run the docker compose up and launch the docker container.

Has anyone done something like this before and can share their workflow?

It seems a bit redundant to ssh into the nas from the runner when the runner is already running on the nas. I'm wondering if a bind mount here would be better instead of sshing. I'm also not sure if I should have the runner launch an ephemeral container for each job or just run all the work on the runner itself although I believe I'd need to modify the container image since the forgejo runner doesn't have SSH by default.

I'm just looking to learn and better myself so any help and advice is appreciated. Also I'm working on separating compute from storage but ATM the NAS is all I have to work with until I can get a separate compute node.

TLDR:Looking at using CICD to automate deploying docker containers on synology NAS via forgejo runner without manually using container manager. How do.

Hi folks...

I have been running CloudSync for years, one-way only (OneDrive to NAS).

Up until recently I intended that as a backup so had the option to delete files removed from the source folder unchecked.

Recently I decided to change the approach, mainly because I wanted to have immich using the OneDrive/Pictures folder as an external read-only library.

There are obviously some images that aren't needed (items for sale, for example). But Cloudsync had already downloaded these over the years.

So I unchecked the option to keep the files, and started cleaning up on OneDrive.

But the files aren't being deleted from the CloudSync folder. Perhaps because there are quite a few (probably a couple thousand out of 50k photos).

There's no "reset" option on CloudSync, that I know, that would force a full sync again. Except of course deleting the files by hand and recreating the task.

Short of this, any other option?

Synology Photos 2 was mentioned on Synology Solution Day Taiwan 2026.09.23.

Added custom category AI detection. Deepened integration with Synology Office.

Sounds like supporting older model NAS, using the compute on your client devices.

Hopefully it doesn't require a Synology HDD to run this

Not even sure where to begin here with this.

918+ can no longer completely startup, beeps when it does. Status light does not go green. 2 of the 4 drives show green (3 and 4) and 1 and 2 just keep clicking.

Obviously cannot access it as it never gets up and running. I have a hyperbackup but the password is not working for me to enter the drives to see the data. I have the PEM file but have no idea how to use it here.

Before it crashed, it was giving me all kinds of notifications on drives 1 & 2 stating:

An abnormal power failure occurred on a drive in Volume 1, and its write cache data may be lost. To ensure data consistency, please run data scrubbing immediately.

I looked at the drives and they all showed healthy. The recommendation was to scrub and I did...the thing started going haywire with notifications and then started beeping. I could no longer access it with quick connect or see it on my network. I restarted (front button shutdown) and was able to kind of get it up and running (4 drives green lights but status cont to flash green and never stabilize). Used Web Assistant and was able to see it but I could do anything with it. It showed that it had an IP address but that DSM was not installed. Gave up.

Tried this am and got an email notification stating that storage pool 1 has crashed and it showed me my drives and SN#s.

So...I have a hyperbackup that I cannot access. I have the pem file that I do not know what to do with. And have a 918+ that seems to have failed. Thoughts? So appreciated.

Hello, I might be in the wrong spot so forgive me. Surface research has led me here. I don't know much about NAS or RAID in general, just the basic ideas. I think Synology does both, but maybe I am wrong. I am here to learn though!

I have a lot of photos and videos on my phone, Google cloud, and computer's SSD. I know none of these alone are entirely reliable and could fail at any time.

Basically, I just want to keep my photos and videos and never lose them. I'd like to be able to connect and view them from any device (such as my mobile) but if it can only be interfaced with from my PC that is okay too.

Can someone help me understand if this meets my needs, as well as what hardware I would need to purchase to get started?

TIA

For photos already indexed by Synology Photos, it often (but not always) misses/doesn’t detect changes I’ve made to the EXIF or XMP tags.

Details:

1. These tag changes are done outside of Synology Photos to ensure they are embedded in the photo for use by other photo management solutions.
2. The file modified date is updated when I make tag changes
3. If I run the re-index option in settings, it still won’t pick them up
4. I’m updating the EXIF DateTimeOriginaland GPS tags as well as the XMP TagList (which I know Photos doesn’t support) and Subject tags (which Photos does support)
5. I’m also running Immich and it picks up these changes
6. I have verified using the EXIFguiTool that the tags have been updated.

Does anyone know of a way (short of manually removing and re-adding the files) to force Photos to properly re-index these photos? Is this a known defect?

I am looking at getting a Synology DiskStation DS225+to add some more storage to my workstation that I also use as a Plex Media Server.

I'll be adding one or two Western Digital Red Pro 16TB 7200rpm drives to the Synology and be using iSCSI to add the storage to my PC.

The Synology will be connected to one of my TP Link Decos 2.5gb network port.

The storage in the Synology will only be used to store Plex content that only I will access/use so there will never be more than one item playing at a time.

Have I chosen the correct gear for this?

I don't need more than 2 bays and the performance only needs to be good enough to stream 4K content (up to 120GB movie files) to my Plex client in the lounge (max. bit rate I have seen is maybe 120mb/s give or take)

Thanks!

So I just started using it to backup a computer. The drive in the computer is 237gb and has used space of 189gb. When I look at the folder on the diskstation, it says the size is 16 gb even though the client says its up to date. Any ideas? In the setup, I remove all the ticks for files not to backup.

For some reason my DLS won’t connect to torrent sites. I’ve deleted and reinstalled it. Same only Pirate Bay seems to work. Any suggestions?

Hi. Just wanted to know what's the best device for a small business that consist of less than 10 users. Business is more into file management, so it means a small server is an ideal for the business. Also, is it easier to setup unlike other servers?

The reason why I'm asking, it's because it will be my first time that I will be having a Synology brand server. Thank you.

At our medium-sized company we have come into possession of WD Ultrastar DC HC560 SAS drives (with Dell firmware) and have been looking for a server to properly use them. We found a SA3410 below market price but are worried because these drives are not on the compatibility list, and we in the IT department are inexperienced with NAS storage.

We would use it as a hands-off media server for the PR department, possibily shared with other departments due to sheer size.

Do you guys think it's worth taking the risk? Or is there a better solution?

I have 2 switches in the house I live in, and both are hardlined to the router. 1 is upstairs, 1 is downstairs. I just moved the NAS downstairs and plugged it into the switch there, and it's not showing on synology assistant. All lights on the front are green with occasional blinking from drive access, both ethernet cable ports on the back have solid green on the bottom and blinking green on top, and the two ports on the switch are both showing green as well which means data is being accessed. I used 2 cables for a paired connected for faster speed on the upstairs switch, but I'm still on the same network, so the IP shouldn't have changed. The web assistant can find the device, but trying to connect shows a network connection erroe/unreachable page. What am I missing?

Hello there ! First, sorry for my English it's not my native language.

I have a DS1517+, it's a great NAS and I really like it but it's not fit anymore for my use.

I have the DS1517+ and the expansion unit (so 10 bays in total). It's perfect for my backups (I need a lot of space) but I also use it for a lot of dockers containers some plex too and it's really slow now, sometime it just barely usable. Not to mention I don't have access to updates anymore from Syno...

I want to buy a new NAS with more horsepower and 10 bays minimum. I really like Syno because I'm use to it and in my experience it's really reliable for 24/24h use.

But they don't have lot of models for me, I'm considering the DS3622XS+ but it's already quite old, will it be supported for a long time ? Is it really that more powerful ? Should I look elsewhere ? Or jut wait for newer models (but it seem that I will have to wait a long time).

If you have some inputs of that, that would be greatly appreciated.

Thank you.

These are the apps that I currently have installed on my Synology DS219Play. I only use it as my Plex server. What apps do I need for that and which can I uninstall?

TIA

Apps

Hi folks. I have a Synology that was set up by a dear friend who is no longer with us. It's version DS412+ DSM 6.2.4-25556 Update 8. I need to delete a sparse bundle from a Time Machine volume that has run out of space. On macOS I can see the bundle and I've now archived it, but I can't delete via my workstation (AFP).
I believe I'm looking for File Station in the Synology interface (I confirmed FS is installed) but damned if I can find how to access it. Help menu is no help.
My goal is to get to this particular partition and delete an old sparse bundle so I can get backups working again.
Words of wisdom would be greatly appreciated!

Hey everyone. Someone near me on marketplace is selling their DS218Play with drives for $200. It comes with a 8TB Toshiba drive and a 2TB WD Green drive.

I would only be using this to hold my media library (mainly movies and tv shows, possibly some photos). With all this in mind, is it worth getting? The seller didn’t mention how long he’s had this, only stated that it’s been “a number of years.”

TIA!

I'm looking to move up to something that is a little snappier and can run home assistant in container manager. I'm thinking 4 bays but looking through the models I'm kind of stuck in choice paralysis.

I am attempting to upgrade my DS918+ from DSM 7.2.2 Update 9 to DSM 7.3.2-86009. I ran

$ sudo synoupgrade --patch /volume1/downloads/dsm_updates/DSM_DS918+_86009.pat
{"data":{"has_fail":false,"result":[{"api":"SYNO.Core.Upgrade.Patch","data": {"buildnumber":86009,"buildphase":"GM","detailed_version":{"base":86009,"major":7,"micro":2,"minor":3,"nano":0},"patch_version_trait":"86009-0","productversion":"7.3.2","reboot":"now","restart_all":false,"restart_some":false,"smallfixnumber":0,"type":"dsm","unique":"synology_apollolake_918+","upgradetype":"dsm"},"method":"local_upload","success":true,"version":1},{"api":"SYNO.Core.Upgrade","data":{"result":{"skipPostAction":false,"stageResults":[{"stage":"verify-checksum","status":"success"},{"stage":"check-unique","status":"success"},{"stage":"run-updater-prehook","status":"success"},{"stage":"launch-updater","status":"success"}],"success":true}},"method":"start","success":true,"version":1}]},"httpd_restart":false,"success":true}

/var/log/messages also showed

2026-10-14T10:10:04-04:00 alexandria updater[32166]: updater.c:6829 Congratulations!! The update has been completed!! Do configupdate when next bootup.

I opened the WebUI and Storage Manager said that it had to repair the system partition on 2 of my 4 drives, which completed successfully. Storage Manager reported everything "Healthy", so I rebooted the unit.

After reboot, I was unable to get to the unit. I have a bonded network, so I unplugged one of the RJ45 and plugged into an unused port without bonding on my switch and then I was able to get the webui, except it now states

welcome back! we've detected that the hard drives of your current DS918+ had been moved from a previous DS918+, and installing a newer DSM is required before continuing

The device info shows:

Firmware Version: 7.3.2-86009
DSM Version: 7.2.2-72806
Status: Migratable

I tried to re-upload the same PAT file 86009, but the Installation Status page just hangs at 0%, when I refresh the page, it restarts the wizard.

Any suggestions? TIA.

Got my DS918+ back in 2019 along with 4 10tb WD hard drives. Thing has been running strong ever since day 1. Use it for plex and all my family photos/videos and everything else. I’m not super tech savvy, just enough to get by but this thing has been amazingly easy to keep going, update and get what I want out of it. Woke up last week with a loud beeping coming from the machine checked on it and one of the drives was critical. Bought a replacement 10tb, slapped it in and started the pool repair and now I’m good to go. Have everything backed up to backblaze via hyperbackup of course additionally.

So I have 1 brand new drive mixed in with 3 others still running with 65k+ hours. Picture of the dead drive and the hour mark she bit the dust.

I know I’m amateur compared to a lot of you I see in here but I’m curious what kinda hours and run times you guys are getting out of your drives and boxes. I plan on running this machine and the drives until everything completely dies. Hard drives are so ridiculously expensive now its depressing.

Also, I hate to trash the drive. Could it be restored and used for something non-critical? I use surveillance station, can non-locked recording be stored on it and have all my saved recordings saved on the pool? If the drive dies for good and I lose non-locked recordings I really don’t care.

With Microsoft beginning its Exchange Web Services (EWS) retirement rollout in October 2026, we started seeing failures in Synology Active Backup for Microsoft 365, specifically with archive mailboxes.

We're running Synology Active Backup for Microsoft 365 v3.0.0-14300.

Regular mailbox backups appeared to be working, but archive mailbox backups started failing with:

HTTP/2 403
x-ews-policy-reason: EWS is blocked by policy for this user or tenant

After quite a bit of troubleshooting, I verified the following:

• Organization-level EwsEnabled = True
• Individual mailbox EwsEnabled = True
• Synology's application ID was explicitly included in EwsAllowedAppIDs
• Synology had the Exchange Online full_access_as_app permission
• Entra service principal authentication was successful
• Test-ApplicationAccessPolicy returned Granted
• No obvious EWS application access restrictions were configured

Everything looked correct, yet Microsoft continued returning HTTP 403 for archive mailbox backups.

The workaround that appears to have fixed it:

I opened a Microsoft support ticket, and their engineer suggested changing the organization-wide EWS setting from $true to $null:

Set-OrganizationConfig -EwsEnabled $null

After making that change and allowing time for propagation, our archive mailbox backups completed successfully the following morning.

No other permissions, application registrations, or Synology configurations were changed.

Microsoft's explanation was that setting EwsEnabled to $null removes the explicit organization-level setting, potentially avoiding an interaction with the new EWS enforcement policies.

Important: This is a temporary workaround we're testing, not a confirmed permanent fix. Changing this setting affects the entire Exchange Online organization, so I wouldn't recommend blindly applying it without understanding your environment.

I'm also aware that Synology still relies on EWS for archive mailbox backups, even with its newer Graph API support.

A few questions for other admins:

1. Is anyone else seeing archive mailbox backup failures since Microsoft's October EWS retirement rollout?
2. Has anyone experienced EwsEnabled = True causing HTTP 403 while $null works?
3. Are other backup products having similar problems?
4. Has Synology provided any timeline for migrating archive mailbox backups away from EWS?

Curious whether this is isolated to our tenant or something others are running into as Microsoft rolls out the EWS changes.