@zen

Here you go: /dev/sdf: issuing standby command SG_IO: bad/missing sense data, sb[]: 70 00 01 00 00 00 00 0a 00 00 00 00 00 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Here's the results of hdparm -I if you're interested. root@WARNAS:~# hdparm -I /dev/sdf /dev/sdf: ATA device, with non-removable media Model Number: TOSHIBA HDWG180 Serial Number: 90J0A00JFBEG Firmware Revision: 0603 Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0 Standards: Used: unknown (minor revision code 0x006d) Supported: 10 9 8 7 6 5 Likely used: 10 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 15628053168 Logical Sector size: 512 bytes Physical Sector size: 4096 bytes Logical Sector-0 offset: 0 bytes device size with M = 1024*1024: 7630885 MBytes device size with M = 1000*1000: 8001563 MBytes (8001 GB) cache/buffer size = unknown Form Factor: 3.5 inch Nominal Media Rotation Rate: 7200 Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Advanced power management level: 128 DMA: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE * Advanced Power Management feature set SET_MAX security extension * 48-bit Address feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * WRITE_{DMA|MULTIPLE}_FUA_EXT * 64-bit World wide name * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE unknown 119[6] unknown 119[7] * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Gen3 signaling speed (6.0Gb/s) * Native Command Queueing (NCQ) * Host-initiated interface power management * Phy event counters * Host automatic Partial to Slumber transitions * Device automatic Partial to Slumber transitions * READ_LOG_DMA_EXT equivalent to READ_LOG_EXT * DMA Setup Auto-Activate optimization Device-initiated interface power management * Software settings preservation unknown 78[7] * SMART Command Transport (SCT) feature set * SCT Write Same (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) * SANITIZE_ANTIFREEZE_LOCK_EXT command * SANITIZE feature set * OVERWRITE_EXT command * Extended number of user addressable sectors * DOWNLOAD MICROCODE DMA command Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase 756min for SECURITY ERASE UNIT. 756min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 5000039a68d04281 NAA : 5 IEEE OUI : 000039 Unique ID : a68d04281 Checksum: correct

Never spin down. Even clicking on the "green dot" in the UI does nothing. SAS Drives behave as expected. The only log entries I can find for "spinning down" the drives are when I set the spin down time on the specific drives: Apr 1 08:04:00 WARNAS kernel: mdcmd (43): set md_num_stripes 1280 Apr 1 08:04:00 WARNAS kernel: mdcmd (44): set md_queue_limit 80 Apr 1 08:04:00 WARNAS kernel: mdcmd (45): set md_sync_limit 5 Apr 1 08:04:00 WARNAS kernel: mdcmd (46): set md_write_method Apr 1 08:04:00 WARNAS emhttpd: spinning down /dev/sdf Apr 1 08:04:00 WARNAS emhttpd: sdspin /dev/sdf down: 1 Apr 1 08:04:14 WARNAS kernel: mdcmd (47): set md_num_stripes 1280 Apr 1 08:04:14 WARNAS kernel: mdcmd (48): set md_queue_limit 80 Apr 1 08:04:14 WARNAS kernel: mdcmd (49): set md_sync_limit 5 Apr 1 08:04:14 WARNAS kernel: mdcmd (50): set md_write_method Apr 1 08:04:14 WARNAS emhttpd: spinning down /dev/sdl Apr 1 08:04:14 WARNAS emhttpd: sdspin /dev/sdl down: 1 Apr 1 08:04:20 WARNAS emhttpd: spinning down /dev/sdi Apr 1 08:04:20 WARNAS emhttpd: sdspin /dev/sdi down: 1 Apr 1 08:04:27 WARNAS kernel: mdcmd (51): set md_num_stripes 1280 Apr 1 08:04:27 WARNAS kernel: mdcmd (52): set md_queue_limit 80 Apr 1 08:04:27 WARNAS kernel: mdcmd (53): set md_sync_limit 5 Apr 1 08:04:27 WARNAS kernel: mdcmd (54): set md_write_method But the drives did not spin down, nor is there a spin up notices later in the logs. I know the drive(s) are still spun up because file access is instantaneous to files on those specific drives. Hardware is a LSI 3008 ---> SuperMicro SAS3 Expander Backplane Again SATA Spin down worked as advertised before installation of SAS spin down plugin. Not blaming, just don't think the issue is anything with the hardware- beyond the drives, nothing has changed in years. As I said, the plugin was a life saver! Currently on 6.12.8, but problem existed in prior versions. Let me know if you'd like any specific diagnostic packages.

Doron, thanks for this plugin! It saved me more than a few bucks spinning down all my SAS drives. I've since retired them for SATA drives, and they no longer spin down since the plugin was installed (which I didn't care about earlier, as I only had 2). Since I have I have now replaced the SAS drives with larger SATA ones and need my SATA spindown to start working again. Uninstalling the SAS Spin down plugin did not solve for the problem. Globally spin down is set for 1h, and I've tried setting it to 15 mins on the same drives. Thoughts?

I think I was CPU bound.. time for more horsepower. But here's the diagnostic info. But I would appreciate it if someone in the know took a look and let me know if there were any other issues. w.a.r.appserver-diagnostics-20210126-0720.zip

I'm using the Preclear plugin to prep/test my drives to create my array. While they were zeroing they were cruising along nicely (150-220 mbps each) but now that one of my drives has started the read process, performance has hit fallen off signficantly. Any thoughts on what to check? SMART is not reporting any errors beyond the typical ECC errors for high capacity drives.