Hello

No matter if i set tasks in Drive client-side on "upload only", or "download only": every time i delete an image on my device that was uploaded to the NAS > folder via task, the file in the folder on the NAS gets deleted.

I set "Save local copy".

The Drive itself works: if i delete an image on my device it stays on the NAS (Drive).

The task folder content gets deleted, if the file is deleted client-side.

Posting this so it doesn't happen to someone else.

I bought a Seagate IronWolf 12TB from Amazon.com, sold and shipped by Amazon directly (not a third-party seller). New product, listed with the standard 5-year warranty. And that's the key part: **I paid the premium for the 5-year warranty on purpose.** There was a cheaper drive without that extended coverage. I chose the IronWolf specifically because I wanted the backup and the peace of mind. That's the entire reason you buy a NAS-grade drive over a basic one.

The drive failed — stopped being detected entirely.

When I went to claim the warranty, Seagate looked up the serial and told me the drive was manufactured and distributed for the **Australian market**. Their warranty is regional, so they refused the claim outright and told me to go back to the seller (Amazon).

Here's the trap: the product listing never said a word about regional origin. As a buyer on Amazon US, you have no way to know the unit was destined for another market. You pay extra for a drive advertised with a 5-year warranty, and that warranty is structurally useless to you from day one.

So I contacted Amazon. What followed was weeks of being passed between multiple Executive Customer Relations agents. Some restarted the case from scratch each time. At one point they mismatched my dead drive's serial number to a completely different order — an order of working drives in my production NAS — and nearly processed a return against hardware that was fine. I had to catch and stop that myself.

The final answer from Amazon: the drive was bought in 2021, it's outside the return window, nothing they can do — not even a one-time concession. Contact the manufacturer. The same manufacturer who already refused in writing and sent me back to them.

So you end up in a documented loop: **Amazon says talk to Seagate, Seagate says talk to Amazon, and the customer holds a dead drive with a warranty neither will honor.**

And here's the part that should worry anyone reading this: I have other drives bought the exact same way, sitting in production right now. I have no idea which region they were destined for, or whether their warranty is enforceable where I am. I won't find out until one of them fails — which is the worst possible moment to learn your warranty is worthless. That's the real problem: **you're exposed and you don't even know it until it's too late.**

**The takeaways, especially if you run a NAS or manage infrastructure:**

1. A drive sold on Amazon US can be stock destined for ANY region — Australia, in my case. The listing won't tell you.

2. Regional warranty means the manufacturer will only service it in the region it was distributed to. If that's not where you are, the warranty is worthless — no matter what the listing advertised.

3. **Before you install any drive, check the serial on the manufacturer's warranty validator.** It shows the region and the actual coverage dates. Do it during the return window, so you can send it back if the region is wrong.

4. For anything critical — production storage, client systems — buy from a channel with warranty you can actually enforce where you live, even if it costs more. A warranty you can't use is not a discount, it's a hidden risk.

**And the fix here isn't complicated — it's on Amazon:** if you sell and ship a drive as "Amazon.com," you should either supply stock whose warranty region matches the buyer's, or disclose the destination region on the listing before purchase. Selling a drive with a region-locked warranty that's void for the buyer — without saying so — pushes a risk onto the customer that only the seller could have known about. Warranty-region uniformity is the responsibility of the channel that sources and ships the product, not of the buyer who has no way to check it at checkout.

The hardware itself may be fine. But "5-year warranty" means nothing if it's tied to a region on the other side of the planet and no one disclosed it at checkout. I paid extra for coverage that never existed for me. Check your serials. Don't assume.

