What you guys are up to at this point is beyond me (!) - but I just thought I’d relay the odd behavoir of mine lately:
The good news. It DOES sleep. This is odd because I recently did a System reset on it (after some erratic behavoir) but I never re-issued the two commands that had been absolutely necessary before for it to get to sleep (i.e. the stop rsdk process & unmount/mount commands)
What’s also odd is that my user.log is much bigger than it’s ever been (9,489,219 bytes to be precise), is frozen in time since 12/14 and hasn’t changed in size by even a byte over the last three days of downloading it. Entries stopped several days ago so I cannot see precisely when it comes and goes into Standby - although it does seem to be for long periods because the case cools down and the led does the slow blink…
I’ve also done 3 seperate sizeable backups to it (about 400 Gb each, mixed files) and havent notice any excessive churning etc. in the aftermath.
Something’s still obviously wrong with it and it’s still a mystery to me as to why it’s now sleeping, but at this point my approach is to leave it alone and “let sleeping dogs lie”!
FYI Here are the last few entries in the log (there are dozens if not hundreds more just like those preceeding):
2017-12-14T23:29:25.960640-05:00 di=wHxsG70otX notice restsdk: paths.go:49: Could not dial crawler socket at ‘/tmp/WDMCRequest.socket’, error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2017-12-14T23:29:35.928742-05:00 di=wHxsG70otX notice restsdk: watch.go:109: Stat(), error: stat /tmp/dynamicconfig.ini: no such file or directory
2017-12-14T23:29:35.964375-05:00 di=wHxsG70otX notice restsdk: paths.go:49: Could not [LOG STOPS HERE!]
Don’t know if any of this helps or not, but, there it is…