Auto-Spindown of hdd's does not work on OMV6

Quote from wsxws

his drive have been working i a synology-nas and standby worked fine

afterwards they have been used in unraid and standyby worked fine

now they are used in omv6 the automatic standy does not work fine

when i use hdparm -y /dev/sdxx the go down

but some time later they are running again

I have the same problem and I just tried -y and it worked. But I've had this problem in OMV 5.x too, although at some earlier point in 5.x it worked. Then it did not. After upgrading to 6.x it still doesn't work. Since I was fixing some other issues, it brought be me, and I am going to try using hd-idle.

Same here using sdparm (external usb drives), drives no longer spindown and if I force it it randomly spin up again

sdparm throws this now

mode sense command: Illegal request
change_mode_page: failed fetching page: Background control (SBC)

It was working fine on OMV5

Should probably do a clean install of OMV 6

EDIT : Weird, going back to OMV5 the error still shows up but drives spindown as expected

I can confirm that hdd spindown doesn't work anymore on a fresh install of OMV 6. It worked perfectly on OMV 4. I skipped OMV 5.

1. Altering the drive settings through the OMV interface does nothing and nothing gets stored in the hdparm.conf either. Don't know if this is expected behaviour.

2. Manually editing the hdparm.conf with my previous settings does nothing:

quiet
/dev/disk/by-id/ata-Samsung_SSD_850_EVO_250GB_S3R0NF1J800330R {
    write_cache = on
}
/dev/disk/by-id/ata-WDC_WD30EZRX-00D8PB0_WD-WCC4N0ZCFKS7 {
    apm = 255
    spindown_time = 240
    write_cache = on
}
/dev/disk/by-id/ata-WDC WD60EZRZ-22GZ5B1-WD-WX61D893R9FX {
    apm = 255
    spindown_time = 240
    write_cache = on
}

After a fresh installation of OMV 6 I can confirm that changes in the OMV interface got properly reflected in the hdparm.conf this time though I can't get the drives to spindown no matter the settings. My previous settings which worked perfectly for years in OMV 4.x don't work either. I tried to not activate S.M.A.R.T. and deactivated monitoring and basically kept the OMV installation as unaltered as possible. Basically I just tried to get proper spindown without configuring anything else beforehand but without success. I am using a german OMV setup btw. if that helps to debug.

"omv-showkey hdparm" does nothing ("command not found") if I run in the terminal or where am I supposed to run this?

Just installed OMV 5 and spindown works as expected and like it used to work on OMV 4 with exact same settings.

Quote from macom

Was hadparm working for you with OMV5 and the same drives?

I'm using OMV5 for about 2 year.

RPi4 + USB HUB + 4 WD USB HDD.

OMV5: Auto spin down work great, SMART inform show: APM 1.

Same devices with fresh install of OMV6: APM settings don't apply to drives.

My Settings in OMV6:

APM: 1
AAM: Disabled
Time: 10 min
Caché: ON

S.M.A.R.T inform:
AAM: Disabled
APM: 128

OMV6 hdparam.conf

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.


/dev/disk/by-id/usb-WD_Elements_2620_57583132443630324154564A-0:0 {
apm = 1
spindown_time = 120
write_cache = on
}

SMART inform:

I have the same problem: no auto spindown on fresh OMV6. Is there already a solution?

root@OMV:~# omv-showkey hdparm
<hdparm>
<uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
<devicefile>/dev/xxx</devicefile>
<apm>0 = disable|1-255<apm>
<aam>0|128|254</aam>
<spindowntime>0 = disabled|1-254</spindowntime>
<writecache>0|1</writecache>
</hdparm>
<hdparm>
<uuid>1dde588b-75a4-49ef-ba2d-7c72c13442c6</uuid>
<devicefile>/dev/disk/by-id/ata-SAMSUNG_HD103SI_S1Y5J9CZ109589</devicefile>
<apm>127</apm>
<aam>0</aam>
<spindowntime>240</spindowntime>
<writecache>0</writecache>
</hdparm>

root@OMV:~# cat /etc/hdparm.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.


/dev/disk/by-id/ata-SAMSUNG_HD103SI_S1Y5J9CZ109589 {
apm = 127
spindown_time = 240
write_cache = off
}

Here's what else I've noticed. Maybe it helps with troubleshooting?

When I manually spindown the HDD via hdparm -y and it comes up again it stays up.

