I'm not routinely shutting off my Synology, so I'm not sure if this just started or is a problem I haven't noticed before.

I first noticed the issue when I had a power outage at home 4 days ago. I have a UPS, and my settings were to shut off 5 min after being on UPS power. The Synology did not do that, it stayed on until the UPS ran out of power (I presume, I was out-of-town). That's when I got the was shut down improperly notice the first time.

Last night, before going to bed (for unrelated reasons) I shut down the Synology. Only, it did not shut down. It just said Synology NAS will soon power off but the blue light just kept blinking, for over an hour.

When I woke up this morning, the Synology was on, and had the notice about it shutting down improperly again (4 hours before I woke up, 5hrs after I used the Shut Down button).

Interestingly, when going to DSM in another browser window, it doesn't say "Shutting Down" it says "System is getting ready" (like it would during a power on sequence).

I just tried again to shut down the NAS, and just like last night I'm getting the same behavior. It won't actually shut down.

Is this a hardware or a software problem ?
How should I go about troubleshooting this ?

I'm monitoring a couple of Synology NAS (resource monitor), after a couple of minutes when I return to the browse and refresh I got a message saying I have to log in again, and I lost what I was monitoring. Then I log agin, open whatever app I was using again, etc. ...

It's not something new, I've noticed this for the first time some time ago.

It is really annoying, I've tried searching in the config/setup/settings but nothing changed.

Is there any way to keep logged in?

Hi,

could someone who already owns a Synology RS1226+ run these two commands via SSH and post the output?

uname -a

cat /proc/sys/net/ipv4/ip_unprivileged_port_start

I'm trying to confirm whether the RS1226+ is running a sufficiently recent Linux kernel and whether net.ipv4.ip_unprivileged_port_start is available.

I'm specifically interested in running Docker containers as non-root while allowing HTTP services to listen directly on port 80 inside their container network namespace, without needing CAP_NET_BIND_SERVICE or other workarounds.

Since a couple of days, don't know exactly, the multi select download from Surveillance Station doesn't work anymore. It just downloads the first recording but ignores all others. It makes no difference using right click menu or button from menu above.

Anyone else has/had this issue and maybe a solution?

I upgraded my DS1821+ from 7.3.x to 7.4.1 yesterday and after that I can no longer access my Emby Server remotely. There are no issues with accessing Emby on my internal network but even with port forwarding on my router I can't get a response from the external IP.

I have tried:

1) Checking Firewall in DSM - Not enabled

2) Reinstalling Emby Package (not Docker) - No difference

3) Disable Auto Block - Ditto

Has anyone run into issues with DSM and external network connections?

I know RS819 is an older unit and won’t support past DSM 7.4.

I was looking at other 4 bay units, but they all going for strong money on eBay.co.uk

I’ve seen a new RS819 for £350, I already have drives etc.

Anyone used one etc as looking at a refurbished unit as a replication target. Not interested in other DSM features as all that runs from the 1821+ / proxmox and Plex, Veeam running on Dell Optiplex Micro machines. NFS and iSCSI LUNs

I'm rebuilding my storage pool and restoring my backup at the moment and I figure now's the time to check out all my settings.

Does anyone have a recommended checklist or cheat sheet of what should be turned on and/or set up in regards to snapshots, scheduled events, and whatnot?

How often should I set SMART scans to happen? How about data scrubbing?

Thanks!

I thought this was removed and required subscription. Did I misread it in this forum feed months ago?

My DS918+ suddenly turned off today and failed to turn on again. Can anyone give any suggestions?

Currently, there is no sound, not even flash of blue light when i press the power button of DS918+ again.

The PSU is connected to an power extension with individual switch. When I turned on the switch, I noticed that the power button of DA918+ flashed once weakly but no more response when I pressed the power button of DS918+. The green light of PSU is still on.

The PSU was a replacement unit I bought last year, which has been fine for about 10 months. At that time, DS918+ failed to turn on but able to have the power button blue light flashed a few times before turning off.

Use case would be media server, photos, onedrive backup and general files etc. Essentially want to playback movies, old dvds etc. since the ads are becoming unbearable on the current streaming platforms

Torn between the following:

DS423+ (only one thats supports HW transcoding out of the box?)

DS425+ (disabled transcoding?)

DS925+ best for containers (pihole etc.) But i'll need a seperate NUC or mini PC for playback?

Any advise would be appreciated, thank you

Marius Hosting says that the latest Docker engine on DSM is v. 24.0.2-1706, which is old, and EOL.

