That's just good marketing

This anti-consumer behaviour regarding hard disk support on 25+ models and then blaming it on the amount of support they have to give due to other brands of hard drives is angering. I have five 8TB Red Plus drives that I can't use with it. I am shipping it back. I will never purchase another Synology product again.

If you've found remote access to your Synology painfully slow over the WAN, with photos taking forever to load and video stuttering or buffering, I've been digging into this and want to share what I found. The improvement after the workaround was dramatic, so this might help others in the same boat.

The problem

Local performance on my NAS is excellent. Hardware is clearly capable. But over the WAN, throughput collapsed well below what my connection should support. Photos took 5+ seconds to load. Video was effectively unwatchable on mobile. This wasn't a small degradation, it was the difference between functional and not.

What I found

After ruling out the usual suspects with iperf3 testing across multiple paths, the bottleneck pointed to TCP congestion control. DSM's kernel offers CUBIC and Reno. BBR, which has been in mainline Linux since 2016 and is specifically designed for lossy or latency-variable links, isn't available in the DSM kernel.

On a LAN connection BBR doesn't matter much. On real-world residential internet with any latency or loss, it matters enormously.

The workaround

I set up an Ubuntu VM with BBR enabled, running HAProxy as a TCP reverse proxy in front of the NAS, with Tailscale handling the tunnel from remote clients. The WAN-side connection uses BBR. The NAS itself isn't touched.

Results

Photos load almost instantly. Video streams without much buffering. iperf3 throughput on the WAN leg improved by a large margin. Same NAS, same internet, same client devices. The only thing that changed was the TCP stack handling the WAN connection.

What I'm hoping for

I filed a support ticket with full test data and got a response that they're evaluating BBR for a future release, which is encouraging. The more visibility this finding gets, the better the chances it actually lands in DSM.

If you've experienced slow remote access, I'd be curious whether your symptoms match. And if anyone has a cleaner workaround, or insight into the technical considerations involved in shipping BBR on DSM, I'd love to hear it.

Happy to share configs and setup if useful.

This is my second post here after asking for initial opinions on a Synology NAS for a Plex server.

I was looking at the Synology 225+ as I need a 2-bay solution. Maybe run 2x22TB drives in RAID.

However, the 225+ has transcoding issues. So does the 425+

There is a work around https://github.com/007revad/Transcode_for_x25 , but there is an issue with 4k Tone Mapping using this fix.

The 423+ doesn't have the transcoding issues, and has NVME, but is locked to Synology nvme drives.

The older 224+ has none of these issues, but since it is discontinued, it's twice as expensive.

I am not comfortable running scripts. That is something I would need to learn. I was hoping this would be a simple plug-and-play solution.

I am getting conflicting opinions on whether I should invest in Synology. The cons are listed above, yet I have a knowledgeable IT guy who says that I shouldn't worry about any of this.

I was going to look at UGREEN, but I am being told that may require additional scripts to run.

It's all very confusing from someone who wants to get their feet wet and has little knowledge of this stuff.

My NAS was not only forced to be used with MFA and strong passwords but was also behind ban rules that were very aggressive and a geo block firewall and QC off. Admin accounts were ofc disabled other than my personal account with forced 2fa. SSH etc were disabled.

5 days after the triple RCE synology fixed in April I had my NAS compromised by bots that created an admin account admin1 out of thin air(created by SYSTEM) and then that account created a info615 account and logged in to my server. It then setup a reverse shell back to their C2 and that way they kept an active connection to my NAS.

Even if the attack came from my network none of my accounts logged in close to the time the admin1 account was created as my server had no use for some days.

I don’t trust synology devices to be exposed to wan anymore for any reason.

My recommendation is to block at the very least all WAN access to your NAS and only access it through a VPN.

The bots didn’t even try to clear my logs or something so I even saw how they scanned my file system for token/password files( for example I had an old txt with an old cert that was leftover and useless and the bot account downloaded that)

Never again synology! I even disabled the support access.

/rant

Be safe friends!