If I manually put the drive into spindown and then it wakes up again, it stays awake. It no longer goes into spindown.

But if I then read the hard disk information and status via hdparm -I and hdparm -C, it goes into spindown after a short time. Strange, isn't it?

Hi

I have 2 ODROIDN2 installed with OMV. The first one is the version 5 and the other one the version 6. On the OMV6 the spindown works only for one HD, the other doesn't spin down. On the OMV5 auto spin down works fine. HD cases are the same on both odroid and same size (2*4*8TB)

I checked in the hdparm.conf and it's looks like fine.

The only reliable way to spin down drives seems to be hd-idle as of now. My new WD Red Pro 12 TB drive would also not spin down on OMV 5 using hdparm while all other WD drives (greens and blues) would spin down reliably. Using hd-idle the drives reliably spin down on OMV 5 and OMV 6 including the brand new WD Red Pro.

Tinkering with hdparm seems to be pointless at this point.

On a fresh OMV 6 install you will need to install gnupg2 before you can install hd-idle through the adelolmo repo as explained in the linked tutorial below:

sudo apt-get install gnupg2

Post

[How-To] Spin-down hard drives with hd-idle

INTRODUCTION

If you like to spin-down your hard drives but you’re having trouble in doing so, you’re not alone.

Not all hard drives like hdparm, the utility used by Debian and OpenMediaVault. There’s an alternative called hd-idle which does the job but introduces another issue: it will eventually fail if you use standby/hibernation on your server, plus other inconveniences.

Hd-idle has been abandoned many years ago and was left in a buggy state, but we finally have a solution: a…

auanasgheps

Jan 9th 2021

My current WD Reds (3Gb) just say APM is not supported:

# hdparm -B /dev/sda

/dev/sda:
 APM_level    = not supported

I guess hd-idle is the way.

Quote from backslash

The only reliable way to spin down drives seems to be hd-idle as of now. My new WD Red Pro 12 TB drive would also not spin down on OMV 5 using hdparm while all other WD drives (greens and blues) would spin down reliably. Using hd-idle the drives reliably spin down on OMV 5 and OMV 6 including the brand new WD Red Pro.

Tinkering with hdparm seems to be pointless at this point.

On a fresh OMV 6 install you will need to install gnupg2 before you can install hd-idle through the adelolmo repo as explained in the linked tutorial below:

Code

sudo apt-get install gnupg2

Post

[How-To] Spin-down hard drives with hd-idle

INTRODUCTION

If you like to spin-down your hard drives but you’re having trouble in doing so, you’re not alone.

Not all hard drives like hdparm, the utility used by Debian and OpenMediaVault. There’s an alternative called hd-idle which does the job but introduces another issue: it will eventually fail if you use standby/hibernation on your server, plus other inconveniences.

Hd-idle has been abandoned many years ago and was left in a buggy state, but we finally have a solution: a…

auanasgheps

Jan 9th 2021

Display More

I didn't need to install gnupg2. But, yes true words. tinkering with hdparm seems to be pointless at the moment.

I also had spindown issues with my 8 WD Red 10TB disks. In my case not all drives made the spindown, here an example:

hdparm -C /dev/sd[abcdefgh]

/dev/sda: drive state is:  standby

/dev/sdb: drive state is:  standby

/dev/sdc: drive state is:  active/idle

/dev/sdd: drive state is:  active/idle

/dev/sde: drive state is:  active/idle

/dev/sdf: drive state is:  active/idle

/dev/sdg: drive state is:  standby

/dev/sdh: drive state is:  standby

Sometimes I saw 7 of my 8 disks in standby. Why not all disks? I don't understand this.

The following command always brought all 8 disks to standby:

hdparm -y /dev/sd[abcdefgh]

My hdparm.conf was configured through OMV6 web interface and looked as follows for all eight disks:

/dev/disk/by-id/... { 
apm = 127 
spindown_time = 120 
write_cache = off
}

Played around with the hdparm settings by the omv web interface, but it didn't get better.

So I installed hd-idle and it seems to do what is expected. Thanks for the link to the good How-To.

Regards Hoppel

My impression is also that SMART monitoring keeps waking up my Red Pro drive, no matter how the SMART monitoring is being configured. This seems also to be the case when using hd-idle instead of hdparm. This is not the case with all my other WD drives.

After 5 days with hd-idle I can say that it works in my environment