Titles says it all.  Ever since I went to the latest beta this SSD drive no longer "spins down."  I did not try beta 14 or 14a, I went right from 12 to 14b.

 

I have twelve other Western digital drives in the array including parity and cache.

5x WD40EZRX

6x WD30EZRX

1x WD5002ABYS

 

The WD5002ABYS is the cache drive.  The Patriot Pyro SSD is actually part of the main array.  It's used to store metadata that needs to be accessed quickly.  The Patriot Pyro contains a folder that is part of a user share that spans all drives in the array (user share = "media").

 

All drives are in reiserfs still.

 

If I click "spin down" on the "main" page the drive will not spin down there either.  The page just continues to try and load until I navigate away from the main page and back again.  When I go back to main the drive is still spun up.

 

Plugins include:

Dynamix Cache Directories 2015.02.14

Powerdown Package (2.13) 2015.02.22

 

Let me know if you need any other information.

 

craigr

I am confused - why would you want to spin down a SSD anyway since it has no moving parts anyway?

Just read first post sticky and have removed my plugins.  I've rebooted and will see what happens after the spin down time of 45 minutes.

 

craigr

I am confused - why would you want to spin down a SSD anyway since it has no moving parts anyway?

For me this does not seem like a big problem.  I am just reporting a new "bug" that's cropped up since the last beta.  This may impact other drives and users.

 

That said, the drive does use less power when "spun" down and the temperature of the drive goes down when "spun" down.  Even when the drive is in "spun" down state, it "spins" up very quickly and there is virtually no delay.

 

So I guess I must ask, why wouldn't I want the drive to "spin" down

 

craigr

Well, with plugins removed, on the Main page,  clicking "Spin Down" still does not "spin" down the Patriot Pyro SSD drive.

 

I'll let the spin down time pass and report back then.

 

Thanks,

 

craigr

All plugins removed.  The drive still does not spin down.

 

craigr

I'm pretty sure this is expected behavior from SSDs.

 

If there is a defect it would be that 6b12 showed SSDs as spun down.

I'm pretty sure this is expected behavior from SSDs.

 

If there is a defect it would be that 6b12 showed SSDs as spun down.

All previous versions of unRAID showed spun down.  Also version 5.x showed spin down.

 

craigr

Clearly you did not read the release note before you upgraded:

 

Version 6.0-beta14b

 

    Fix device spinning status.

    Fix SSD's appearing "spun-down".

    Fix inability to disable Docker once enabled.

    Release notes appear now via info icon on Plugins page

 

To be fair that message could quite easily mean "Disks appearing spun down when they are not".

 

Obviously SSD never spin down since they never actually spin but what has never been clear is if they can go into a power state lower than idle. Whether this power state actually consumes less electricity is irrelevant.

SSDs dont spin down, so we changed the gui to never show them as such. This is expected behavior and not a bug.

I am still not convinced that you cant put them into a sleep/state as pre 14b there was a noticeable delay if they were "spun down" before you could access them. Regardless the obvious confusion now is the GUI allows you to set them to spin down (which is not a viable config option any more) and the icon for a spun up disk and SSD is the same i.e if you hover there is an icon showing spun down is a possible SSD state which it no longer is.

 

I would suggest something like changing SSD to no or greyed out spin down settings, a new color icon to signify SSD and some pop up help.

 

Minutia maybe buy we should capture it as a QA fix for later down road map as it is needlessly confusing as is.

This seems to be a semantic problem forcing a change in functionality that doesn't need to happen. In the past, unRAID has translated the STANDBY power mode to be "spun down". SSDs also have a STANDBY power mode but the "spun down" translation doesn't make sense. Why disable the STANDBY power mode for SSDs when you can just change some labels and keep the same functionality?

Huh.  Please provide a link to an SSD that has a standby mode.

Huh.  Please provide a link to an SSD that has a standby mode.

 

http://www.storagereview.com/patriot_pyro_se_review_240gb

 

Patriot Pyro SE 240GB Specifications

 

60GB, 120GB, & 240GB capacities

SandForce SF-2281 SSD processor

SATA 6.0 Gbps interface

Up to 550MB/s sequential read speeds

Up to 520MB/s sequential write speeds

Maximum 4K random write: 85,000 IOPS

TRIM Support

Power Consumption: Operational <5W Standby <.1W

O/S Support: Windows® XP / Vista / 7 / Mac® OS / Linux

3-year warranty

 

When my Patriot Pyro was "spun down" in earlier versions of unRAID the disc would stop reporting temperature.  When it woke up temperatures would again report and would get warmer while the disc reached steady state temp again after coming out of "stand by."  Also, when the disc was in "spun down" standby mode, it would take about a half second to wake up before I could access data on the disc.

 

Also, in the unRAID "main" page, with 14b, if I click the "spin down" button now, the browser tries to reload for an eternity.

 

