The Synology RS3621XS+ is a Great System, But One Thing About The Drives... [YouTube Release]

Additional Resources:

Our Synology Tutorials

Benchmarking The Synology RS3621xs+ For The Best Raid Configuration

Synology Active Backup Review: Is It The Solution For You?

Testing Synology and TrueNAS NFS VS iSCSI

Connecting With Us

Lawrence Systems Shirts and Swag



Amazon Affiliate Store

All Of Our Affiliates that help us out and can get you discounts!
:shopping_cart: Affiliates We Love - Lawrence Technology Services

Gear we use on Kit
:shopping_cart: Kit

Try ITProTV free of charge and get 30% off!
:shopping_cart: Learn technology and pass IT certifications with ITProTV

Use OfferCode LTSERVICES to get 10% off your order at

Digital Ocean Offer Code

HostiFi UniFi Cloud Hosting Service
:shopping_cart: HostiFi - UniFi cloud hosting

Protect you privacy with a VPN from Private Internet Access
:shopping_cart: Buy VPN with Credit Card or PayPal | Private Internet Access

Content ethic policy

:moneybag: lawrencesystems is creating Tech Tutorials & Reviews | Patreon

:stopwatch: Timestamps :stopwatch:
00:00 Synology RS3621XS+ Review
01:25 Technichal Specs
03:19 Works Best With Synology Drives
04:08 Network Connectivity
04:49 Power Supplies
05:19 Hot Swap Fans
05:40 Inside The Case
06:07 Noise Levels
06:28 Synology DSM 7

#Synology #NAS #Storage

We got hit with the ridiculous ‘supported’ drives nonsense on a pair of new rs2821rp+ ( which we purchased with ultrastar hc550s as they were literally half the price of the synology/ drives ).

The ‘critical’ state was annoying - but dsm7 also inhibits smart monitoring on ‘unsupported’ drives, which is far worse on a production system

The ‘supported’ drive list for the 2821 is basically all Synology models - plus one 4tb seagate and one 4tb wd - so clearly synology is looking to up sales of their drives, a very cynical move. Hopefully Synology receives sufficient push back from customers that this kind of behaviour is simply unacceptable.

Anyway, the ‘supported drive’ database in DSM7 is just plain text - so if you know what you’re doing it’s trivial to edit it and add the relevant lines to ‘support’ whatever you have - once that’s done no more ‘critical’ state, and the smart tools are usable. The database will get over-written with DSM updates, so will need to be re-editted at that stage ( and as the database only seems to be read on boot that means a double reboot after update - but that’s no big deal )