Hello,
I have a bit of a problem with the S3 Plugin, the log shows:
Mar 14 11:30:57 NAS s3_sleep: ----------------------------------------------
Mar 14 11:30:57 NAS s3_sleep: s3_sleep process ID 7685 started, To terminate it, type: s3_sleep -q
Mar 14 11:30:57 NAS s3_sleep: Disk activity on going: sdb
Mar 14 11:30:57 NAS s3_sleep: Disk activity detected. Reset timers.
Mar 14 11:31:57 NAS s3_sleep: Disk activity on going: sdb
Mar 14 11:31:57 NAS s3_sleep: Disk activity detected. Reset timers.
The problem is, that sdb is spun down and not doing anything. This behaviour appears randomly on SSDs and HDDs. There is nothing scheduled (mover, paritiy etc.) or polling (sata, autofan) in one minute steps. Also the file activity plugin shows nothing. What is wrong here?
@limetechUpdate:
It seems that the problem has something to do with the intentionally broken SSD standby since 6.9.
When SSDs are set into standbymode via console (hdparm -y), then it works as intended. Right now I'm not able to get back the spindown (=standby) command for SSDs from Unraid 6.8.3, since there is no comment or help on this decision from the developers. That's kind of a dealbreaker, since many chipsets (including mine) go into the lowest C-States, when drives remain active.
Thanks in advance