[[Plugin] Spin Down SAS Drives]

5 hours ago, doron said:

Sure is... Check out the output file (or see below). Thanks for your help!

 

      "controller": {
        "Slot": "01:00.0",
        "Class": "Serial Attached SCSI controller [0107]",
        "Vendor": "Broadcom / LSI [1000]",
        "Device": "SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] [0064]",
        "SVendor": "Broadcom / LSI [1000]",
        "SDevice": "9200-16e 6Gb/s SAS/SATA PCIe x8 External HBA [3030]",
        "Rev": "02"

Not sure if you need this info or not. After the sas-util command, the drives didn't go back to Standby as UnRaid still had them grey balled. I started use some of the drives and those went to standby after the time set in UnRaid (1hr). The others I just clicked on the grey ball in UnRaid and they went green, then after 1hr they also went to Standby.

 

Working Great!

 

 

[[Plugin] Spin Down SAS Drives]

53 minutes ago, doron said:

Thanks for reporting! I'm really happy to hear that.

 

Would you mind running

/usr/local/emhttp/plugins/sas-spindown/sas-util

and send me the resulting file (/tmp/sas-util-out)?

(when run without parameters it doesn't do anything intrusive, just reports the HDD and controller(s) models in JSON format)

You can pm me or post here (no sensitive info such as serial numbers etc. is shared). Thanks

Sure thing.

Doesn't look like it is showing the controller. I have UnRaid running in a VM Proxmox now. So the controller is a LSI SAS9200-16e flashed to P20 IT mode.

Happy to help any way I can. Thanks again very very much!

 

sas-util-out

[[Plugin] Spin Down SAS Drives]

22 hours ago, doron said:

I've just pushed a new version - 0.8 - of the plugin, supporting 6.9.0-rc1 and its new spin up/down mechanisms.

As always, please report issues.

Many Thanks doron and limetech for working through this. My setup is finally working. I installed the new release candidate version and .8 spindown. Started a MC session of about 1tb and went to bed. This AM all drives are in Standby properly. AT idle I am finally down below 50w on my Suoermicro 16bay JBOD.

 

Keep up the great work.

[[Plugin] Spin Down SAS Drives]

12 hours ago, doron said:

I've just pushed a new version - 0.8 - of the plugin, supporting 6.9.0-rc1 and its new spin up/down mechanisms.

As always, please report issues.

Looking forward to trying it out!

[[Plugin] Spin Down SAS Drives]

17 hours ago, doron said:

This is essentially what the plugin does when it tries to spin down SAS drives. So either this does nothing in your setup (combination of hard drive and controller), or something else is going on. 

Could it be that you have constant i/o against the array - in which case, a spun-down drive will immediately spin back up? Do you see i/o counters (read or write) on the main page moving, during that time?

So D, you got me digging deeper. I found on those drives IDLE_B=1, IDLE_C=1, and IDLE=1. So I changed those to zero.

These drives are already sleeping according to Unraid, Grey Ball. Checked with SDPARM they show no additional lines as before. When I issue the commands sg_start and mdcmd they both work when checked with sdparm, also the light goes out on the supermicro drive bay. With in a few minutes the drive spins back up  and the supermicro light comes back on. But they are still Grey Balled and sleeping in Unraid.

 

Maybe the Cache directory's is not working properly. I do not see any activity on the read /writes.

 

Thanks for at least getting me closer.

[Syslog Spam]

On 7/31/2020 at 4:10 PM, joshbgosh10592 said:

Those are my Proxmox nodes binding, which should be NFS. The nodes weren't happy I rebooted the NAS on them..

Did you ever find a answer to this? My proxmox is  causing the same log spamming. Sure seems like a Unraid issue vs a Proxmox issue.

[[Plugin] Spin Down SAS Drives]

On 12/5/2020 at 10:41 AM, doron said:

It's identical to pushing the "spin down" button (when the plugin is installed). If there's no massive i/o going on against it, sure.

Yes it's the same result.

[[Plugin] Spin Down SAS Drives]

17 hours ago, doron said:

 

(sorry for previous misfire, I was reading on a tiny phone)

 

Does this same drive react the same way to direct spindown? e.g.:

sg_start -r --pc=3 /dev/sdd

sdparm --command=sense /dev/sdd

 

is it safe to run that command while the array is in use?

[[Plugin] Spin Down SAS Drives]

16 hours ago, doron said:

@nlcjr, can you restart your rsyslog service, then spindown one drive just once, then read sense with sdparm?

 

e.g.:

/etc/rc.d/rc.rsyslogd restart

mdcmd spindown 2

(wait a couple of seconds, then...)

sdparm --command=sense /dev/sdd

 

Here are the results.

 

 

[[Plugin] Spin Down SAS Drives]

Sure,

 

I made some changes since I sent the forum post So hopefully the logs aren't to confusing.

 

When I had .6 installed I could see the drive standby also by the drive ready light going out. That no longer occurs.  Parity drives are set to never standby as they don't seem to work correctly being netapp drives. IE no grey ball and lots of logs trying over and over to spin down. 0 and 29 I think.

 

All others but cache are set to 1 hour. They do change to grey ball but no power savings via supermicro power consumption display. Drive ready light also stays lit on supermicro.

 

Thanks for your relentless pursuit to save watts!

 

syslog.txt

[[Plugin] Spin Down SAS Drives]

Doron,

 

Anyway to switch bay to version .6? That version seemed to work as long as no timers were set on my Segate Exos 7 drives. The new version seems to not spindown my drives anymore. I checked with the:  sdparm --command=sense /dev/sd[d-j]   to check all my drives and no additional lines are sensed.

 

Thanks in advance

[Private NFS share mounts without user/pass]

Ken-Ji

 

Thank you for this, I was struggling to mount "secure or private" nfs shares to my Proxmox storage group.

 

This worked perfectly.