Hi, just wondering...

 

I keep my server constantly plugged in (but switched off).  I have WOL on so that I can turn the server on from my laptop/squeezebox.  Does this use much power since presumably the network card is always monitoring for magic packets? 

 

Thanks, Matt.

I doubt it.  Any device that is plugged in will constantly pull 1 or 2 W.  If you get a Kill-A-Watt or similar you can test it for yourself.

I doubt it.  Any device that is plugged in will constantly pull 1 or 2 W.  If you get a Kill-A-Watt or similar you can test it for yourself.

 

I depends of your PSU too, and what ports are powered by the +5vsb line. Each device powered in standby will consume a little ammount of energy, and if the PSU is low efficient, it will consume even more.

To give you at least a sample value:

My server pulls 2.4 Watts when in S3 mode. Much less than online with drives spun down, but of course more, than when disconnected from the powersocket ;-)

While a little OT compared to the initial post, have any of you encountered data corruption problems using S3?  I think I read a post from Weebotech (maybe BubbaQ) where they made a comment that it's not such a good idea using standby on a raid system?? I'd like to because power costs just keep going through the roof, but things like this make me uncertain how to proceed.

While a little OT compared to the initial post, have any of you encountered data corruption problems using S3?  I think I read a post from Weebotech (maybe BubbaQ) where they made a comment that it's not such a good idea using standby on a raid system?? I'd like to because power costs just keep going through the roof, but things like this make me uncertain how to proceed.

 

The comment was not from me. I do not use S3 with my unRAID server.

I turn it off.

 

costs just keep going through the roof, but things like this make me uncertain how to proceed.

 

What I do with my XBMC in the stereo is let it turn off, but I set the bios to turn it on at 5:55am every day. This way I get up and it's up and running.

 

If I did not need my unRAID server on all the time, I would just put a cron job to shutdown every night  after 11pm if the server was inactive.

Then use the BIOS to turn it on around the time when I would be using it.

While a little OT compared to the initial post, have any of you encountered data corruption problems using S3?  I think I read a post from Weebotech (maybe BubbaQ) where they made a comment that it's not such a good idea using standby on a raid system?? I'd like to because power costs just keep going through the roof, but things like this make me uncertain how to proceed.

 

I think, that this problem is one of the major reasons, that Tom doesn't include S3 in stock product.

There is no general answer to your question, because proper function of S3 depends on many components - HW, BIOS with ACPI tables, drivers, etc. - so it would be sufficient to add a component to your system to break proper S3 capability.

I use S3 since over a year without problems - I never got corruptions - but I did a lot of testing on a testmachine without important data and changed some of the components to make it work (including the motherboard ...). I still get hardresets for the diskcontrollers after resume, but it seems, the kernel handles that just fine.

Result is storage availability "on demand" (unraid server gets started whenever a HTPC is started by WOL) while saving energy during the rest of the time.

 

Result is storage availability "on demand" (unraid server gets started whenever a HTPC is started by WOL) while saving energy during the rest of the time.

I have the same exact setup. Works like a charm.

The comment was not from me. I do not use S3 with my unRAID server.

I turn it off.

 

I turn mine off too, but WOL sounds nice. Not at the risk of corrupted data though.

 

Does your XBMC comment mean you turn your unRAID Server off with XBMC? If so, how?

 

Is there a post that explains a cron job for shutdown after a certain time if inactive?  That sound interesting.

 

Result is storage availability "on demand" (unraid server gets started whenever a HTPC is started by WOL) while saving energy during the rest of the time.

 

This sounds great.

 

I still get hardresets for the diskcontrollers after resume

Not so sure about this though. 

 

My server has been running very well for 3.5 years. Don't want to jinx it