December 8, 201213 yr Hi guys I am having some issues with automated drive spin down on my Unraid box, and would like to know if you can assist me to troubleshoot and possibly resolve it. I initially configured the drives to automatically spin-down via the HTTP interface, but discovered that the system becomes very unstable after a drive spin's down. thus i rather opted to disable automated spin-down for now, in order to troubleshoot it manually before attempting it again. reading up on the forums it seems spindown is achieved/managed currently by the HDPARM command unfortunately even manually trying to sleep the drive doesnt seem to work see output below : *********************************************************************************************** root@Storage:~# hdparm -C /dev/sdt /dev/sdt: drive state is: active/idle root@Storage:~# hdparm -i /dev/sdt /dev/sdt: HDIO_GET_IDENTITY failed: Inappropriate ioctl for device root@Storage:~# hdparm -I /dev/sdt /dev/sdt: ATA device, with non-removable media Model Number: ST31500341AS Serial Number: 9VS2ZFF9 Firmware Revision: CC1H Transport: Serial Standards: Used: unknown (minor revision code 0x0029) Supported: 8 7 6 5 Likely used: 8 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: 2930277168 Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 1430799 MBytes device size with M = 1000*1000: 1500301 MBytes (1500 GB) cache/buffer size = unknown 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 = ? Recommended acoustic management value: 254, current value: 0 DMA: 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 * DOWNLOAD_MICROCODE SET_MAX security extension * Automatic Acoustic Management feature set * 48-bit Address feature set * Device Configuration Overlay 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-Read-Verify feature set * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Native Command Queueing (NCQ) * Phy event counters Device-initiated interface power management * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Long Sector Access (AC1) * SCT LBA Segment Access (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase 256min for SECURITY ERASE UNIT. 256min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 5000c50019dc5212 NAA : 5 IEEE OUI : 000c50 Unique ID : 019dc5212 Checksum: correct root@Storage:~# root@Storage:~# hdparm -Y /dev/sdt /dev/sdt: issuing sleep command root@Storage:~# hdparm -C /dev/sdt /dev/sdt: No such device or address root@Storage:~# *********************************************************************************************** Thus as per above, after issuing the hdparm - Y on the device, the drive just seems to disappear. Restarting the unraid box is the only way to restore the array - and even worse - seems to invalidate the parity. syslog is attached just in case I am thinking this is a possible linux driver issue, but i am not knowledgeable enough in order to know if drivers can be updated in order to verify if it is resolved. I found the listed linux drivers in the below link : Adaptec Linux drivers page can be found at : http://www.adaptec.com/en-us/support/raid/sas_raid/sas-52445/ I would definitely prefer rather to fix the functionality on my current controller, as i am stuck in south-Africa, and thus obtaining some of the supported controllers will just be too expensive. Any assistance and/or ideas will be appreciated Regards Neo_X syslog3.txt
December 8, 201213 yr hdparm is only used on the cache drive. Use "hdparm spindown 1" to spindown disk 1.
December 8, 201213 yr hdparm is only used on the cache drive. Use "hdparm spindown 1" to spindown disk 1. Actually, the correct command to spindown disk 1 in the array is: mdcmd spindown 1 I think dgaschk just forgot to change the name of the actual command in his response.
December 8, 201213 yr Author hdparm is only used on the cache drive. Use "hdparm spindown 1" to spindown disk 1. Actually, the correct command to spindown disk 1 in the array is: mdcmd spindown 1 I think dgaschk just forgot to change the name of the actual command in his response. Hi Joe thanx for the update. would rather prefer to test on the parity in stead of a data drive. what dis number will the parity be? regards
December 8, 201213 yr hdparm is only used on the cache drive. Use "hdparm spindown 1" to spindown disk 1. Actually, the correct command to spindown disk 1 in the array is: mdcmd spindown 1 I think dgaschk just forgot to change the name of the actual command in his response. Hi Joe thanx for the update. would rather prefer to test on the parity in stead of a data drive. what dis number will the parity be? regards parity disk would be mdcmd spindown 0 if you are not at the "root" home directory, you might have to invoke the "mdcmd" command with the full path: /root/mdcmd spindown 0
December 8, 201213 yr Author hdparm is only used on the cache drive. Use "hdparm spindown 1" to spindown disk 1. Actually, the correct command to spindown disk 1 in the array is: mdcmd spindown 1 I think dgaschk just forgot to change the name of the actual command in his response. Hi Joe thanx for the update. would rather prefer to test on the parity in stead of a data drive. what dis number will the parity be? regards parity disk would be mdcmd spindown 0 if you are not at the "root" home directory, you might have to invoke the "mdcmd" command with the full path: /root/mdcmd spindown 0 ok tried it on drive 0 Dec 8 12:38:31 Storage in.telnetd[17654]: connect from 192.168.0.2 (192.168.0.2) Dec 8 12:38:36 Storage login[17655]: ROOT LOGIN on '/dev/pts/0' from '192.168.0.2' Dec 8 12:43:20 Storage kernel: mdcmd (77): spindown 0 Dec 8 12:43:20 Storage kernel: Dec 8 12:43:29 Storage kernel: sd 1:1:0:0: [sda] Spinning up disk....ready Dec 8 12:43:29 Storage kernel: sd 1:1:0:0: [sda] 5851033600 512-byte logical blocks: (2.99 TB/2.72 TiB) Dec 8 12:46:02 Storage kernel: mdcmd (78): spinup 0 Dec 8 12:46:02 Storage kernel: verified via Unmenu , and the spinning icon did change ( although hdparm-C still showed the particular device as active/idle still) guess next step is to enable spin down on all drives and check again?
December 8, 201213 yr Author *update* after previous post with mdcmd seeming to work, i went ahead to enable the default spin down delay to 15minutes (array is very rarely used with only one client currently connected, so i suspect almost all drives to powerdown. in stead i keep seeing(and hearing) the array to be powered up and powered down continuously - not even obeying the 15minute rule.... any thoughts as to why? syslog is attached. thx *edit* noticed in the syslog a reference to Adaptec aacraid driver 1.2-0. on the website i indicated in the OP, its currently already on version 1.5 for Fedora Core versions of Linux. syslog4.zip
Archived
This topic is now archived and is closed to further replies.