Surprisingly, The WD My Cloud Uses More Power When It Is Shutdown Than When It Sleeps

I’ve only had the My Cloud for about two weeks and I connected it to a Kill-A-Watt to see how much power it used.  Prior to the mistake of updating the firmware from V03.03.01-156 to V03.03.01-165 last night, the My Cloud Sleep function seemed to work ok.  The Kill-A-Watt reported 4 watts when sleeping and 8 watts when “playing” .flac files.  When I was loading the .flac files it used about 10 watts.

Since the sleep function no longer works, last night when I was through using it I shut it down from the Dashboard and it seemed to shut down normally as the front panel light went off after a little while.  Much to my surprise when I looked at the Kill-A-Watt it was reporting 5 watts after the shutdown had completed and was still reading the same this morning - One watt more than when it used to sleep!  Thinking that it might be a problem with the power supply and since the unit was shut down I pulled the power connector out of the back of the My Cloud and the Kill-A-Watt reading went to 0 (zero).  That is really sad when the Shudown state uses more power than the Sleep state.  My Synology DS410 only uses 1 watt when it is sleeping and waiting for a potential Wake-On-LAN request.

Other miscellaneous information:

  1. I am not accessing the Internet, only my local LAN.

  2. Sleep is turned On.

  3. I enabled SSH and FTP but so far have not tried to use it for anything.

  4. Currently I am only using this as the DLNA server for my .flac files to my 2 WD TV SMPs and to share mostly text type files bewteen my main XP system, my W7 notebook, and my 2 Raspberry Pi computers.

  5. I’m using my Retrospect Professional Backup software to back up any critical files on the My Cloud to my XP system.

Hopefully I provided enough information so this sleep and shutdown power issue can be resolved.

1 Like

Hello,

That’s normal. Any product will use more power to boot from when you power it off  than when it wakes up from sleep mode.

Hello Nico12345/NETKID,

Is this problem still there?