I have a DS1515+ which has an SSD cache function that uses a whitelisted set of known good drives that function well.
If you plug in a non whitelisted ssd and try to use it as a cache, it pops up a stern warning about potential data loss due to unsupported drives with a checkbox to acknowledge that you’re okay with the risk.
So…there’s really no excuse why they couldn’t have done this for regular drives.
Everyone will understand it costing more, fewer people will understand why the NAS ate their data without the warning it was supposed to provide, because cheap drives that didn’t support certain metrics were used.
If Synology wants to have there be only one way that the device behaves, they have to put constraints on the hardware.
As long as Synology is up front in the requirement and has a return policy for users who buy one and are surprised, I think they’re well within their rights to decide they’re tired of dealing with support costs from misbehaving drives.
As long as they don’t retroactively enforce this policy on older devices I don’t understand the emotionality here. Haven’t you ever found yourself stuck supporting software / systems / etc that customers were trying to cheap out on, making their problems yours?
Toyota might have great reasons for opening a chain of premium quality gas stations, but the second they required me to use them, I'd never buy another Toyota for as long as I lived.
I want to bring my own drives, just as I have since I bought my first DS-412+ 13 years ago.
This copy operation is done either while the disk is idling, or forced by stop responding to read and write operations if CMR buffer zone is depleted and data has to be moved off. RAID softwares cannot handle the latter scenarios, and consider the disk faulty.
You can probably corner a disk into this depleted state to expose a drive being SMR based, but I don't know if that works reliably or if it's the right solution. This is roughly all I know on technical side of this problem anyway.