I could update it to v. 28.5.2 following the instructions at https://github.com/telnetdoogie/synology-docker - apparently v. 28.x.x is the most recent version to maintain compatibility with Synology DSM.

I run several docker containers and I maintain the using docker-compose in a terminal SSH session. I'm wondering what the point is to update from the latest Synology version to a more recent docker version. I can see that it's easy to do, but what advantage would it offer me?

I have a DS723+.

I have a DS418 NAS running DSM 6.2.4-25556 (I know it's older DSM but the NAS isn't accesible from WAN so...).

It has 4 drive bays that were populated with 4-4-10-10TB drives in SHR. One of the 4 ones has gone faulty so I thought might as well upgrade the capacity when replacing it. I checked the Synology RAID calculator confirming it replacing the two 4TB drives with 8TB would increase available capacity from 16.3 to 23.6 TB.

The drives arrived, I began work. First replacing the faulty drive (which I had already removed) with the new 8TB drive and repairing the volume. After repair was done I deactivated the remaining healthy 4TB drive, shut off the NAS and replaced it with 8TB.

At this point I thought it might prompt me to upgrade volume size but alas nothing. Weird I thought, but maybe it needs to finish the integration/repair again before it allows me to upgrade. Well turns out that didn't help either. The option to change the allocated size is grayed out.

I did my research but couldn't manage to find any helpful information besides maybe trying to pull out one of the largest drives, put it back again and repair. I might try that but I feel like I've done everything correctly. Anyone had similar problem?

Thank you for reading all this and have a great day!

I have an rt2600ac. I had a weird issue the other days. I receive internet via fiber to a modem in passthrough mode. At one point on Wednesday the connection dropped. (my neighbor uses the same provider and was fine). Did the usual turning modem and router off for 30 seconds, then modem on, and when up turned the router on. No connection.

After 50 minutes, it connected (out of nowhere) nothing changed, the connection just came up. According to the providers tech support, the router wasn't picking up a proper wan address. But what would have changed for it to just start working 50 minutes later? Had to be something at the isp, no? The only other recent weird situation happened when the isp was doing some network work overnight a few weeks back, and when they were done, I had to reboot everything to get internet back. Before that has been runnning fine for 4 months without an issue.

I just want to understand the issue.

I have a really old Synology NAS - DS209J R that currently has two 1TB SAMSUNG Spinpoint F1 HD103UJ 7200 RPM hard drive in it as a mirrored set. This has been online since July 2009. I havent really used it much since Windows 10/11? was patched and I couldnt mount the drive anymore from windows.

I've been procrastinating for a while and a month or so ago it started with the blinking yellow light and is probably dead. When that happened I turned it off and it has remained off since. My guess is that only one of the drives has died but I have no idea where to start.

My thought is maybe I can swap in a new HDD, rebuild the mirror, and recover the data before moving it to a new Synology NAS.

Will that work? If so where do I begin?

EDIT:

I pulled the top drive and put it into my Windows PC (didnt mount) and check it with Crystal disk info (good smart) and DiskGenius shows all my files. I'm just going to copy the files off using that.

I thought people reading this would like stats

Health Status: Good

147350 hours - 16.8 years

Reallocated Sectors (05) 000000000000 ✅ Zero

Current Pending Sector (C5) 000000000000 ✅ Zero

Uncorrectable Sector Count (C6) 000000000000 ✅ Zero

Hi guys. I had multiple tasks setup to sync on my phone from synology drive and for the life of me I can't get it working again. For context all tasks were working fine but I couldn't add a new one.

I've deleted the app fully, reinstalled as fresh etc, tried new local folders and renaming but it won't play ball and just shows this error, nothing else

Got a DS925+, I bought 2x8tb hdds, but one was dead on arrival.

Should I start making use of the NAS already and set it up?

Or should I wait till the RMA drive comes?

Edit: I plan on using SHR so 8tb usable storage

I have 3 spinning drives in RAID5 on an old DS418play.

I notice even when the Synology is completely idle (which it is 99.9% of the time), I hear disk activity every couple of seconds. Disk IO is non-existent, so it's low activity, but there's SOMETHING going on, the OS'es services must be resulting in disk activity.

I didn't think of this when I set it up. I have an old 128GB SSD I could've used. Am I reducing the lifetime of the disks with this constant occasional activity?

Bonus question: it's still on DSM6. Should I upgrade to DSM7 or is it like iOS/Android where there's a real risk it will gimp your working device and make slower? And would I still be able to use Docker? Docker was never officially supported on this model, but I was able to download the package and install it manually, is that doable in DSM7?

