Strider27

@SimonF Yes, I tried several, "Active Streams", "File Activity" and "Open Files". The first two showed nothing, "Open Files" showed a large list including docker etc. which live on the cache drive anyway, disabled Docker and VM manager. Was only getting "find" popping up every 10 secs or so, disabled "Dynamix Cache Directories", "find" stopped popping up, nothing else in the list, still same issue. @doron Removed both plugins as well as Dynamix System Stats and rebooted, same issue. Every time a drive tries to spin down, there is a tiny read from that drive that wakes it up, it is like something is monitoring the drives and spins them up if they try to spin down. The SATA drive is now fully provisioned and is in the same array, seems to spin down no problem (no files on it yet though) Selected New Config and removed the array, drives would not spin down when in unassigned devices list either. EDIT: installed iotop + python 2.7 (needed for iotop) Stopped docker, when spinning down drives, no IO at all in iotop, in GUI shows either 7.9 kb/s or 4.8 kb/s every time I try to spin down manually. EDIT 2: Started randomly working but not all drives can be spun down. 3 left that can't spin down... only thing that changed is I installed Dynamix SCSI Devices at some point in the last few hours (tested spin down immediately after installing and configuring it, didn't work at the time) . And the server has been up for a few hours without me rebooting for testing.

Hi all, Similar issue here, my 8 SAS drives spin back up immediately after spin-down. Getting the below both when manually or automatically spun down. Aug 12 01:45:25 MKRAID emhttpd: spinning down /dev/sdh Aug 12 01:45:25 MKRAID SAS Assist v2022.08.02: Spinning down device /dev/sdh Aug 12 01:45:25 MKRAID emhttpd: read SMART /dev/sdh So had the SAS plugin installed since it's early days. It didn't work at the time so left it alone until a few days ago. A few days ago tested out manual spin down and it worked mostly fine but had a few things that had to be moved to cache pool to prevent drives spinning up unnecessarily. While was doing that decided to add another HBA and add some more SAS drives to the array on that HBA...... also installed Dynamix Autofan ..... realised the drives no longer spin down and the additional HBA consumes about 50W by itself..... Removed new unmapped drives and the HBA. Restarted, spin-down still not working.... Shutdown all Docker containers. Same Issue. After some digging discovered that Dynamix Autofan can mess with the spin-down.... Tried the custom file for autofan that supposedly fixes it from earlier in the thread, still no luck. Nuked Dynamix Autofan... same problem. Found info somewhere on this forum that adding blank slots with unassigned devices to the array will prevent spin-down. Stopped the array and removed blank slots with unassigned devices that I added earlier when was planning on adding more drives. Same issue. Tried the wrapper for smartctl from earlier in the thread... it only gets me as far as emhttpd Aug 12 02:19:27 MKRAID emhttpd: spinning down /dev/sdl Aug 12 02:19:27 MKRAID SAS Assist v2022.08.02: Spinning down device /dev/sdl Aug 12 02:19:28 MKRAID emhttpd: read SMART /dev/sdl Aug 12 02:19:28 MKRAID smartctl wrappper[7713]: Caller is smartctl_type, grandpa is emhttpd, args "-A /dev/sdl" Aug 12 02:19:28 MKRAID smartctl wrappper[7713]: stdin passed "", hex "" Aug 12 02:19:28 MKRAID smartctl wrappper[7713]: RC=0 Restored to an Unraid flash backup from a day before, when spin-down worked. Same issue. Nuked all Dynamix utilities. Same issue. Nuked most of the other plugins, only have Community Applications, Spin Down SAS Drives, User Scripts (no scripts scheduled to run or active), Same issue. Added a SATA drive to the array, paused DISK-CLEAN, spin-down works fine on that SATA Drive. (it is still being prepped so not fully part of the array, so the test is not 100% conclusive) Switched from UEFI to Legacy boot to test things out. Same Result. P.S. I may have updated the Spin Down SAS Drives plugin when I was adding drives. My Drives are SEAGATE ST320004CLAR2000 BS17 The HBA is SAS9205-8i rebranded by HP it is in IT mode Unraid is 6.10.3 Diag is attached bellow, hope the devs can help mkraid-diagnostics-20220812-0308.zip