problem: The WD Cloud would wake up at random intervals throughout the night. Some as short as 2 minutes, 6 minutes, 20 minutes and the longest sleep is 70 minutes. After rebooting the device with no jobs killed or restarted, the device managed to sleep for 2 hours and 12 minutes. I do not know why it woke up. (Static IP, all scan jobs off).
I can fully understand why a PC would wake up and defrag its drive once a week, or re-build an index for faster searches but that is the old days…
As more and more devices are capable of sleeping, I have become use to putting a device to sleep and they have remain sleeping; devices such as iPhone, iPad, laptops, etc.
Even my PC is set with the indexing service turned off as I don’t have any media files on my PC for it to index or search. Defrag is off since it is a SSD. Even the net waking the pc has been turned off. The only thing that wakes my PC is the keyboard, not even the mouse (as a bump on the desk would wake a sleeping pc).
Although the hard drive does spin down theWD Cloud doesn’t really sleep as the processor inside is constantly maintaining a vigil on everything; hence it is constantly warm to the touch. However once in awhile the hard drives spins up and everyone has been saying well, it is a small computer and such things like DHCP needs to refresh its IP, logs have to be written to the disk, etc. etc. etc…
I think one of the best quote that I have read on one of the posts in regards to the cloud taking days to scan all the media files has been “I bought a storage device and not a super computer calculating the value of pi”.
A storage device should not be waking up every hour, just like your TV doesn’t turn on every hour to scan its channels to ensure that it indexes shows for you to watch the next day? Nor does your phone spend time defragging memory or use GPS to ensure that you haven’t wandered away from your house while it is sleeping?
If any device does wake up, it should be more discreet!
Just because it is a mini linux computer that has a cron (job scheduler) and multitasking doesn’t mean it should be designed that way. When my cloud drive sleep, it should sleep for weeks/months or even years sipping power or even suspended like a person on cryogenics; dreamless. There should be NO daily/weekly/monthly jobs unless it is user specified. If the process is needed, such as the scanning process to build photo images and other functions for DLNA, these scans must be a user controllable function.
Move items like the time update so it is done when the user wakes up the device and not a cron job that wakes the storage device up in the middle of the night. Can you imagine your smart tv turning on just because NTPD needs to run. Perhaps the smart tv does, but at least it isn’t turning on the TV to do so and just the same with the storage device that the drive should remain sleeping … until the user accesses it.
All log transfers even though they should be kepted in case of a power failure should not wake up the drive everyday just to write the logs. Either include a small SD card to keep the logs or don’t write to disk until the user wakes up the device.
This is just common sense and I’m so glad you don’t write the OS for my car as I cannot imagine my car starting up every half hour just to warm up because it is cold
"this is a storage dev