Thank you for having a look @doron! It isn't consistent. It happened three times, then it went a couple of months without an occurrence, then it happened again on four drives at once. I switched to an LSI 9400-16i to rule out the HBA, and it did happen again a day later. Since that time, I just have them set to not spin down. 

17 hours ago, doron said:

@valiente, can you, after the device spins back up (ie after the SMART message), issue, again, only the last part of the command (the "sdparm -C sense /dev/sdi" part) and post the result?

Here is the result, ran it a couple of times before forcing spin-down, during and after:

root@brute:~# sdparm -C sense /dev/sdj
    /dev/sdj: SEAGATE   ST16000NM004J     E004
root@brute:~# sdparm -C sense /dev/sdj
    /dev/sdj: SEAGATE   ST16000NM004J     E004
root@brute:~# sdparm -C sense /dev/sdj
    /dev/sdj: SEAGATE   ST16000NM004J     E004
root@brute:~# sdparm -C sense /dev/sdj
    /dev/sdj: SEAGATE   ST16000NM004J     E004
Decode response as sense data:
Fixed format, current; Sense key: Not Ready
Additional sense: Logical unit not ready, notify (enable spinup) required
  Field replaceable unit code: 2
root@brute:~# sdparm -C sense /dev/sdj
    /dev/sdj: SEAGATE   ST16000NM004J     E004
root@brute:~# sdparm -C sense /dev/sdj
    /dev/sdj: SEAGATE   ST16000NM004J     E004
root@brute:~# sdparm -C sense /dev/sdj
    /dev/sdj: SEAGATE   ST16000NM004J     E004

 

 

Drive is still not down:
 

Quote

Oct 22 09:45:45 brute emhttpd: spinning down /dev/sdj
Oct 22 09:45:45 brute SAS Assist v2024.02.18: Spinning down device /dev/sdj
Oct 22 09:46:05 brute emhttpd: read SMART /dev/sdj

 

 

I was doing this with SDJ drive today as SDI was being used at the moment.

8 hours ago, rabidfibersquirrel said:

Thank you for having a look @doron! It isn't consistent. It happened three times, then it went a couple of months without an occurrence, then it happened again on four drives at once. I switched to an LSI 9400-16i to rule out the HBA, and it did happen again a day later. Since that time, I just have them set to not spin down. 

Yes, I should have been more precise with the question at the end. During the time it went without an occurrence, - do you know for a fact that these particular drives actually spun down, at any time, and subsequently woke up successfully? (looking at the diag you sent, your array seems quite busy, so the question might be not as far out as it seems).

49 minutes ago, valiente said:

I was doing this with SDJ drive today as SDI was being used at the moment.

Okay I think I see what's going on. Would you be open to test a bit of code for me, to see if it helps any? (standard disclaimer - this would be untested so expect the unexpected etc.). 

If you would, I'll send you the instructions privately.

47 minutes ago, doron said:

Okay I think I see what's going on. Would you be open to test a bit of code for me, to see if it helps any? (standard disclaimer - this would be untested so expect the unexpected etc.). 

If you would, I'll send you the instructions privately.

Yes please lets try it!

Hi,

I'm sorry to report, that the Plugin does nothing in following cofiguration:

 

