greg0986

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

greg0986's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Smartmontools 7.2 was released at the very end of December, so maybe SAS spin down can finally work properly?
  2. I've just rebooted it, and selected Spin Down on the Main section and this is what it showed: Jan 18 16:16:19 Tower emhttpd: req (2): cmdSpindownAll=true&startState=STARTED&csrf_token=**************** Jan 18 16:16:19 Tower emhttpd: Spinning down all drives... Jan 18 16:16:19 Tower kernel: mdcmd (48): spindown 0 Jan 18 16:16:19 Tower kernel: mdcmd (49): spindown 1 Jan 18 16:16:19 Tower kernel: mdcmd (50): spindown 2 Jan 18 16:16:19 Tower kernel: mdcmd (51): spindown 3 Jan 18 16:16:19 Tower kernel: mdcmd (52): spindown 4 Jan 18 16:16:19 Tower kernel: mdcmd (53): spindown 5 Jan 18 16:16:19 Tower kernel: mdcmd (54): spindown 6 Jan 18 16:16:19 Tower kernel: mdcmd (55): spindown 7 Jan 18 16:16:19 Tower kernel: mdcmd (56): spindown 8 Jan 18 16:16:19 Tower kernel: mdcmd (57): spindown 9 Jan 18 16:16:19 Tower kernel: mdcmd (58): spindown 10 Jan 18 16:16:19 Tower emhttpd: shcmd (150): /usr/sbin/hdparm -y /dev/nvme0n1 Jan 18 16:16:19 Tower kernel: mdcmd (59): spindown 11 Jan 18 16:16:19 Tower root: HDIO_DRIVE_CMD(standby) failed: Inappropriate ioctl for device Jan 18 16:16:19 Tower root: Jan 18 16:16:19 Tower root: /dev/nvme0n1: Jan 18 16:16:19 Tower root: issuing standby command Jan 18 16:16:19 Tower emhttpd: shcmd (150): exit status: 25 Jan 18 16:16:19 Tower emhttpd: shcmd (151): /usr/sbin/hdparm -y /dev/nvme1n1 Jan 18 16:16:19 Tower root: HDIO_DRIVE_CMD(standby) failed: Inappropriate ioctl for device Jan 18 16:16:19 Tower root: Jan 18 16:16:19 Tower root: /dev/nvme1n1: Jan 18 16:16:19 Tower root: issuing standby command Jan 18 16:16:19 Tower emhttpd: shcmd (151): exit status: 25 Jan 18 16:16:19 Tower rsyslogd: Child 7692 has terminated, reaped by main-loop. [v8.33.1 try http://www.rsyslog.com/e/0 ] Jan 18 16:16:19 Tower rsyslogd: Child 7726 has terminated, reaped by main-loop. [v8.33.1 try http://www.rsyslog.com/e/0 ] Jan 18 16:16:19 Tower rsyslogd: Child 7760 has terminated, reaped by main-loop. [v8.33.1 try http://www.rsyslog.com/e/0 ] Jan 18 16:16:19 Tower rsyslogd: Child 7828 has terminated, reaped by main-loop. [v8.33.1 try http://www.rsyslog.com/e/0 ] Jan 18 16:16:19 Tower rsyslogd: Child 7845 has terminated, reaped by main-loop. [v8.33.1 try http://www.rsyslog.com/e/0 ] Jan 18 16:16:19 Tower rsyslogd: Child 7862 has terminated, reaped by main-loop. [v8.33.1 try http://www.rsyslog.com/e/0 ] (Highlighted in yellow are the two NVME drives I installed today) After entering the code you mentioned above and doing it again, this is what it shows: Jan 18 16:20:14 Tower emhttpd: req (4): cmdSpindownAll=true&startState=STARTED&csrf_token=**************** Jan 18 16:20:14 Tower emhttpd: Spinning down all drives... Jan 18 16:20:14 Tower kernel: mdcmd (72): spindown 0 Jan 18 16:20:14 Tower kernel: mdcmd (73): spindown 1 Jan 18 16:20:14 Tower kernel: mdcmd (74): spindown 2 Jan 18 16:20:14 Tower kernel: mdcmd (75): spindown 3 Jan 18 16:20:14 Tower kernel: mdcmd (76): spindown 4 Jan 18 16:20:14 Tower kernel: mdcmd (77): spindown 5 Jan 18 16:20:14 Tower kernel: mdcmd (78): spindown 6 Jan 18 16:20:14 Tower kernel: mdcmd (79): spindown 7 Jan 18 16:20:14 Tower kernel: mdcmd (80): spindown 8 Jan 18 16:20:14 Tower kernel: mdcmd (81): spindown 9 Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter triggered Jan 18 16:20:14 Tower kernel: mdcmd (82): spindown 10 Jan 18 16:20:14 Tower kernel: mdcmd (83): spindown 11 Jan 18 16:20:14 Tower emhttpd: shcmd (162): /usr/sbin/hdparm -y /dev/nvme0n1 Jan 18 16:20:14 Tower root: HDIO_DRIVE_CMD(standby) failed: Inappropriate ioctl for device Jan 18 16:20:14 Tower root: Jan 18 16:20:14 Tower root: /dev/nvme0n1: Jan 18 16:20:14 Tower root: issuing standby command Jan 18 16:20:14 Tower emhttpd: shcmd (162): exit status: 25 Jan 18 16:20:14 Tower emhttpd: shcmd (163): /usr/sbin/hdparm -y /dev/nvme1n1 Jan 18 16:20:14 Tower root: HDIO_DRIVE_CMD(standby) failed: Inappropriate ioctl for device Jan 18 16:20:14 Tower root: Jan 18 16:20:14 Tower root: /dev/nvme1n1: Jan 18 16:20:14 Tower root: issuing standby command Jan 18 16:20:14 Tower emhttpd: shcmd (163): exit status: 25 Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter, R=sdb S=0 Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter triggered Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter, R=sdf S=1 Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter triggered Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter, R=sdg S=2 Jan 18 16:20:14 Tower rsyslogd: Child 8893 has terminated, reaped by main-loop. [v8.33.1 try http://www.rsyslog.com/e/0 ] Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter triggered Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter, R=sdd S=3 Jan 18 16:20:14 Tower rsyslogd: Child 8912 has terminated, reaped by main-loop. [v8.33.1 try http://www.rsyslog.com/e/0 ] Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter triggered Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter, R=sdl S=4 Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter triggered Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter, R=sdk S=5 Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter triggered Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter, R=sdh S=6 Jan 18 16:20:14 Tower rsyslogd: Child 8969 has terminated, reaped by main-loop. [v8.33.1 try http://www.rsyslog.com/e/0 ] Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter triggered Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter, R=sdm S=7 Jan 18 16:20:14 Tower rsyslogd: Child 8988 has terminated, reaped by main-loop. [v8.33.1 try http://www.rsyslog.com/e/0 ] Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter triggered Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter, R=sdi S=8 Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter triggered Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter, R=sdj S=9 Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter triggered Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter, R=sdc S=10 Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter triggered Jan 18 16:20:14 Tower SAS Assist v0.83: debug: syslog filter, R=sde S=11 (Highlighted in yellow are the two NVME drives I installed today)
  3. V0.83 None, just the above messages. Done: Jan 18 13:26:11 Tower emhttpd: req (10): cmdSpindown=disk1&startState=STARTED&csrf_token=**************** Jan 18 13:26:11 Tower kernel: mdcmd (48): spindown 1 Jan 18 13:26:11 Tower SAS Assist v0.83: debug: syslog filter triggered Jan 18 13:26:11 Tower SAS Assist v0.83: debug: syslog filter, R=sdf S=1
  4. I have been waiting for this for ages, so thanks Doron for coming up with an easy to install solution! I do have a problem however, and I've checked the thread and can't see anything like what error I get. Whenever a spin down request is made, or after the 15 minute no activity period has passed and the server tries to spin down the sas drives, it comes up with the below and absolutely spams the system log. Jan 18 08:51:35 Tower emhttpd: req (1): cmdSpindown=parity&startState=STARTED&csrf_token=**************** Jan 18 08:51:35 Tower kernel: mdcmd (48): spindown 0 Jan 18 08:51:35 Tower rsyslogd: Child 11865 has terminated, reaped by main-loop. [v8.33.1 try http://www.rsyslog.com/e/0 ] I'm running a Dell R510, with a Dell H310 HBA card, and 12 Seagate ST6000NM0034 6TB SAS drives. Unraid version 6.5.3 (I know, I need to update but it works so don't want to mess with it)
  5. I've been waiting for SAS spindown/up for absolutely ages! i've for 12 Dell SAS drives in an R510 that won't spin down, so this is fantastic news!