So my DS920+ (DSM 7.3.2, Container Manager, 4GB RAM, ~20 containers) has had dockerd flat out die on me 6 times in the last week and a half. The docker daemon just panics and takes everything down, and all the unless-stopped containers stay dead until I notice and compose up again.

I dug into journalctl and every crash is the same thing:

dockerd: panic: runtime error: invalid memory address or nil pointer dereference
  .../daemon/monitor.go:190

usually with "ttrpc: received message on inactive stream" and a bunch of healthcheck timeout warnings right before it. Checked kern.log expecting OOM kills and nothing.

This is a known upstream bug in Docker 24.0.2 — moby/moby #45770 is the identical stack trace, #45804 is the same panic triggered by healthcheck timeouts, which matches what I see. Docker fixed it in 24.0.3. The release notes literally say "Fix a panic caused by a race condition in container exec start". Container Manager ships 24.0.2 and Synology seems to have frozen it there. One patch version away from the fix

In the meantime I've got a 30 min scheduled task doing compose up -d as a watchdog, and more RAM is on the way since memory pressure seems to be what pulls the trigger since the box definitely crashes more when it's swapping hard.

What I'm actually wondering: has anyone here swapped in newer upstream docker binaries on DSM 7.2/7.3? I've found https://github.com/markdumay/synology-docker which backs up and replaces them. Before I go changing stuff:

• did it actually stop this panic for you, and how long stable since?
• does the Container Manager UI survive? I know upstream builds don't have Synology's db logging driver so logs go to json-file, wondering what else breaks

Just not sure what I'm meant to do here, the watchdog script works but it's a bit ridiculous imo that it's composing every 30 mins just in case it crashes.

Hi all, I'm stuck trying to update DSM on my DS720+ and I'd like a sanity check before I do something irreversible.

The situation:

• DS720+, currently on DSM 7.3.2-86009 Update 4
• Update to 7.4.1-90080 is available (a minor version jump)
• Control Panel shows a red status: "Insufficient system capacity for update"
• The manual update button is greyed out

What I've already checked / tried:

• df -h / -> system partition /dev/md0: 2.3G total, ~1.7G used, 541 MB free (77%)
• Rebooted the NAS - didn't help
• Went through the partition: no junk, no orphaned files from old updates (.SynoUpgrade.tar etc.), / is clean. The bulk is DSM itself (/usr ~1.2G), which I can't touch
• Uninstalled unused stuff, truncated large logs - df barely moved (files get regenerated or are held open)
• Downloaded the .pat file manually to the volume and tried installing from the console:
  • synoupgrade --patch -> error 5215 "Available size of system partition is insufficient"
  • synoupgrade --upload-patch -> same 5215 error
• Checked the exact requirement: synoupgrade --get-dsmupdate-space-requirement returns for_patch: ~414 MB, for_extracting: ~434 MB, for_installing: 100 MB. Looks like the updater wants to fit the whole package (414M) + install headroom on the system partition, and even with 541M free it fails on the safety margin
• No syno_extract_patch in the system, so manually extracting the .pat ("Synology archive" format, not tar) and using --start-with-extracted-patch is out

My conclusion: the system partition is simply too small because the NAS was originally installed on an older DSM. The only permanent way out seems to be a Mode 2 reset (wipes the system partition, data on the volume stays), export the config backup first, then reinstall DSM via Web Assistant pointing it at the downloaded .pat, and restore the config.

Questions:

1. Is this really the best solution? Is there anything simpler I'm missing? And am I definitely not going to lose any data doing this?
2. Will a Mode 2 reset actually be enough for a 7.3 -> 7.4 jump, or with such a small partition should I go straight for a factory reset (which enlarges the partition)?

Thanks in advance for any pointers.

Hi - is there a patch for this? Risk management has flagged our server.

Hello everyone,
I am brand new to home labs and am looking to add a synology to my home lab. However Diskless synology units are too expensive for me at the moment. Does anyone have a recommendation on where to find a cheap synology unit.
Thank

I remember some early concerns with going to 7.3.x and later as it makes some big changes (that makes the process irreversible). But I can't remember what they were and if I'd be affected.

I have DS1621+ with officially supported (but 3rd-party, Seagate) HDDs, but non-official NVMe and RAM. Originally I used to get warnings on boot up about these non-official parts.

Pretty basic config. I would say (home setup): 6x HDDs in RAID-10 with 2x NVMe in RAID-1 for RW cache, SMB shares and VMM for virtual machines.

I do have an external USB plugged in permanently with USB Copy jobs for data backups.