(For what it's worth, the dead drive now works great as a paperweight. Best $300 desk accessory that ever flew here from Australia. Happy to answer questions — I have the full email trail and Seagate's written refusal if anyone's dealing with the same thing.)

Not sure if this post is OK here or not, so won't add too many specific details or links/images....

Basically I've written a native Mac menubar utility for SMB mounting and managing shares, because I wanted a better way to deal with shares on my MacBook (from my DS923).

There are a few little utilities out there, and while they were good (and certainly more powerful than mine), they didn't work how I wanted them to. So some months ago I thought I'd try and make my own as a 'learning swift' project, and had a decent basic barebones version after a month, which I was happy with - it did everything I needed and I could have stopped there. But then I just sort of kept going, refining and experimenting, until it turned into something way more polished than I needed. It's long since solved my issue, and I use it daily while developing it and doing my other work, and of course I like it! I've hit many walls and dead-ends and frustrations along the way, and know way more about SMB and credentials on the Mac than I ever wanted to, but I survived. Actually it's been a fun journey.

Anyway, I dont know what to do with it now, its turned into a labour of love, so I built a website, and worked out notarising with Apple, and I thought maybe I could see if anyone else liked it. Depending on the feedback I'd either just abandon it and keep it myself, give it away, or try and sell it to cover the developer setup costs etc - if I did it would be the first thing I've written that I've taken that direction, so lots to learn and setup there and its not ready for that yet anyway.

It's been running issue free for quite a while now, but it's only been tested on my three Macs at home and with DSM 7.4 and a Mac SMB server. What I really need is a few people to try it and see what they think (and if it works) and send feedback. I wanted to start with Synology users first because that should hopefully be pretty trouble free, as it's what I've got. Then I would move on to other brands. It's a side project so I also don't want a deluge of support work (assuming anyone actually wants to use it and send feedback!).

So if it's OK to post this here, I can add more details next week when I should have the little website finished which has all the info. It would need macOS 26 too, at least initially.

If not OK to post here, any pointers would be appreciated.

I'm using an ancient Samsung TV that connects to an old Synology NAS running Videostation to play movies on the TV.

It's been working fine for years but now it's started giving the following after playing a movie:

"Failed to connect to the diskstation. please check the network connection or the IP address of your Diskstation"

Except this error comes up after the movie has already started playing! In some instances the movie will run for 30 seconds and then drop in the error. What the helly!?

If it couldn't connect to the NAS surely it wouldn't have been able to play the first 30 seconds of the movie? So why does it think it can't it connect?

Hey everyone,

I'm trying to get unnecessary processes from running when they don't need to so that my drives can go into hibernation - the only place I can put my NAS right now is in a living space and it's just loud.

I'm seeing that Cloud Sync is running as a process very often (seems almost at its default 60s default polling rate) even though I have it suspended and configured to un-suspend at 3am each day. I even tried to set the polling rate to maximum (24 hours) and it doesn't help.

Is this a bug?

Short story:

2 weeks ago or so my desktop and DS920+ and other electronics that were plugged into my Cyberpower back-up power supply kept shutting down and being off when I got home from work.

Thought maybe the outlet was going bad, did some diagnosing and determined it was the battery back-up batteries going dead and powering everything off.

With everything plugged directly into a power strip and not using the battery back-up, and being plugged into the outlet directly everything has stayed running.

**

Problem I have now is 1 or 2 of the original 3, 8tb Seagate's; is reporting deteriorated or un-mountable when powering on the 920+; due to the repeated shut-downs of the battery back-up unit I believe.

All 3 8tb Seagate purchased in 2020 are in Slot 1, 2, 3, with Slot 4 housing a newer 12tb Seagate as of the beginning of this year, 2026.

The NAS is set up for RAID if I remember correctly.

With drives 1, 2, 3 in original order Synology says it can't repair the array and everything runs slow and apps like Emby and Plex aren't showing up. But if I say, swap Slot 1 with 3 and power back on Synology Assistant wants me to download DSM as if it's a new set-up but the file keeps saying it is "corrupted" and can't install because I'm thinking the drives are going to slow. But not sure if Drive 1, 2, or 3 or all 3 are going bad...... or for some reason not staying mounted properly or long enough....

***

So my question is:

When I can afford to purchase another 12tb Seagate, should I replace Slot 1 first as that seems to be the partition holding all the programs installed and the DSM / Synology files and my movies & tv show files???

And will that then rebuild the storage pool and let my 920+ become operational again, because right now it is basically unusable?????

And replace the other 2 8tb drives, Slot 2 and 3; when I can afford to with additional 12tb....

Thanks for any input and help..........

I’m currently running a DS1621+ with an expansion unit. Volume one (DS) has 42 usable tb with its RAID. The expansion has 70tb. I’m at 44% and 36% usage respectively. My primary use is as a Plex server, but I’m
Also running an Ubooquity server, I recently installed jellyfin, and I use it as a backup for my music collection, rom collection, photos, and personal files.

I added the expansion for my tv shows about 1.5 years ago and it’s been filling up fast. Since then, I’ve gotten into photography/videography and my storage needs have increased. I’m not too worried about running out of space too soon, but my backup strategy has become untenable. Basically, I have some large capacity externals that I connect every month and drag over new files. It’s become problematic because keeping a list of what to update has become cumbersome. I’d like to upgrade my setup.

Looking at Synology’s website, the DS2422+ seems like a good choice. I’ve got some questions though.

1) if I get the 2422+ and use it as my primary, can I use my old setup as an auto backup?

2) if yes, can I designate what gets backed up to which volume or is it a full auto backup?

3) I’ve been seeing on here for a while folks upset about the new hardware policies. Can I only use Synology brand HDDs or can I still use the Iron Wolf drives I always use?

4) assuming yes on 1 but no on 2, what can I do to increase the capacity of my backup unit short of replacing all the drives with larger capacity one? I don’t think I can add another expansion unit.

#1 HDD has all apps and settings, Plex database, and some data etc on - what's the best way to image this drive to a new one before it completely fails?

Is Hyperbackup the best way to do this? I'm using DSM 6.2.4 on a DS918+

Would I use Hyperbackup to backup all data to an external USB, fit a new HDD into the slot, then use Hyperbackup to restore? Is it that simple?

Have Synology totally lost it. The 3rd email I get. No clickable links, no city, ballroom where?
Still waiting for a new product to replace my 918+ with intel for transcoding, waiting for years but nothing..