upvote

points

by SideburnsOfDoom4 hours ago |
comments
upvoteby wccrawford4 hours ago|
next
[-]
They did it for a very short time. The community backlash was so bad that they recanted immediately.

I'm not at all surprised that Ubiquiti is getting ahead of that and promising it from the start.

reply
upvoteby luma3 hours ago|
parent|
next
[-]
Kinda, NVME devices still need to be on their HCL and are priced about what you would expect.
reply
upvoteby layer82 hours ago|
parent|
prev|
next
[-]
Not immediately, it took about half a year of watching sales numbers drop, and they still have restrictions.
reply
upvoteby SideburnsOfDoom2 hours ago|
parent|
prev|
next
[-]
> Synology recanted immediately

Is that correct? Looking at a common flagship model, the 4-Bay DS925+

and then the "Compatibility list" here https://www.synology.com/en-global/compatibility?search_by=d...

I see only Synology branded drives.

Synology do not make their own hard drives. They are rebadged.

reply
upvoteby Hamuko2 hours ago|
parent|
[-]
It's true for HDDs. They don't maintain a list of compatible third-party HDDs, but you use them perfectly fine. No errors, drive health monitoring works, etc.

https://www.guru3d.com/story/synology-reverses-policy-bannin...

>Now, with the release of DSM 7.3, Synology has quietly walked the policy back. Third-party hard drives and 2.5-inch SATA SSDs can once again be used without triggering warning messages or reduced functionality. Drives from Seagate, WD, and others will work exactly as they did before—complete with full monitoring, alerts, and storage features.

NVMe SSDs are different.

reply
upvoteby Hamuko3 hours ago|
parent|
prev|
[-]
They still require you to buy their overpriced (even by AI bubble standards) NVMe drives with zero third-party support. There is a project that adds third-party SSD support for newer Synology devices, but you need to redo it every time your NAS updates, so it's very much unsupported. Would definitely not say that they "recanted immediately".
reply
upvoteby chrisweekly4 hours ago|
prev|
[-]
[dead]
reply