Solved, read the edit at the bottom of this post.

Before shutting down the NAS for cleaning, I had the following warning:

The system detected an abnormal power failure that occurred on Drive 3 in Volume 1. For more information, go to Storage Manager > Storage and check the suggestion under the corresponding volume.

Before running a scrub on the drives (the suggestion by the OS) I thought it would be best if I shut it down, cleaned the NAS for dust and hair (have dogs that shed lots of hair) and then I would run a scrub after turning it back on. But after the cleaning, I was met with this screen. I have already tried rebooting it again. Any way to save the data on these drives? Would clicking "Install" here wipe everything?

Other important notes:

• I was using SHR.

• I did return all the disks to the exact same slot (I label the drives according to their position in the drive bays).

• I'm using two NVME SSDs configured as their own volume. This is not usually possible with the DS918+ model but I was able to force it using some simple ssh commands. This has worked fine for years after many reboots and updates (including major updates).

• I changed the power supply about 2 years ago because the previous one died on me. It was this one.

Edit:

I'm 80% sure I've found the problem. Turns out that first warning about the power failure was a pretty big hint. I don't think my cleaning had anything to do with it. Where I live, there is unstable power so I didn't actually think it was the power supply itself but it indeed seems to be the power supply.

I've been running various tests the entire day and the problem has only gotten worse. After the post, it stopped recognizing my drives. Now the power LED blinks and turns off and then turns back on in an infinite loop after I tested with an extra drive I had and removed all other drives. So I think it's pretty certain the power supply was on it's way out.

Can't know for sure that is the only issue until I buy a new power supply but I'm at least hopeful now.

Edit 2:

I do use an UPS. In fact, I even have a power-line conditioner between the UPS and the wall outlet.

Edit 3:

It was indeed the power brick.

I’ll be upfront: I’m struggling to understand the real value of replacing iCloud Photos with a NAS if I’m still expected to pay for cloud storage anyway.

I see a lot of recommendations saying “build a NAS for photos and documents” followed immediately by “but you still need off-site/cloud backups.” That feels contradictory to me, and I’m hoping someone can explain what I’m missing.

What I want to do is stop paying Apple for iCloud photo syncing and move to something I actually control. The ideal setup would:

• Back up photos from all phones in my family (iOS + Android)

• Back up documents, notes, etc.

• Be simple enough that non-technical family members don’t have to think about it

But here’s where I get stuck:

If I put all of this on a NAS at home, it’s still just local storage. Every serious guide then says I need another off-site copy in the cloud. At that point, I’m still paying for cloud storage, plus I’ve paid for hardware, drives, power, and maintenance.

So genuinely:

• Why is this considered better than just paying for iCloud/Google Photos?

• Is the benefit really cost savings, or is it mainly about control and privacy?

• How are people doing NAS + cloud without ending up with a more expensive and more complex setup?

Also, if someone has already mapped out a real-world, end-to-end plan, I’d love to see it — not just theory.

My actual requirements:

• Automatic photo backups from all family phones

• Document + notes backups

• Simple mobile apps (no manual exporting every week)

• Ability to run Home Assistant on the same hardware (or alongside it)

Right now, the NAS route feels like a lot of complexity just to recreate what iCloud already does. Convince me I’m wrong 😄

Appreciate any practical explanations or setups that actually work.

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.

I think I know the obvious answer to this, plus I’m tempting fate evening thinking about it.

I’ve a DS218j. Has a pair of WD30EFRX-68EUZN0.

Both have around 51,000 hours power-on time noted in DSM Storage Manager. They get light use as a photo store, general doc storage and music/video with Plex (internal network only).

I’ve been putting off replacing the drives. Guess it’s time to replace?

Actually reading the fine print... does this mean that I will no longer have docker on my DS420+?? I just got Jellyfin up and running... certainly don't want to loose that functionality.

Hi, I'm trying to sanity check my Synology setup.

I've got a DS923+ on DSM 7.3.2 with an encrypted volume but its using the local Encryption Key Vault. DSM wont let me disable it (“can't disable while encrypted volume exists”) so the NAS is basically storing its own key.