Honestly guys I am just reporting a problem all be it a minor one.  From most of the replies to my thread it seems that I should have just shut up and ignored it.  I am trying to help with the beta program by reporting as one should with beta software.  If the community does not want to hear about my findings from now on I will just keep my mouth shut.

 

Regards,

craigr

Clearly you did not read the release note before you upgraded:

 

Version 6.0-beta14b

 

    Fix device spinning status.

    Fix SSD's appearing "spun-down".

    Fix inability to disable Docker once enabled.

    Release notes appear now via info icon on Plugins page

Clearly you are correct, I did not read them otherwise I would have sited them in my post.  That said, my SSD was going into standby before and now it isn't anymore.  Whether you want to call this "spun down" or standby is silly and a question of semantics.  Before 14b unRaid supported SSD standby and now it doesn't.  I liked it better when my SSD standby was supported in earlier versions of unRAID.  I try and have my server use the least amount of electricity as possible when it is not in use.  With 14b I am using 5 watts more 24/7.  With SSD cache pools and other SSD drives coming into use with version 6 these power draws will add up.  If I have five SSD drives in my box I'll be using 25 more watts 24/7.  This will add up to a large amount of power use once you consider all unRAID users.

 

Whatever,

craigr

I am still not convinced that you cant put them into a sleep/state as pre 14b there was a noticeable delay if they were "spun down" before you could access them. Regardless the obvious confusion now is the GUI allows you to set them to spin down (which is not a viable config option any more) and the icon for a spun up disk and SSD is the same i.e if you hover there is an icon showing spun down is a possible SSD state which it no longer is.

 

I would suggest something like changing SSD to no or greyed out spin down settings, a new color icon to signify SSD and some pop up help.

 

Minutia maybe buy we should capture it as a QA fix for later down road map as it is needlessly confusing as is.

Thank you, exactly.

 

Although frankly, having the SSD just say "spun down" was not a big deal to me, nor was it confusing.  I (as I am sure others) just took "spun down" to mean "standby" because it's an SSD drive and obviously nothing is spinning in the first place.  So for me spun down has always been synonymous with standby for SSD in unRAID.

 

As poster NAS points out this may be minutia, but this is beta software and we are supposed to point out bugs and odd behavior right?  I agree with NAS, what would be best would be for the GUI to say "standby" for SSD instead of "spin down."  It would be nice to at least have the capability to put the SSD into standby again no matter what you call it.  Furthermore, as it stands now, there is still the option to "spin down" the SSD in the GUI and now the disc's can't even get to the spun down / standby state anymore.  It's odd to have this option in the GUI that has no impact on what the drive is doing or reporting.

 

craigr

SSDs dont spin down, so we changed the gui to never show them as such. This is expected behavior and not a bug.

I would like it if you could please restore standby for SSD drives in unRAID.  That is my suggestion.

 

Thank you,

craigr

This seems to be a semantic problem forcing a change in functionality that doesn't need to happen. In the past, unRAID has translated the STANDBY power mode to be "spun down". SSDs also have a STANDBY power mode but the "spun down" translation doesn't make sense. Why disable the STANDBY power mode for SSDs when you can just change some labels and keep the same functionality?

I agree.  This would really be the best option if it's not too difficult to make these changes in the GUI just for SSD.  If it is difficult to make these semantic changes than I really would like for "spin down" to be resotred for SSD drives.

 

Best regards,

craigr

SSDs dont spin down, so we changed the gui to never show them as such. This is expected behavior and not a bug.

I would like it if you could please restore standby for SSD drives in unRAID.  That is my suggestion.

 

Thank you,

craigr

Craigr, please don't take offense to some of the other posts in this thread. Some folks are just really quick to jump on things and your post was well-intentioned, I can tell.  We really do want ALL feedback like this because while we put things in the announcement thread, we really want to hear the "gut instinct response" to things we do and feedback on things we could do better.

 

I wasn't aware of this (power standby for SSDs) and that's why I forwarded this thread to Tom for his input.  We will look into this further. Thank you for contributing your feedback and please continue to do so.

Yeah, "what JonP said".  I had received some email asking "Why are you spinning down an SSD, is that a bug?"  I was just fixing what I thought was a bug because I've never heard of an SSD that goes into standby mode, but it does make sense.  Thank you for the feedback and we'll see about getting the functionality restored and maybe change some terminology.

I like the idea of using the term "standby" more in relation to disks. In fact we should give some thoughts to using smartctl terminology of IDLE, STANDBY and SLEEP more often.

Thanks guys.

 

Sorry for being grouchy yesterday too.  I read and posted early yesterday morning before coffee and while my 8 month old was having a melt down.

 

Best regards,

craigr

My understanding about the "standby mode" stats for SSD is the consumption when the PC/Server goes into StandBy mode and it's not a state that can be triggered while the PC is operating. But happy to be corrected if I've misunderstood.

The problem is google is failing with definitive answers.

 

What can be said is if you tell a SSD to "spin down" it accepts the command and then to access it there is a perceived delay as it "spins up". Presumably thats coming in and out of standy but its anecdotal at best.