Dave Russell

@R-a-K-i > What surprises me is that everything works so far. I can create a volume and also activate deduplication. I have no idea why everything is working when you're...

Yes, there'd be a lot of v6 db files left over from DSM 6. Try: ``` sudo rm /var/lib/disk-compatibility/ds1520+_host.db ``` Then close and reopen storage manager.

I see a few potential issues. You didn't run the syno_hdd_db with the -n option to prevent DSM updating the drive database. > ds920+_host_v7 version 8052 > ds920+_host version 4021...

Okay, it's not DSM 7.2.1 update 5. It's the newer host db version. I notice there's also: ``` "barebone_installable_v2": "auto", ``` I'll add size_gb and "barebone_installable_v2": "auto"

Delete ds920+_host.db and ds920+_host.db.new ``` sudo rm /var/lib/disk-compatibility_ ds920+_host.db sudo rm /var/lib/disk-compatibility_ ds920+_host.db.new ``` Then delete "volume1/homes/scripts/Synology_HDD/syno_hdd-db.sh -n" from the shutdown task. Next create bootup task with "volume1/homes/scripts/Synology_HDD/syno_hdd-db.sh -n". Then...

Leave syno_enable_m2_volume.sh as a shutdown task. But also leave the syno_enable_m2_volume.sh shutdown task disabled for now. You should **not** need it with a DS920+ running DSM 7.2.1.

Was storage manager already open? If yes, then close and reopen storage manager.

Unrecognized firmware would not cause the drive to be marked as critical. You could run https://github.com/007revad/Synology_SMART_info to see why DSM is saying it is critical.

Only 615 power on hours. It's been used for less than 4 weeks. I noticed the 25 "Unsafe Shutdowns" too. My NVMe drives have about 5, but it's because I...

That makes sense. Though the 25 "Unsafe Shutdowns" are a concern if you didn't remove the drive while it was powered on 25 times, or maybe the notebook shut down...