Disks: 4 SAS Drives Seagate (ST6000NM0034 (6TB)

Controller: (LSi) Broadcom 9300-16i SATA/SAS 12GB in HBA Mode (16 Drives connected!)

Connected Drives to this Controller:

4 Seagate IronWolf 12TB SATA Drives (Vanilla Unraid installation spins down correctly)

4 Seagate ST6000NM0034 6TB SAS Drives

8 Kingston A400 1TB SSDs

 

Everything works fine, except the spindown of the SAS-Drives

14 hours ago, MadKetchup said:

Everything works fine, except the spindown of the SAS-Drives

Thanks for reporting. Indeed, people had mixed success with these Seagate drives.

Can you provide some more detail - do the SAS drives spin down and immediately back up? Not spinning down at all? How are you determining that they are not spinning down?

 

On 10/22/2024 at 4:13 AM, doron said:

Yes, I should have been more precise with the question at the end. During the time it went without an occurrence, - do you know for a fact that these particular drives actually spun down, at any time, and subsequently woke up successfully? (looking at the diag you sent, your array seems quite busy, so the question might be not as far out as it seems).

 

I can't say I'm fully confident that they did spin down. I think I remember seeing them spun down a few times, but it was a while back.

 

Thanks again for looking into it. 

Helo! Would this able to Spun down Unassigned Drives? Have a Issue where the plugin seems to works just find with drives in array but seems to failed to spun down a unassigned drive(At least the lights stays green on the UI)

 

I'm planning to use the unassigned drive as a backup just in case something died while I'm gone

Edited November 30, 20241 yr by LunarstarPony

14 hours ago, LunarstarPony said:

Helo! Would this able to Spun down Unassigned Drives? Have a Issue where the plugin seems to works just find with drives in array but seems to failed to spun down a unassigned drive(At least the lights stays green on the UI)

 

I'm planning to use the unassigned drive as a backup just in case something died while I'm gone

What hard drives do you have in your UD where you experience this?

Just chiming in to say thank you for this plugin  Using it to successfully spin-down a DS2426 with 24x 10k 900gb SAS drives in a ZFS pool. This pool should rarely need to be accessed, so it's great to save some power!

5 hours ago, doron said:

What hard drives do you have in your UD where you experience this?

It's the ST2000NM003A, tho I do have the exact same drive in the array which spin down just fine.

 

The only drive that failed to spin down is the one that's unassigned.

 

1 hour ago, LunarstarPony said:

It's the ST2000NM003A, tho I do have the exact same drive in the array which spin down just fine.

 

The only drive that failed to spin down is the one that's unassigned.

What do you see in the log when you try to spin it down? Do you get a "spinning down" message? Do you get any "SAS Assist" message?

2 hours ago, doron said:

What do you see in the log when you try to spin it down? Do you get a "spinning down" message? Do you get any "SAS Assist" message?

Dec  1 05:13:14 Lunar-UnRAID SAS Assist v2024.11.25: Spinning down device /dev/sdf
Dec  1 05:13:24 Lunar-UnRAID emhttpd: spinning down /dev/sdd
Dec  1 05:13:24 Lunar-UnRAID SAS Assist v2024.11.25: Spinning down device /dev/sdd
Dec  1 05:34:09 Lunar-UnRAID webGUI: Successful login user root from 192.168.214.152
Dec  1 05:36:44 Lunar-UnRAID emhttpd: spinning down /dev/sde
Dec  1 05:36:44 Lunar-UnRAID SAS Assist v2024.11.25: Spinning down device /dev/sde
Dec  1 05:36:52 Lunar-UnRAID emhttpd: read SMART /dev/sde

Here sde is the unassigned drives, sdd and sdf is 2 of the other drive that get shutoff automatically. seems to do a smart read a lil after.

Edited December 1, 20241 yr by LunarstarPony

14 minutes ago, LunarstarPony said:

Here sde is the unassigned drives, sdd and sdf is 2 of the other drive that get shutoff automatically

Like in other cases reported here, seems like something is spinning this drive back up right after it's being spun down. That could be code in UD (scanning?), in which I'm not too fluent. Will try to take a look later.

Couple of complement questions - just ruling out different angles:

- Do you have other, non SAS drives in your UD? If so, do they spin down properly and stay spun down?
- Do you perhaps have this drive mounted with a file system that's being used?

4 hours ago, doron said:

Like in other cases reported here, seems like something is spinning this drive back up right after it's being spun down. That could be code in UD (scanning?), in which I'm not too fluent. Will try to take a look later.

Couple of complement questions - just ruling out different angles:

- Do you have other, non SAS drives in your UD? If so, do they spin down properly and stay spun down?
- Do you perhaps have this drive mounted with a file system that's being used?

All the HDD drive in my system is SAS which all seems to spin down just fine beside the only one thats unassigned, as for mounted it shouldn't be, at least I never manual mount it.

 

Here's the diag attatched if required

lunar-unraid-diagnostics-20241201-2029.zip

Edited December 2, 20241 yr by LunarstarPony

@doron I will be expanding my array some more soon. I prefer to use SAS HDDs due to their affordability, and will be going 18TB or larger. Are there any plans to add more support for the Toshiba models, or is there another brand that simply spins down reliably with the plugin? 

 

I plan on making a donation regardless. The plugin has been great aside from the Toshiba business! Thanks for all you do! 

On 12/1/2024 at 3:32 PM, doron said:

Like in other cases reported here, seems like something is spinning this drive back up right after it's being spun down. That could be code in UD (scanning?), in which I'm not too fluent. Will try to take a look later.

Couple of complement questions - just ruling out different angles:

- Do you have other, non SAS drives in your UD? If so, do they spin down properly and stay spun down?
- Do you perhaps have this drive mounted with a file system that's being used?

So No idea about my problem I supposed?

 

On 12/4/2024 at 10:28 PM, rabidfibersquirrel said:

@doron I will be expanding my array some more soon. I prefer to use SAS HDDs due to their affordability, and will be going 18TB or larger. Are there any plans to add more support for the Toshiba models, or is there another brand that simply spins down reliably with the plugin? 

 

I plan on making a donation regardless. The plugin has been great aside from the Toshiba business! Thanks for all you do! 

Unfortunately adding extra support for specific drives is impractical. Unraid's kernel code architecture does not allow for issuing explicit spin-up instructions, which is what some of these drives seem to expect.

 

Re drives that "behave", my experience with HGST (aka WD) SAS drives, e.g. the HC5x0 series, has been flawless, with fully reliable spin down and up per Unraid and this plugin.

Edited December 8, 20241 yr by doron

On 12/5/2024 at 7:08 AM, LunarstarPony said:

So No idea about my problem I supposed?

I don't have more info as to what wakes your drives up, no. I tried to skim the UD code for obvious clues and came out empty. I still believe something does. If you want to pursue this further, my next suggestion would be that you start Unraid with no plugins except for this one, no dockers and no VMs, and see whether the problem persists. If it does not, add back plugins and containers one by one (or...) and isolate which of them needs to be focused on.

It's back to summer here and I was getting constant temp notifications for SAS drive that should be spun down, looking into it the drive letters had changed causing telegraf to persist waking them up again like last time.

 

Just a reminder for anyone with issues with this plugin it's because reading the smart data from the drive (like with telegraf) will spin it up again for sas drives. The only fix i've ever found is excluding them in the conf for telegraf.

15 hours ago, deanpelton said:

... causing telegraf to persist waking them up again like last time.

Thanks for reporting this.

Could you help with two more data points:

(a) What make/model are your SAS drives?

(b) When one of them is spun down, and before telegraf makes it spin up again (or when telegraf is disabled for a moment), can you share the output of:

sdparm -C sense /dev/sdX

replacing /dev/sdX with the device node of the spun-down SAS drive?

Does this plugin help with SAS3 expander backplane and not handling sleep correctly? i.e. I have had an issue when I put my server to sleep, when it comes out of sleep if throws up errors that it can't write to the file system correctly, this has resulted in drives getting the Red X beside the drive.
Thoughts?

On 1/15/2025 at 4:31 AM, crowdx42 said:

Does this plugin help with SAS3 expander backplane and not handling sleep correctly? i.e. I have had an issue when I put my server to sleep, when it comes out of sleep if throws up errors that it can't write to the file system correctly, this has resulted in drives getting the Red X beside the drive.
Thoughts?

Unrelated. 

If you want to put your server to some sleep mode, you may want to stop the array first.

On 3/30/2023 at 10:10 AM, doron said:

It turns out that the standby (aka "spin down") commands are interpreted differently by different SAS HDDs, unlike SATA drives. These commands are not well standardized. Some drives, after receiving this command, do spin down, but expect an explicit "spin up" command to start revolving again. This behavior is not compatible with Unraid, which expects a spun-down drive to spin back up automatically when the next I/O is directed at it. This translates to read or write errors (depending on the I/O that was underway); if it was a write, you'll get the drive red-x'ed, like you experienced.

This has been reported a lot with Seagate drives, and a bit less with Toshiba drives.

 

There's very little the plugin can do about it. I can add the MG06 to the exclusion list - which will mean that the plugin will simply avoid touching these drives. 

Towards that end can you share the output of:

 

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

 

 

Hello!

 

I recently purchased MG06 SAS drives and was trying figure out why the spin-down does not work.

So I found this old thread and read that this MG06 drives are not good for SAS spin-down as they expect a spin-up command but unRaid does not work like that.

 

I used to have MG06 SATA drives and I got read-errors rarely (resulting in drive X failed by unRaid), but apparently still enough that I eventually had a failed array with some lost data. Now I replaced all drives with MG06 SAS drives only to find out that the spin-down is disabled for those (I guess from reading thread from 2 years ago).

 

Has this problem been addressed after that?

 

Here is the output of my drives also:

sdd     | MG06SCA800AY  | 1000:0097:15d9:0808   |  n/a  | 
sde     | MG06SCA800AY  | 1000:0097:15d9:0808   |  n/a  | 
sdc     | MG06SCA800AY  | 1000:0097:15d9:0808   |  n/a  | 
sdg     | MG06SCA800AY  | 1000:0097:15d9:0808   |  n/a  | 
sdh     | MG06SCA800AY  | 1000:0097:15d9:0808   |  n/a  | 
sdi     | MG06SCA800AY  | 1000:0097:15d9:0808   |  n/a  |