OMV4 to OMV5 upgrade spin down hdd problem

I did an upgrade from omv4 to omv5, and I also upgraded armbian from strech to buster version. For now, the only problem I have is that my disk is not going to spin down. Before that on omv4 it worked properly. For spin down I used a jmicron controller.

I reinstalled the firmware and set the time for the spin down with command below. I also made a cold boot, but I didn't achieve anything with that.

My NAS is Odroid HC2 with 4 tb WD Red hdd.

Do you have any idea what to do to fix this?

root@odroid:~# ./JMS578FwUpdate -d /dev/sdb -f ./JMS578-Hardkenel-Release-v173.01.00.02-20190306.bin -b ./backup.bin -t 30

I use settings like this now in omv5, and I also used them in omv4 and everything worked properly. For a test, I can completely turn off smart.

Same thing. HDD still doesn't go into spin down. I forgot to mention before that if I give the command hdparm -y / dev / sdb hdd goes to spin down and can stay sleep for hours. I also can't detect any process that would prevent the disk from going into spin down.

I can't figure out what the problem might be. Something definitely went wrong during the upgrade. Is there any other way for the disk to go into the spin down without being harmful to the disk? Maybe hdparm or hd-idle? If I use one of these two programs then in the jmicron controller I must turn off spin down?

Unfortunately that command does not work with my disk. I managed to run this command and set the spin down to 10 minutes. Now I'm waiting to see if it works.

hdparm -S 120 /dev/sdb

Unfortunately, this doesn't work either. It seems that only this command works with hdparm and my disk:

hdparm -y /dev/sdb

What else can I try to solve this problem?

I also have another Odroid HC2 with a fresh installation of armbian and omv5 and everything works ok

With hd-idle disk goes into spin down after 20 minutes, but it goes into spin down very rarely. I think something often reads or writes on the disk. How to see what it could be about? With iotop I see that kworker has some IO almost every second.

Something is very, very strange to me. Even the hd-idle doesn't seem to work properly. I set the disc to go to spindown after 5 minutes and the disc did not go to spindown. I later checked the log and in the log it was written that the disk was in spindown. He certainly wasn't because I heard him spin. Now I have run your script and the disk has been in spindown for half an hour and is not spinning. I'm not sure what this is about. It doesn’t seem to be any program that prevents the disk from going into spindown but it’s something else.

It is ok, my hdd is sdb.