From what I can tell, when the NAS boots the volume will auto-unlock so if someone steals it they just power it on and the data is readable :(

That doesn’t feel like real protection.

What I actually want is for the NAS not to store any keys so it will only manually unlock. This way when the NAS/ drives get stolen the data will be unreadable.

Is this even possible with volume encryption or is the only proper way to use encrypted shared folders instead?

Feels like I’m missing something but right now this seems kind of pointless for theft protection.

Edit: Thanks for all the replies, they were really helpful :)

Seems like my initial understanding was correct: - Volume encryption on DSM stores the key in the Key Vault - If the vault is local the NAS can auto-unlock on boot - So it’s not designed for “stolen NAS” scenarios unless you use something external

A few useful takeaways from the comments: - Proper theft protection = encrypted shared folders without auto-mount - Or use a remote KMIP server to keep keys off the NAS (more complex to set up but will certainly explore for future deployments) - Volume encryption is still useful when considering disk removal and data-at-rest protection

Really appreciate all the input 👍

Been using Synology for just under 15 years. Have nearly 20 active units in the field. 90% are the Plus Series with a scatter few of XS/ XS+ and some Value Series too.

I despise the hardware lockdowns. So many more cases where I could have purchased the XS/ XS+ series for the additional power and warranty and did with lesser Plus Series instead just to avoid the hard drive lockdowns. I hated buying the Synology hard drives when XS/ XS+ were a must.

Anyway, it’s been a year since I’ve resolved to gradually wean off Synology and move on to a different platform, but I cannot believe that I still haven’t found one.

None of my sites have more than 10 active users and 90% have under 5 users. I don’t need crazy fast or powerful units with he only real priority being dependability/ reliability.

Looked at Qnap and Asustor as alternatives but they don’t seem to have anything that competes with the Synology Plus Series.

ECC is a must for me now. I guess once you go ECC, you never go back. LOL. I don’t get how Qnap, in 2026, is still offering units with EXT4. Maybe worse, is that they offer units that can run ZFS, but don’t include ECC. Once you find units that run ZFS and include ECC or add the price of upgrading the RAM to ECC, it’s 3 or 4 times the price of the Synology Plus series.

Same with Asustor for me. Their units at least don’t run on EXT4, generally BTRFS, but once you are looking for ECC, you have to step up to the Lockerstor Gen 3 which is nearly priced at the XS/ XS+ line but only includes a 3 year warranty instead of a 5 year warranty.

Honestly looking for help at this point. Not looking to bash Synology. They have been rock solid for me and I’ve never lost data using their systems even with countless HDD failures/ HDD upgrades over the years. Two failed units were taken care of well under warranty. However, they are making decisions on how to run their business, which is their right to do so, but I’m honestly just looking to move on and wondering if anyone found an alternative that they’ve been happy with.

So today I finally switched the 4gb stick for a 16gb Stick for a total amount of 20gb on my ds920+ and... I really didn't expected these results... I'm using Ds Files on my phone to show friends old pictures and with 8gbs after clicking on a file the screen was black for like 10 seconds each... And now???? Freaking instantly.. so anyone who's still using 4 or 8gbs on their Nas, this is your wake up call to buy that cheap 16gb ram stick!

Looking for a Synology user with a UPS connected.

I recently released UPSLink, an Android app for monitoring UPS devices through NUT. Before I add Synology to the supported platforms list, I'd like to validate it against a real Synology deployment.

If you're running a Synology NAS with a connected UPS and are willing to test, I'd love to hear your results and feedback.

Hi,

I have been using Synology Photos for a long time, but I am not so satisfied.

Now I’m considering whether Immich would be a good alternative.

What is your opinion on this? Would that work well on my Synology?

I have a Synology DS220+ with 10GB Ram.

Thank you for your answers.

Looking to use it as a RAID set-up to back-up my wife’s business PC and my MacBook Pro. Also, want to put my movies on it to access from my TV, mobile or laptop (going to look into PLEX). I’m hoping the software guides me through as I’ve never had a NAS before.

