November 26, 201411 yr I've been using the following command in my go script to put drives that are not in the protected array to sleep: hdparm -S 242 /dev/sd? where ? is the individual drive. Lately, I've noticed two issues: 1) my drives keep changing designations - i.e. sdk will change to sdg thus making one or more of the commands not relevant to drives outside the array 2) none of the drives listed in my go script will actually go to sleep unless I manually do it from MyMain. Has something changed or does someone know a better way to do this?
November 26, 201411 yr 1) my drives keep changing designations - i.e. sdk will change to sdg thus making one or more of the commands not relevant to drives outside the array That is normal computer behavior and has to do with random timings in BIOS and the order the drives get recognized. If you only want to do this for certain drives you'll have to do it differently, perhaps using /dev/disk/by-uuid/ or /dev/disk/by-id/ instead of /dev/sd?.
November 26, 201411 yr Author 1) my drives keep changing designations - i.e. sdk will change to sdg thus making one or more of the commands not relevant to drives outside the array That is normal computer behavior and has to do with random timings in BIOS and the order the drives get recognized. If you only want to do this for certain drives you'll have to do it differently, perhaps using /dev/disk/by-uuid/ or /dev/disk/by-id/ instead of /dev/sd?. Ok, thanks. Should I use the id from blkid? For example: # blkid | grep /dev/sdk EDIT: I did find this thread but the whole label thing is confusing: http://lime-technology.com/forum/index.php?topic=21465.msg190901#msg190901 And this thread where I actually posted over 3 yrs ago! http://lime-technology.com/forum/index.php?topic=7931.0;nowap But neither seems to address the sd? issue. I've tried manually using "by-id" and "uuid" with no success.
December 3, 201411 yr I have this dusty old rc script for my drives, you can hack it anyway you like. It was designed to set hdparm spin down and add PUIS Power Up In Standby mode. I have not used it in years. You can use it as a model, but I don't know how it will work. It demonstrates using configured values in a here document to set HDPARM values on startup. root@unRAID:/mnt/disk1/cache/boot/custom/etc/rc.d# more S01-hdparm #!/bin/bash PUIS="-s1 --yes-i-know-what-i-am-doing" HDPARM_TEST="-Tt " UDMA6="-X udma6" TMPFILE=/tmp/S01-hdparm.$$ trap "rm -f ${TMPFILE}" EXIT HUP INT QUIT TERM while read DISK PARM do [ -z "${DISK%\#*}" ] && continue echo ls -l ${DISK} > ${TMPFILE} read -a LS < ${TMPFILE} # hddtemp -f /dev/null ${DISK} 2>/dev/null hdparm -I ${DISK} | egrep -i 'Number:' | tr -s " " " " | tr -d '\t\n' echo " -> ${LS[10]}" if [ "${SET:=YES}" = "YES" ] then hdparm ${PARM} ${DISK} fi if [ "${TEST:=NO}" = "YES" ] then hdparm ${HDPARM_TEST} ${DISK} fi # hdparm -I ${DISK} | egrep -i standby done <<-EOF # Symlinked devies by serial number # include list with a similar command like this. # ls -1 /dev/disk/by-id | grep scsi-SATA* | grep -v part >> S01-hdparm /dev/disk/by-id/scsi-SATA_ST31000340AS_5QJ0BH1D -S244 # /dev/disk/by-id/scsi-SATA_ST31000340AS_3QJ08RZW -S244 /dev/disk/by-id/scsi-SATA_ST31000340AS_9QJ1Q30B -S244 /dev/disk/by-id/scsi-SATA_ST31500341AS_9VS08VEK -S244 /dev/disk/by-id/scsi-SATA_ST31500341AS_9VS25PKR -S244 /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-00_WD-WCASJ0353226 -S244 ${PUIS} /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-00_WD-WCASJ0437718 -S244 ${PUIS} /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-00_WD-WCASJ0808397 -S244 ${PUIS} /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-00_WD-WCASJ1352706 -S244 ${PUIS} /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-00_WD-WCASJ1353170 -S244 ${PUIS} /dev/disk/by-id/scsi-SATA_WDC_WD10EACS-32_WD-WCASJ0126857 -S244 ${PUIS} # # Hard coded devices # /dev/sda -S242 -s1 --yes-i-know-what-i-am-doing # /dev/sdb -S242 -s1 --yes-i-know-what-i-am-doing # /dev/sdd -S242 -s1 --yes-i-know-what-i-am-doing # /dev/sdc -S242 -s1 --yes-i-know-what-i-am-doing # /dev/sde -S242 -s1 --yes-i-know-what-i-am-doing # /dev/sdf -S242 -s1 --yes-i-know-what-i-am-doing # /dev/sdg -S242 -s1 --yes-i-know-what-i-am-doing EOF exit
December 4, 201411 yr Author I have this dusty old rc script for my drives, you can hack it anyway you like. It was designed to set hdparm spin down and add PUIS Power Up In Standby mode. I have not used it in years. You can use it as a model, but I don't know how it will work. It demonstrates using configured values in a here document to set HDPARM values on startup. Thanks for the reply. It seems no matter what syntax I try, I can't get my devices to be recognized "by-uuid" or "by-id". Here's what I get when I just issue a manual hdparm spindown timer command: Tower login: root Linux 3.9.11p-unRAID. root@Tower:~# hdparm -S 25 /dev/disk/by-id/scsi-SATA_TOSHIBA_DT01ACA300_236DEZJGS /dev/disk/by-id/scsi-SATA_TOSHIBA_DT01ACA300_236DEZJGS: No such file or directory root@Tower:~# hdparm -S 25 /dev/disk/by-id/scsi-SATA_DT01ACA300_236DEZJGS /dev/disk/by-id/scsi-SATA_DT01ACA300_236DEZJGS: No such file or directory root@Tower:~# hdparm -S 25 /dev/disk/by-id/scsi-SATA_ST32000542AS_5XW0343S /dev/disk/by-id/scsi_SATA_ST32000542AS_5XW0343S: No such file or directory I'm sure it's a simple syntax issue but I'm not that proficient with these commands.
December 4, 201411 yr can you do an ls -l on those devices? Look in syslog do an hdparm -tT on those devices first.
December 5, 201411 yr What does "ls -l /dev/disk/by-id" show? Model/Serial -> device id root@unRAIDb:/# ls -l /dev/disk/by-id/ | egrep -v 'part|usb' total 0 lrwxrwxrwx 1 root root 9 Dec 4 01:48 ata-HGST_HDN724040ALE640_PK2334PCHX2DLB -> ../../sdc lrwxrwxrwx 1 root root 9 Dec 4 01:48 ata-HGST_HDN726060ALE610_NAG1D7TP -> ../../sdd lrwxrwxrwx 1 root root 9 Dec 3 22:54 ata-HGST_HDN726060ALE610_NAG1DEKP -> ../../sdb root@unRAIDb:/# hdparm -tT /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB: Timing cached reads: 2916 MB in 2.00 seconds = 1457.72 MB/sec Timing buffered disk reads: 496 MB in 3.01 seconds = 165.01 MB/sec
December 7, 201411 yr Author What does "ls -l /dev/disk/by-id" show? =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.12.07 09:22:40 =~=~=~=~=~=~=~=~=~=~=~= Tower login: root Linux 3.9.11p-unRAID. root@Tower:~# ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [0m[01;36mata-Hitachi_HDS5C3020ALA632_ML4220F312RXSK[0m -> [40;33;01m../../sdf[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-Hitachi_HDS5C3020ALA632_ML4220F312RXSK-part1[0m -> [40;33;01m../../sdf1[0m[K lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mata-ST2000DM001-9YN164_W1E1KAXV[0m -> [40;33;01m../../sdk[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-ST2000DM001-9YN164_W1E1KAXV-part1[0m -> [40;33;01m../../sdk1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mata-ST3000DM001-1CH166_W1F2ZDFV[0m -> [40;33;01m../../sdl[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-ST3000DM001-1CH166_W1F2ZDFV-part1[0m -> [40;33;01m../../sdl1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mata-ST32000542AS_5XW024TM[0m -> [40;33;01m../../sdc[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-ST32000542AS_5XW024TM-part1[0m -> [40;33;01m../../sdc1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mata-ST32000542AS_5XW0343S[0m -> [40;33;01m../../sdi[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-ST32000542AS_5XW0343S-part1[0m -> [40;33;01m../../sdi1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mata-ST32000542AS_5XW2ARMA[0m -> [40;33;01m../../sdo[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-ST32000542AS_5XW2ARMA-part1[0m -> [40;33;01m../../sdo1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mata-ST32000542AS_5XW2B7XV[0m -> [40;33;01m../../sdn[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-ST32000542AS_5XW2B7XV-part1[0m -> [40;33;01m../../sdn1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mata-ST32000542AS_6XW01EP1[0m -> [40;33;01m../../sdb[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-ST32000542AS_6XW01EP1-part1[0m -> [40;33;01m../../sdb1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mata-ST32000542AS_6XW04PTA[0m -> [40;33;01m../../sdg[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-ST32000542AS_6XW04PTA-part1[0m -> [40;33;01m../../sdg1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mata-ST32000542AS_6XW055PH[0m -> [40;33;01m../../sdd[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-ST32000542AS_6XW055PH-part1[0m -> [40;33;01m../../sdd1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mata-ST320005XXXX_5XW04ZSB[0m -> [40;33;01m../../sdm[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-ST320005XXXX_5XW04ZSB-part1[0m -> [40;33;01m../../sdm1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mata-ST4000DM000-1F2168_Z300W3KJ[0m -> [40;33;01m../../sda[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-ST4000DM000-1F2168_Z300W3KJ-part1[0m -> [40;33;01m../../sda1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mata-TOSHIBA_DT01ACA300_236BA57GS[0m -> [40;33;01m../../sdj[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-TOSHIBA_DT01ACA300_236BA57GS-part1[0m -> [40;33;01m../../sdj1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mata-TOSHIBA_DT01ACA300_236DEZJGS[0m -> [40;33;01m../../sde[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mata-TOSHIBA_DT01ACA300_236DEZJGS-part1[0m -> [40;33;01m../../sde1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_Hitachi_HDS5C30_ML4220F312RXSK[0m -> [40;33;01m../../sdf[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_Hitachi_HDS5C30_ML4220F312RXSK-part1[0m -> [40;33;01m../../sdf1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_ST2000DM001-9YN_W1E1KAXV[0m -> [40;33;01m../../sdk[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_ST2000DM001-9YN_W1E1KAXV-part1[0m -> [40;33;01m../../sdk1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_ST3000DM001-1CH_W1F2ZDFV[0m -> [40;33;01m../../sdl[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_ST3000DM001-1CH_W1F2ZDFV-part1[0m -> [40;33;01m../../sdl1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_5XW024TM[0m -> [40;33;01m../../sdc[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_5XW024TM-part1[0m -> [40;33;01m../../sdc1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_5XW0343S[0m -> [40;33;01m../../sdi[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_5XW0343S-part1[0m -> [40;33;01m../../sdi1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_5XW2ARMA[0m -> [40;33;01m../../sdo[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_5XW2ARMA-part1[0m -> [40;33;01m../../sdo1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_5XW2B7XV[0m -> [40;33;01m../../sdn[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_5XW2B7XV-part1[0m -> [40;33;01m../../sdn1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_6XW01EP1[0m -> [40;33;01m../../sdb[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_6XW01EP1-part1[0m -> [40;33;01m../../sdb1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_6XW04PTA[0m -> [40;33;01m../../sdg[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_6XW04PTA-part1[0m -> [40;33;01m../../sdg1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_6XW055PH[0m -> [40;33;01m../../sdd[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_ST32000542AS_6XW055PH-part1[0m -> [40;33;01m../../sdd1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_ST320005XXXX_5XW04ZSB[0m -> [40;33;01m../../sdm[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_ST320005XXXX_5XW04ZSB-part1[0m -> [40;33;01m../../sdm1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_ST4000DM000-1F2_Z300W3KJ[0m -> [40;33;01m../../sda[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_ST4000DM000-1F2_Z300W3KJ-part1[0m -> [40;33;01m../../sda1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_TOSHIBA_DT01ACA_236BA57GS[0m -> [40;33;01m../../sdj[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_TOSHIBA_DT01ACA_236BA57GS-part1[0m -> [40;33;01m../../sdj1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mscsi-SATA_TOSHIBA_DT01ACA_236DEZJGS[0m -> [40;33;01m../../sde[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mscsi-SATA_TOSHIBA_DT01ACA_236DEZJGS-part1[0m -> [40;33;01m../../sde1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36musb-SanDisk_U3_Cruzer_Micro_43243218E7908694-0:0[0m -> [40;33;01m../../sdh[0m[K lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36musb-SanDisk_U3_Cruzer_Micro_43243218E7908694-0:0-part1[0m -> [40;33;01m../../sdh1[0m[K lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000039ff4c52641[0m -> [40;33;01m../../sdj[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000039ff4c52641-part1[0m -> [40;33;01m../../sdj1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000039ff4c5a8f3[0m -> [40;33;01m../../sde[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000039ff4c5a8f3-part1[0m -> [40;33;01m../../sde1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000c500162690b7[0m -> [40;33;01m../../sdb[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000c500162690b7-part1[0m -> [40;33;01m../../sdb1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000c5001636101f[0m -> [40;33;01m../../sdd[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000c5001636101f-part1[0m -> [40;33;01m../../sdd1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000c50016361aa1[0m -> [40;33;01m../../sdg[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000c50016361aa1-part1[0m -> [40;33;01m../../sdg1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000c5001648b576[0m -> [40;33;01m../../sdm[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000c5001648b576-part1[0m -> [40;33;01m../../sdm1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000c5001684a5e9[0m -> [40;33;01m../../sdc[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000c5001684a5e9-part1[0m -> [40;33;01m../../sdc1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000c50017d81677[0m -> [40;33;01m../../sdi[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000c50017d81677-part1[0m -> [40;33;01m../../sdi1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000c5002f1021c3[0m -> [40;33;01m../../sdo[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000c5002f1021c3-part1[0m -> [40;33;01m../../sdo1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000c5002f18a1da[0m -> [40;33;01m../../sdn[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000c5002f18a1da-part1[0m -> [40;33;01m../../sdn1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000c5005c688fc6[0m -> [40;33;01m../../sdk[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000c5005c688fc6-part1[0m -> [40;33;01m../../sdk1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000c5006095468b[0m -> [40;33;01m../../sdl[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000c5006095468b-part1[0m -> [40;33;01m../../sdl1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000c50064f214a6[0m -> [40;33;01m../../sda[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000c50064f214a6-part1[0m -> [40;33;01m../../sda1[0m lrwxrwxrwx 1 root root 9 2014-12-07 09:07 [01;36mwwn-0x5000cca369cf5650[0m -> [40;33;01m../../sdf[0m lrwxrwxrwx 1 root root 10 2014-12-07 09:07 [01;36mwwn-0x5000cca369cf5650-part1[0m -> [40;33;01m../../sdf1[0m root@Tower:~#
December 7, 201411 yr Author do an hdparm -tT on those devices first. Do you mean in the go script or just once? I read that the -t and -T hdparm switches should be performed multiple times so wasn't exactly clear what we were trying to achieve with this? Sorry for being such a n00b.
December 7, 201411 yr Author What does "ls -l /dev/disk/by-id" show? Model/Serial -> device id root@unRAIDb:/# ls -l /dev/disk/by-id/ | egrep -v 'part|usb' total 0 lrwxrwxrwx 1 root root 9 Dec 4 01:48 ata-HGST_HDN724040ALE640_PK2334PCHX2DLB -> ../../sdc lrwxrwxrwx 1 root root 9 Dec 4 01:48 ata-HGST_HDN726060ALE610_NAG1D7TP -> ../../sdd lrwxrwxrwx 1 root root 9 Dec 3 22:54 ata-HGST_HDN726060ALE610_NAG1DEKP -> ../../sdb root@unRAIDb:/# hdparm -tT /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB: Timing cached reads: 2916 MB in 2.00 seconds = 1457.72 MB/sec Timing buffered disk reads: 496 MB in 3.01 seconds = 165.01 MB/sec ok, seems to be working now when I use /dev/disk/by-id/ata... Thanks! EDIT: I guess I spoke too soon. While the disk is now being recognized "by-id", it's not spinning down with the -S command?!
December 7, 201411 yr I don't have a definitive answer on this issue. Something is accessing them. What that is, is unknown to me. If these drives are outside the array, perhaps come up in safe mode without loading anything. use the hdparm -S242 command manually to make sure one of the installed packages or plugins are not accessing the drive. Even a well intentioned smartctl command can cause a drive to spin up or stop from being spun down. There's a reason Tom forces a spindown with hdparm -y instead of relying on the drive timers.
December 7, 201411 yr Author I think I understand what you're saying but if something were accessing the system then when I spin them down via MyMain from the UnMenu gui, I might expect them to spin back up from time to time but they never do. Perhaps I just need to issue the same command that MyMain does when I click the arrow to spin it down? How would I determine this?
December 7, 201411 yr Manual spin down is usually via hdparm -y /dev/sd? emhttp spins them up with hdparm -S0 /dev/sd? I don't know enough about mymain to tell you what the details are, perhaps post a note to the author to participate in this thread.
Archived
This topic is now archived and is closed to further replies.