There is quite a few posts on this subject, but I want to bring it up again, because it is affecting me and people might have more to add.
Why am I bringing this up?
Because I want the sleep function to work as it should, I did spend 150 bucks on each of these units.
(I have 3)
So I have 3 units, all connected to the same switch.
And they are set up essentially the same way.
1. 1x WD10EADS-00L5B1
2. 1x WD10EADS-00L5B1
3. 2x WD10EADS-00L5B1 (RAID)
Guess which one is the only one the works with sleep mode correctly?
If you guessed the one in a raid configuration you win... but I have no idea why.
Just to cover the bases:
No other services are running, no ftp, daap, ect. Nothing.
They are all in the same workgroup, all dhcp from my router.
The NON raid units do enter sleep, but they wake on their own every hour.
Even if I pull the network cable, they do this. Pretty bizarre.
But the unit with the raid array works fine, goes to sleep after 20 minutes, and stays asleep
until it's accessed. The other 2 are waking up about every hour or so.
It's weird.
UPDATE:
Just in case there is somebody else who cares about this issue, I have something interesting to report.
While working on my editing, I decided to try a few things at random to one of my single drive 323s to
see if I could get it to stay in stand by:
Results:
One of my boxes has stopped waking up every hour.
I moved the drive to left slot, and deleted a user called ftp. (The FTP service was never running)
As far as I know those are the only changes I've made.
It is currently off and staying off, where the other one still wakes up at 2 minutes past the hour.
I'll keep you posted.
2nd UPDATE:
OK, it's confirmed if you have a single drive setup with this problem, the solution is to keep the single
drive in the left slot (Slot #2 in gui). My units now enters sleep, and stays without issue.
They only spin up when required, and go back to sleep after the counter tells them too.
I can run FTP, whatever service and they seem to cooperate.
Hope this helps someone else.