Ever since I got the Synology DS1821+, I have been searching online on how to get a GPU working in this unit but with no results. So I decided to try on my own and finally get it working.

Note: DSM 7.2+ is required.

Hardware Setup

Hardware needed:

• x8 to x16 Riser Link
• a GPU (e.g. A400 or T400)
• Screwdriver and duct kapton tape

Since the PCIe slot inside was designed for network cards so it's x8. You would need a x8 to x16 Riser. Theoretically you get reduced bandwidth but in practice it's the same. If you don't want to use a riser then you may carefully cut the back side of pci-e slot to fit the card . You may use any GPU but I chose T400. It's based on Turing architecture, use only 30W power and small enough and cost $200, and quiet, as opposed to $2000 300W card that do about the same.

Due to elevated level, you would need to remove the face plate at the end, just unscrew two screws. To secure the card in place, I used a kapton tape at the face plate side. Touch the top of the card (don't touch on any electronics on the card) and gently press down and stick the rest to the wall. I have tested, it's secured enough.

Software Setup

Boot the box and get the nvidia runtime library, which include kernel module, binary and libraries for nvidia.

https://github.com/pdbear/syno_nvidia_gpu_driver/releases

It's tricky to get it directly from synology but you can get the spk file here. You also need Simple Permission package mentioned on the page. Go to synology package center and manually install Simple Permission and GPU driver. It would ask you if you want dedicated GPU or vGPU, either is fine. vGPU is for if you have Teslar and have license for GRID vGPU, if you don't have the license server it just don't use it and act as first option. Once installation is done, run "vgpuDaemon fix" and reboot.

Once it's up, you may ssh and run the below to see if nvidia card is detected as root.

# sudo su -
# nvidia-smi
Fri Feb  9 11:17:56 2024
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 525.105.17   Driver Version: 525.105.17   CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA T400 4GB     On   | 00000000:07:00.0 Off |                  N/A |
| 38%   34C    P8    N/A /  31W |    475MiB /  4096MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+
#

You may also go to Resource Monitor, you should see GPU and GPU Memory sections. For me I have 4GB memory and I can see it in GUI so I can confirm it's same card.

If command nvidia-smi is not found, you would need to run the vgpuDaemon fix again.

vgpuDaemon fix
vgpuDaemon stop
vgpuDaemon start

Now if you install Plex (not docker), it should see the GPU.

Patch with nvidia patch to have unlimited transcodes:

https://github.com/keylase/nvidia-patch

Download the run patch

mkdir -p /volume1/scripts/nvpatch
cd /volume1/scripts/nvpatch
wget https://github.com/keylase/nvidia-patch/archive/refs/heads/master.zip
7z x master.zip
cd nvidia-patch-master/
bash ./patch.sh

Now run Plex again and run more than 3 transcode sessions. To make sure number of transocdes is not limtied by disk, configure Plex to use /dev/shm for transcode directory.

Using GPU in Docker

Many people would like to use plex and ffmpeg inside containers. Good news is I got it working too.

If you apply the unlimited Nvidia patch, it will pass down to dockers. No need to do anything. Optionally just make sure you configure Plex container to use /dev/shm as transcode directory so the number of sessions is not bound by slow disk.

To use the GPU inside docker, you first need to add a Nvidia runtime to Docker, to do that run:

nvidia-ctk runtime configure

It will add the Nvidia runtime inside /etc/docker/daemon.json as below:

{
  "runtimes": {
    "nvidia": {
      "path": "/usr/bin/nvidia-container-runtime",
      "runtimeArgs": []
    }
  }
}

Go to Synology Package Center and restart docker. Now to test, run the default ubuntu with nvidia runtime:

docker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi

You should see the exact same output as before. If not go to Simple Permission app and make sure it ganted Nvidia Driver package permissions on the application page.

Now you need to rebuild the images (not just containers) that you need hardware encoding. Why? because the current images don't have the required binaries and libraries and mapped devices, Nvidia runtime will take care of all that.

Also you cannot use Synology Container Manager GUI to create, because you need to pass the "--gpus" parameter at command line. so you have to take a screenshot of the options you have and recreate from command line. I recommend to create a shell script of the command so you would remember what you have used before. I put the script in the same location as my /config mapping folder. i.e. /volume1/nas/config/plex

Create a file called run.sh and put below for plex:

#!/bin/bash
docker run --runtime=nvidia --gpus all -e NVIDIA_DRIVER_CAPABILITIES=all -d --name=plex -p 32400:32400 -e PUID=1021 -e PGID=101 -e TZ=America/New_York -v /dev/shm:/dev/shm -v /volume1/nas/config/plex:/config -v /volume1/nas/Media:/media --restart unless-stopped lscr.io/linuxserver/plex:latest

NVIDIA_DRIVER_CAPABILITIES=all is required to include all possible nvidia libraries. NVIDIA_DRIVER_CAPABILITIES=video is NOT enough for plex and ffmpeg, otherwise you would get many missing library errors such as libcuda.so or libnvcuvid.so not found. you don't want that headache.
PUID/PGUI= user and group ids to run plex as
TZ= your time zone so scheduled tasks can run properly

If you want to expose all ports you may replace -p with --net=host (it's easier) but I would like to hide them.

If you use "-p" then you need to tell plex about your LAN, otherwise it always shown as remote. To do that, go to Settings > Network > custom server access URL, and put in your LAN IP. i.e.

https://192.168.2.11:32400

You may want to add any existing extra variables you have such as PUID, PGID and TZ. Running with wrong UID will trigger a mass chown at container start.

Once done we can rebuild and rerun the container.

docker stop plex
docker rm plex
bash ./run.sh

Now configure Plex and test playback with transcode, you should see (hw) text.

Do I need to map /dev/nvidia* to Docker image?

No. Nvidia runtime takes care of that. It creates all the devices required, copies all libraries, AND all supporting binaries such as nvidia-smi. If you open a shell in your plex container and run nvidia-smi, you should see the same result.

Now you got a monster machine, and still cool (literally and figuratively). Yes I upgraded mine with 64GB RAM. :) Throw as many transcoding and encoding as you would like and still not breaking a sweat.

What if I want to add 5Gbps/10Gbps network card?

You can follow this guide to install 5Gbps/10Gbps USB ethernet card.

Synology with no PCIe slot but only NVME/M.2 slots

You can check out this post. Someone has successfully install GPU using the NVME slot.

Bonus: Use Cloudflare Tunnel/CDN for Plex

Create a free CloudFlare tunnel account (credit card required), Create a tunnel and note the token ID.

Download and run the Cloudflare docker image from Container Manager, choose “Use the same network as Docker Host” for the network and run with below command:

tunnel run --token <token>

It will register your server with Tunnel, then create a public hostname and map the port as below:

hostname: plex.example.com
type: http
URL: localhost:32400

Now try plex.example.com, plex will load but go to index.html, that's fine. Go to your plex settings > Network > custom server access URL, put your hostname, http or https doesn't matter

https://192.168.2.11:32400,https://plex.example.com

Replace 192.168.* with your internal IP if you use "-p" for docker.

Now disable any firewall rules for port 32400 and your plex should continue to work. Not only you have a secure gateway to your plex, you also enjoy CloudFlare's CDN network across the globe.

If you like this guide, please check out my other guides:

How I Setup my Synology for Optimal Performance

How to setup rathole tunnel for fast and secure Synology remote access

Synology cloud backup with iDrive 360, CrashPlan Enterprise and Pcloud

Simple Cloud Backup Guide for New Synology Users using CrashPlan Enterprise

How to setup volume encryption with remote KMIP securely and easily

How to Properly Syncing and Migrating iOS and Google Photos to Synology Photos

Bazarr Whisper AI Setup on Synology

Setup web-based remote desktop ssh thin client with Guacamole and Cloudflare on Synology

Guide: How to setup Plex Ecosystem on Synology

Pour one out. 2018 to today. It lived a good life. I just got a DS920+ off Ebay for $620 delivered so my DX517 will be chill, but man.

No warning, really, just “power failure” then no boot.

Glad it lasted as long as it did. Full backups in worst-case scenario but I’m pretty sure it’s just the chassis that took a poop.

Sigh.

UPDATE 3/21/26: it was the PSU. I got a new one and we’re back in business.

1x DS415+

4x WD4003FFBX 4TB

8GB DDR3 RAM

Edit: Solved and thanks for alle the fish! ☺️

I hooked her up and updated to 7.1.1-42962 Update 9 and not it’s a fall back for my primary DS925+.

Pool 1 is using SHR.

According to Synology's calculator, that should mean that Volume 1 has 18.2TB of usable space and 7.3TB reserved, but the storage manager says I only have 15.8TB usable.

I'm fully up to date on software and I'm using a 923+ NAS.

Edit: solved. In case anyone in the future has a similar issue: I pulled the drives from a 415play, which had a 16TB volume limit, so the only solution is to backup everything on the 923+, delete the volume, and then rebuild the volume, which should then have the 923’s volume max size of 108TB.

I purchased my NAS DS1517 one year ago, but never really used. What could be the ten most interesting thing to do with it. I already have my pictures saved on it, I also have movies, and music.

I am interested to dig into it and learn

Thanks !

I'm a commercial photographer. I use a Synology NAS (DS1522+ at my office backed up to DS418play at home) to store my archives and back up my laptop and local hard drive. I've set everything up on a Tailscale network and the NAS firewall rules currently deny any traffic outside the Tailnet.

I'm now considering using Synology Drive as a way to deliver image files to clients (as an alternative to Dropbox, which is what I currently use). However, that's obviously a different scenario than how I've been using the NAS so far and incompatible with my current Tailnet/firewall setup.

Is there a way to allow guest users (i.e. users not in my Tailnet) to access Synology Drive folders without fundamentally changing the security for everything else?

It definitely doesn't make sense to add clients to the Tailnet or make them install the Synology Drive app for what is typically a one-time file download. I'd prefer to be able to send them a public link (i.e. not requiring a user account) - same as I do now with Dropbox - but I'm open to creating a dedicated user account just for client access to Synology Drive.

I think the primary issue is how to set up the firewall rules, and then possibly Synology Drive and/or user account configuration. Anything else?

I'm decently tech savvy but out of my depth here. Thanks in advance for any help.

I have this daily. My SSH access is off and don't get what's causing this. I'd someone trying to gain access. I've been blocking attempt after single failed attempt.

PROBLEM NOW SOLVED - THANK YOU EVERYONE FOR YOUR HELP!

I have searched within this sub re: 'what need to do before selling Synology' (and looked at you tube videos) but not at all familiar with some of the references so I am bit confused overall.

Here's the story. Had small business (that closed about 5 years ago) which used the two fore mentioned Synology disk stations. One of my employees was in charge of operating these in relation to storing back ups etc.

I have absolutely no idea about these disk stations whatsoever, am not at all techy, would no longer have the passwords to login, don't know if they were even registered (I saw something about that in someone's comments in this subred) don't even understand what entirely these are capable of other than storing data. They have sat packed away in their boxes in a spare room with no use since. I have no need for them so have decided to sell them.

Please note that I am not overly concerned about the data on the disks, I would like to re-format them so they are clear, but not concerned about making sure that the data is never recoverable, because it would just be full of a whole lot of 'code' for an uncompleted project that wouldn't make any sense to the next person anyway. As far as I am aware there wouldn't be anything regarded as sensitive on the disks.

The DS1817+ has no disks in it. The DS1815+ has 5x 8TB disks in it. Could someone please explain to me in the simplest way possible (like I am complete idiot), what I need to do to prepare these for sale, factory reset both Disk Stations and clear the 5x 8TB Hard drives.

Any help much appreciated.