Newly-built server running 4.3.1.  Currently just three disks as shown below (would be glad to provide the rest of my HW config if needed).  Just setting up user shares now and there's basically nothing on any of the disks.

 

parity WDC WD10EACS-00Z  (1TB)

disk1 WDC WD10EACS-00D  (1TB)

disk2 ST3750640AS    (750GB)

 

If all three disks are spun down, when I hit the Spin Up button only the first two disks will spin up.  I did a search and I see there is a staggered spin up routine but even after many minutes the third disk will still show spun down when I do a refresh.  If I hit Spin Up a second time then the third disk will finally show that it has spun up.  Just trying to understand what's going on.

 

Thanks,

 

Bruce...

 

Only way to help you is to know more of what the system is doing.

 

Please post a syslog.  Instructions here: http://lime-technology.com/wiki/index.php?title=Troubleshooting

 

Joe L.

Sure, here it is.  Sorry I didn't attach it at first.

 

Your syslog looks good.

 

I have had the same problem, for a long time.  It's not an unRAID issue, it's a hard drive and/or disk controller issue.  About 98% of the time, I have to do at least 2 Spin Up's, to get all of the drives to spin up.  About 10 - 30% of the time, I have to do a third Spin Up to finally wake up one of my drives.  Some drives just seem to be heavy sleepers.

 

Tom has experimented with different methods of 'waking up' the drives, and the current one works better than his first one, but I suspect a little more experimentation could find a better call to the drive, to enforce 100% wake up on the first call.  WeeboTech has created a Spincontrol script (here) that uses a different method (I think).  I haven't tried it yet, but I would be interested in seeing if it works better.

 

Added to FAQ (link back only), here.  Feel free to add, edit, or expand.

Ok stupid q: who cares?

 

I mean, ok what if not all drives spin up? They do spin up when you try to use them right?

OK, the delay. That delay is just for the first access and after all, if you leave the drives unused for some time they'll spin down and they'd have to spin back up when you use them again anyway.

 

Not spinning down (ever) I get it, is a problem. Not spinning up (but still usable), I don't see it as a problem.

 

 

Your syslog looks good.  I have had the same problem, for a long time.  It's not an unRAID issue, it's a hard drive and/or disk controller issue.  About 98% of the time, I have to do at least 2 Spin Up's, to get all of the drives to spin up.  About 10 - 30% of the time, I have to do a third Spin Up to finally wake up one of my drives.  Some drives just seem to be heavy sleepers.

 

Thanks, Rob.  Just wanted to make sure I wasn't the only one.

 

Bruce...

 

Ok stupid q: who cares?

 

Well, I suppose some of us still look for Vulcan kin in our ancestry, and like logical explanations for the universe.  Anomalies and inconsistent behavior grab our attention, and require our understanding.  I do realize that that in itself often becomes an illogical waste of time.  I sometime envy others that have little problem with inconsistencies, and maintain attention on the more important questions of life.  Believe it or not, I still find myself trying to logically understand the female mind!

 

The fact that a computer is issuing a command to another computer (the firmware on the hard drive), and it is resulting in inconsistent behavior, does not make sense.  I'm sure there is a good reason, but we do not understand it yet.  And that will always bother some of us, while realizing that in this instance it is inconsequential.

Well that explains it (more or less).

 

In my first years in computing, one of the things that attracted me, was that computers have "yes" or "no". That's it. A yes or a no. A white or a black. A Yin or a Yang. A 1 or a 0. This simple fact made the whole system work.

You press something, you get a result based exactly on the procedure that is triggered by what you pressed.

Maybe my brain was (erm is) as simplistic probably.

 

Then (somewhere when 8 bits came to be obsolete and 16 bits started not being enough - still wonder why) and largely after MS Windows started being something more or less common (although is not to blame here), "Maybe" was introduced in Computer Science.

 

The rest is history.

Today your computer could simply not work the same as it did yesterday. What did you do really? Nothing. Is there a reason? Most definitely yes. Is it practically worthwhile to find it? Not always. There are nowadays a few thousand little "triggers" that effect how things work in a computer (even a "clean non-MS" one), that Chaos Theory should definitely be introduced as a course in any CS major.

 

Sorry for the off topic rambling.

 

 

Do I hear Bobby McFerrin whistling?

 

 

Bill

oook ok

 

 

I also have the issue.

I have two boxes running... 1 old with 12 PATA drives, 1 new with 6 SATA drives and a SATA Cache drive.... all ARRAY drives respond correctly to spinup and spindown, the Cache drive does not respond, which I assume is by design...