STILL NOT SLEEPING! - and I GIVE UP!


#21

Sorry if this is long (!)

Bennor. It looks like we’ve been up to the same thing!

Like you, my MC hardly ever slept. But thanks to you and others - especially RAC8006, I’ve made some progress.

I had tried the “easy” stuff which got me nowhere - or didn’t make much of a difference i.e. turning off iTunes server, Twonky, DLNA, NTP, even all the shares that I could. I unplugged my Roku boxes etc. While some of those may have been contributing or could have prevented sleep by themselves, there were other factors at play that weren’t so easy to track down or adjust through the Dashboard. (Note that I wasn’t actually using the MC for any real “work” or backing up new files etc to it. I was (am!) in pure “troubleshooting” mode - so there should have been no thumbnail processing etc. going on to “cloud” the issue…)

(Side note: With NTP off this drive is a TERRIBLE time keeper. It loses about 1 min per day!)

To anyone attempting to wade through this for the first time you’ll need:

  • To know how to download your system logs (Dashboard/Help/Support/Create and Save system report. Then look in the “log” folder for “user.log” and “daemon.log”. Open them with a basic text editor like Notepad.)
  • Possibly your home router admin password.
  • To use SSH to type a few commands to your MC (“Putty” for the PC)
  • To remember that the drive takes 10 mins to get to “sleep”.
  • Patience!

Here’s what made the biggest differences for me/were the biggest culprits.

  1. Non-static IP address.
    I saw in the (DAEMON) logs that the IP lease issued by my router was only between 1353 and 1780 SECONDS. That’s only roughly 22-29 minutes (look for “REQUEST” and “ACK” entries). Also, I read on MicroSoft technet that: “By default, DHCP clients try to renew their lease when 50 percent of the lease time has expired”. Assuming that that could apply to the MC, that could mean (in my case) only 11-15 mins!

(My router is provided by the cable company and I never changed any of the default settings etc. and I’d guess that’s the same for a lot of people, however I can still get in and “manage” it to some degree through their interface. Note that once in I didn’t find a setting for “Static IP”. Instead the router let me “Reserve” an IP address for any particular device on the network - while maintaining Dynamic addressing for others. It amounts to the same thing, just different terminology for anyone with a similar setup)

Result - PART Success! The MC actually started to sleep for short periods after the IP setup change.

  1. “No such file” errors.
    Despite the static IP change the MC was still wakening sporadically. I saw that the log was full of “/tmp/dynamicconfig.ini: no such file” errors. I first tried turning ON Cloud sharing (per advice elsewhere on the forum) as I was apprehensive about SSH, messing around with linux commands, stopping processes etc.

That definitely helped, however this was around the time the firmware update came out promising to address sleep issues so I jumped at that, but in the process ended up having to do a “Quick” reset. (This was when I got all the “Connection Refused” errors that I outlined above on 11/29). After that, turning Cloud Sharing on didn’t work anymore insofar as suppressing the “no such file” errors went and I saw that the log was again full of them - and I mean full, there were HUNDREDS all just a few seconds apart.

(and no, the firmware update didn’t do anything that I could see that helped)

At this point I took RAC’s advice and issued the following 2 commands through SSH (using "Putty):
“/etc/rc2.d/S20restsdk-serverd stop”
“mount -o remount,noatime,nodiratime /dev/root /”

It was ONLY at this point that the MC started to get some SIGNIFICANT sleep. As in up to almost 7 hours.

THANK YOU RAC8006!
(and when I get enough nerve I’ll add them to the startup file that you had mentioned in several other posts - although did I read somewhere that this may no longer work since the firmware update?)

  1. Wakened by external devices:
    The above commands helped tremendously but there were still seemingly “random” wake ups. With nothing else “on” on my network and as the MC slept, I tried wakening and sleeping (from both “Sleep” and “Hibernate”) my PC laptop numerous times to see what affect it might have had on the MC.

From what I can see so far (and I’m not 100% convinced yet) “Network Discovery” on the PC must be ON to awake the MC [EDIT: -I’ve since discovered that it doesn’t matter which state ND is in] - BUT!! It does NOT wake it every time. I’m guessing there might be some “time out” involved where the PC will only try wake up the MC (via a “WOL” (Wake On Lan) packet?) when it want’s to verify that the MC is actually still at the last place it found it on the network. So far - and I still have some testing to go, it looks like this might be after 3 hours - but I may be barking up a wrong tree here and am open to correction… If anyone knows when or how often a PC looks to refresh or re-verify what was in its Network Discovery list, please chime in!

(With Network Discovery OFF the PC doesn’t seem to wake the MC - but more experimentation is needed to be sure…)

I also found that an iMac I had woke it - but haven’t experimented to the same extent as with the PC. One thing to remember about a Mac (well my one anyway) is that if an MC share is mounted and the iMac goes to “sleep” that the Mac may not be in as deep a sleep as you assume and it may be keeping that Share active. I had to shut down my iMac fully before it “let go” of the MC.

(I’ve also tried messing around with a utility (“wol sniffer” by Depicus) that monitors a subnet for wake up packets etc. addressed to the MC. but it’s not an area I’m knowledgable in and I’ve not had much success - I don’t know much about which ports to monitor etc.)

  1. firmware update check:
    As mentioned by others already, this happens around 3am and there’s nothing you can (easily) do about it. My log shows about 12 mins of various activities beginning at around 2:49am that I assume are associated with this.

  2. “Rotated atop”
    I don’t know what this is (some sort of log maintenance?) but it happens every 8 hours at about Midnight, 8am and 4pm. As much as I’d like to reduce this to once a day, I don’t think there’s much can (easily) by done about this either…

  3. Unknown (as yet) items:
    If you look at my log extract below you’ll see unexplained wake ups outside of the Firmware and Atop wakeups (although the midnight atop has something questionable at about 30mins past midnight - not sure if this is truly “atop” related or not…). These are what I’d like to find out more about…

[A] (1:17am)
[B] (3:20 - 4:20 aprx)
[C] (9:01am)
Any ideas?

To Conclude:
Although I’m still not done troubleshooting there has been much improvement and I’m down to just the few items above. This is the best sleep it ever got - and possibly as good as it ever will get…

Once I’m more confident in my findings I’ll turn back on each of the options I had turned off to try troubleshot this (NTP, MyCLoud, TimeMachine, Twonky, etc. etc.) one by one and try them in various configurations to see what effect they have…

The annoying thing here is that most of these issues are mentioned around these forums in various places already - so solutions (or at least definitive reasons) for a MC not sleeping CAN be identified.

It’s just a pity that WD can’t come up a utility or WD Dashboard component to check, monitor and/or report on some of these common wake sources - maybe by logging incoming WOL packets, listing scheduled “maintenance” job (cron?) times or analysing log entries for known errors like “no such file”.

Without that most people with this problem will be left with the trial and error approach that people like myself, RAC, Bennor and others have labored through…

Anyway, my log is below (w some text stripped out) now - as you can see, a BIG improvement. If anyone knows what those extraneous wakeups are (labelled A, B, C), let me know…


[atop activity - midnight]
2017-12-01T00:01:10.949357: exit standby after 12048 (since 2017-11-30 20:40:22.043437002 -0500)
2017-12-01T00:01:20.965637: Rotated atop, atop_size=2750655 atop_upload_size=2204

2017-12-01T00:30:11.981521: exit standby after 1129 (since 2017-12-01 00:11:22.133437002 -0500)
2017-12-01T00:42:33.463108: exit standby after 7 (since 2017-12-01 00:42:26.213437002 -0500)

[A???]
2017-12-01T01:17:11.345943: exit standby after 1467 (since 2017-12-01 00:52:44.443437002 -0500)

[start of 3 am firmware check?]
2017-12-01T02:48:10.957296: exit standby after 4848 (since 2017-12-01 01:27:22.213437002 -0500)
2017-12-01T02:49:30.323518: { “msgid”:“dataSize”, “mountPoint”:"/", “capacityK”:1968336, “totalK”:673020, “partition”:“rootfs” }
2017-12-01T02:49:30.351740: { “msgid”:“dataSize”, “mountPoint”:"/", “capacityK”:1968336, “totalK”:673020, “partition”:"/dev/root" }
2017-12-01T02:49:30.379899: { “msgid”:“dataSize”, “mountPoint”:"/run", “capacityK”:40960, “totalK”:3968, “partition”:“tmpfs” }
2017-12-01T02:49:30.408015: { “msgid”:“dataSize”, “mountPoint”:"/run/lock", “capacityK”:40960, “totalK”:64, “partition”:“tmpfs” }
2017-12-01T02:49:30.564183: { “msgid”:“dataSize”, “mountPoint”:“5a500f0368bd01ae8dc965a89133d5b3”, “capacityK”:10240, “totalK”:0, “partition”:“tmpfs” }
2017-12-01T02:49:30.592465: { “msgid”:“dataSize”, “mountPoint”:"/run/shm", “capacityK”:5120, “totalK”:0, “partition”:“tmpfs” }
2017-12-01T02:49:30.620859: { “msgid”:“dataSize”, “mountPoint”:"/tmp", “capacityK”:102400, “totalK”:9280, “partition”:“tmpfs” }
2017-12-01T02:49:30.657094: { “msgid”:“dataSize”, “mountPoint”:"/var/log", “capacityK”:40960, “totalK”:8128, “partition”:“ramlog-tmpfs” }
2017-12-01T02:49:30.684921: { “msgid”:“dataSize”, “mountPoint”:"/DataVolume", “capacityK”:5809669936, “totalK”:1230345780, “partition”:"/dev/sda4" }
2017-12-01T02:49:30.827411: { “msgid”:“dataSize”, “mountPoint”:“4940db6e1da83a57bf143cf9700c7e43”, “capacityK”:1024, “totalK”:0, “partition”:“tmpfs” }
2017-12-01T02:49:30.885687: { “msgid”:“inodeUsage”, “filesystem”:“rootfs”, “inode”:125184, “iused”:25160, “mountPoint”:"/" }
2017-12-01T02:49:30.914247: { “msgid”:“inodeUsage”, “filesystem”:"/dev/root", “inode”:125184, “iused”:25160, “mountPoint”:"/" }
2017-12-01T02:49:30.942358: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:230, “mountPoint”:"/run" }
2017-12-01T02:49:30.970687: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:5, “mountPoint”:"/run/lock" }
2017-12-01T02:49:31.055501: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:156, “mountPoint”:“5a500f0368bd01ae8dc965a89133d5b3” }
2017-12-01T02:49:31.083835: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:2, “mountPoint”:"/run/shm" }
2017-12-01T02:49:31.112179: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:20480, “iused”:75, “mountPoint”:"/tmp" }
2017-12-01T02:49:31.148985: { “msgid”:“inodeUsage”, “filesystem”:“ramlog-tmpfs”, “inode”:1815, “iused”:118, “mountPoint”:"/var/log" }
2017-12-01T02:49:31.177349: { “msgid”:“inodeUsage”, “filesystem”:"/dev/sda4", “inode”:182996992, “iused”:233904, “mountPoint”:"/DataVolume" }
2017-12-01T02:49:31.321662: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:5, “mountPoint”:“4940db6e1da83a57bf143cf9700c7e43” }
2017-12-01T02:49:37.390893: { “msgid”:“usageSize”, “totalB”:1286258004542, “photos”:795366851, “video”:139292964049, “music”:2245445301, “other”:1143924228341 }
2017-12-01T03:01:01.888073: deviceInfoCollect: dryrun=0, system=0, configuration=1
2017-12-01T03:01:05.268324-05:00 di=wHxsG70otX notice deviceInfoCollect: { “msgid”:“configuration”, “ftp_enabled”:0, “volume_encryption_enabled”:0, “dlna_enabled”:0, “cloud_access_config”:“disabled”, “drive_standby_enabled”:1, “language”:“DEFAULT”, “RAID_mode”:“na”, “time_machine_enabled”:0, “network_config”:“static”, “auto_update_enabled”:0, “iTunes_enabled”:0, “ssh_enabled”:1 }
2017-12-01T03:05:02.617659: disable lazy init
2017-12-01T03:09:57.628011-05:00 di=wHxsG70otX notice getNewFirmwareUpgrade.sh: begin script: immediate send_alert auto
2017-12-01T03:09:57.668814-05:00 di=wHxsG70otX notice getNewFirmwareUpgrade.sh: http://support.wdc.com/nas/list.asp?devtype=sq&devfw=04.05.00-320&devlang=eng&devsn=&auto=0&devid=*****

[B???]
2017-12-01T03:20:54.998493: exit standby after 7 (since 2017-12-01 03:20:47.683437002 -0500)
2017-12-01T04:17:11.017009: exit standby after 2764 (since 2017-12-01 03:31:06.103437002 -0500)

[atop activity -8am]
2017-12-01T08:01:11.359415: exit standby after 12829 (since 2017-12-01 04:27:22.153437002 -0500)
2017-12-01T08:01:21.526439: Rotated atop, atop_size=2979354 atop_upload_size=1634

[C???]
2017-12-01T09:01:33.143038: exit standby after 3011 (since 2017-12-01 08:11:22.593437002 -0500)

[atop activity - 4pm]
2017-12-01T16:01:11.706639: Rotated atop, atop_size=4072310 atop_upload_size=590

[atop activity - midnight]
2017-12-02T00:01:11.251488: exit standby after 20029 (since 2017-12-01 18:27:22.253437002 -0500)
2017-12-02T00:01:21.619976: Rotated atop, atop_size=6785192 atop_upload_size=6222

2017-12-02T00:30:12.082084: exit standby after 1129 (since 2017-12-02 00:11:22.523437002 -0500)
2017-12-02T00:42:33.221191: exit standby after 7 (since 2017-12-02 00:42:25.963437002 -0500)

2017-12-02T01:01:34.186403: exit standby after 530 (since 2017-12-02 00:52:44.103437002 -0500)

[start of 3 am firmware check?]
2017-12-02T02:48:10.982622: exit standby after 5785 (since 2017-12-02 01:11:45.063437002 -0500)
2017-12-02T02:49:30.350007: { “msgid”:“dataSize”, “mountPoint”:"/", “capacityK”:1968336, “totalK”:664496, “partition”:“rootfs” }
2017-12-02T02:49:30.378812: { “msgid”:“dataSize”, “mountPoint”:"/", “capacityK”:1968336, “totalK”:664496, “partition”:"/dev/root" }
2017-12-02T02:49:30.407008: { “msgid”:“dataSize”, “mountPoint”:"/run", “capacityK”:40960, “totalK”:3904, “partition”:“tmpfs” }
2017-12-02T02:49:30.435561: { “msgid”:“dataSize”, “mountPoint”:"/run/lock", “capacityK”:40960, “totalK”:64, “partition”:“tmpfs” }
2017-12-02T02:49:30.617210: { “msgid”:“dataSize”, “mountPoint”:“5a500f0368bd01ae8dc965a89133d5b3”, “capacityK”:10240, “totalK”:0, “partition”:“tmpfs” }
2017-12-02T02:49:30.645378: { “msgid”:“dataSize”, “mountPoint”:"/run/shm", “capacityK”:5120, “totalK”:0, “partition”:“tmpfs” }
2017-12-02T02:49:30.674081: { “msgid”:“dataSize”, “mountPoint”:"/tmp", “capacityK”:102400, “totalK”:9280, “partition”:“tmpfs” }
2017-12-02T02:49:30.710619: { “msgid”:“dataSize”, “mountPoint”:"/var/log", “capacityK”:40960, “totalK”:7744, “partition”:“ramlog-tmpfs” }
2017-12-02T02:49:30.739012: { “msgid”:“dataSize”, “mountPoint”:"/DataVolume", “capacityK”:5809669936, “totalK”:1230375000, “partition”:"/dev/sda4" }
2017-12-02T02:49:30.884869: { “msgid”:“dataSize”, “mountPoint”:“4940db6e1da83a57bf143cf9700c7e43”, “capacityK”:1024, “totalK”:0, “partition”:“tmpfs” }
2017-12-02T02:49:30.941804: { “msgid”:“inodeUsage”, “filesystem”:“rootfs”, “inode”:125184, “iused”:25168, “mountPoint”:"/" }
2017-12-02T02:49:30.970322: { “msgid”:“inodeUsage”, “filesystem”:"/dev/root", “inode”:125184, “iused”:25168, “mountPoint”:"/" }
2017-12-02T02:49:30.999129: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:230, “mountPoint”:"/run" }
2017-12-02T02:49:31.027672: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:5, “mountPoint”:"/run/lock" }
2017-12-02T02:49:31.114646: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:155, “mountPoint”:“5a500f0368bd01ae8dc965a89133d5b3” }
2017-12-02T02:49:31.143200: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:2, “mountPoint”:"/run/shm" }
2017-12-02T02:49:31.171692: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:20480, “iused”:78, “mountPoint”:"/tmp" }
2017-12-02T02:49:31.208766: { “msgid”:“inodeUsage”, “filesystem”:“ramlog-tmpfs”, “inode”:1815, “iused”:118, “mountPoint”:"/var/log" }
2017-12-02T02:49:31.237638: { “msgid”:“inodeUsage”, “filesystem”:"/dev/sda4", “inode”:182996992, “iused”:233905, “mountPoint”:"/DataVolume" }
2017-12-02T02:49:31.383834: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:5, “mountPoint”:“4940db6e1da83a57bf143cf9700c7e43” }
2017-12-02T02:49:38.531915: { “msgid”:“usageSize”, “totalB”:1286287925822, “photos”:795366851, “video”:139292964049, “music”:2245445301, “other”:1143954149621 }
2017-12-02T03:01:01.732368: deviceInfoCollect: dryrun=0, system=0, configuration=1
2017-12-02T03:01:05.398423-05:00 di=wHxsG70otX notice deviceInfoCollect: { “msgid”:“configuration”, “ftp_enabled”:0, “volume_encryption_enabled”:0, “dlna_enabled”:0, “cloud_access_config”:“disabled”, “drive_standby_enabled”:1, “language”:“DEFAULT”, “RAID_mode”:“na”, “time_machine_enabled”:0, “network_config”:“static”, “auto_update_enabled”:0, “iTunes_enabled”:0, “ssh_enabled”:1 }
2017-12-02T03:05:02.754260: disable lazy init
2017-12-02T03:09:58.236229-05:00 di=wHxsG70otX notice getNewFirmwareUpgrade.sh: begin script: immediate send_alert auto
2017-12-02T03:09:58.264475-05:00 di=wHxsG70otX notice getNewFirmwareUpgrade.sh: http://support.wdc.com/nas/list.asp?devtype=sq&devfw=04.05.00-320&devlang=eng&devsn=&auto=0&devid=*****

[B???]
2017-12-02T03:20:55.048163: exit standby after 8 (since 2017-12-02 03:20:47.753437002 -0500)
2017-12-02T03:59:00.597333: exit standby after 1674 (since 2017-12-02 03:31:06.103437002 -0500)
2017-12-02T04:12:24.666181: exit standby after 7 (since 2017-12-02 04:12:17.413437002 -0500)

[atop activity - 8am]
2017-12-02T08:01:10.922479: exit standby after 13115 (since 2017-12-02 04:22:35.643437002 -0500)
2017-12-02T08:01:21.096637: Rotated atop, atop_size=2974325 atop_upload_size=1658

[C???]
2017-12-02T09:01:32.934997: exit standby after 3010 (since 2017-12-02 08:11:22.243437002 -0500)

[atop activity -4pm]
2017-12-02T15:55:08.477845: exit standby after 199 (since 2017-12-02 15:51:49.913437002 -0500)
2017-12-02T16:01:11.528294: Rotated atop, atop_size=4540945 atop_upload_size=3407

[atop activity - midnight]
2017-12-03T00:01:11.009827: exit standby after 12950 (since 2017-12-02 20:25:20.783437002 -0500)
2017-12-03T00:01:20.991854: Rotated atop, atop_size=3149101 atop_upload_size=670

2017-12-03T00:30:11.760602: exit standby after 1129 (since 2017-12-03 00:11:22.243437002 -0500)
2017-12-03T00:42:32.798951: exit standby after 7 (since 2017-12-03 00:42:25.533437002 -0500)
2017-12-03T00:57:10.991674: exit standby after 267 (since 2017-12-03 00:52:43.733437002 -0500)

[A???]
2017-12-03T01:17:11.456470: exit standby after 589 (since 2017-12-03 01:07:22.143437002 -0500)

2017-12-03T02:06:58.378589: exit standby after 2376 (since 2017-12-03 01:27:22.473437002 -0500)

[start of 3 am firmware check?]
2017-12-03T02:48:11.162805: exit standby after 1862 (since 2017-12-03 02:17:09.323437002 -0500)
2017-12-03T02:49:30.549503: { “msgid”:“dataSize”, “mountPoint”:"/", “capacityK”:1968336, “totalK”:664420, “partition”:“rootfs” }
2017-12-03T02:49:30.577522: { “msgid”:“dataSize”, “mountPoint”:"/", “capacityK”:1968336, “totalK”:664420, “partition”:"/dev/root" }
2017-12-03T02:49:30.605009: { “msgid”:“dataSize”, “mountPoint”:"/run", “capacityK”:40960, “totalK”:3904, “partition”:“tmpfs” }
2017-12-03T02:49:30.633023: { “msgid”:“dataSize”, “mountPoint”:"/run/lock", “capacityK”:40960, “totalK”:64, “partition”:“tmpfs” }
2017-12-03T02:49:30.815804: { “msgid”:“dataSize”, “mountPoint”:“5a500f0368bd01ae8dc965a89133d5b3”, “capacityK”:10240, “totalK”:0, “partition”:“tmpfs” }
2017-12-03T02:49:30.843794: { “msgid”:“dataSize”, “mountPoint”:"/run/shm", “capacityK”:5120, “totalK”:0, “partition”:“tmpfs” }
2017-12-03T02:49:30.871369: { “msgid”:“dataSize”, “mountPoint”:"/tmp", “capacityK”:102400, “totalK”:9344, “partition”:“tmpfs” }
2017-12-03T02:49:30.907310: { “msgid”:“dataSize”, “mountPoint”:"/var/log", “capacityK”:40960, “totalK”:7872, “partition”:“ramlog-tmpfs” }
2017-12-03T02:49:30.935344: { “msgid”:“dataSize”, “mountPoint”:"/DataVolume", “capacityK”:5809669936, “totalK”:1230406964, “partition”:"/dev/sda4" }
2017-12-03T02:49:31.074289: { “msgid”:“dataSize”, “mountPoint”:“4940db6e1da83a57bf143cf9700c7e43”, “capacityK”:1024, “totalK”:0, “partition”:“tmpfs” }
2017-12-03T02:49:31.131304: { “msgid”:“inodeUsage”, “filesystem”:“rootfs”, “inode”:125184, “iused”:25171, “mountPoint”:"/" }
2017-12-03T02:49:31.158916: { “msgid”:“inodeUsage”, “filesystem”:"/dev/root", “inode”:125184, “iused”:25171, “mountPoint”:"/" }
2017-12-03T02:49:31.186572: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:230, “mountPoint”:"/run" }
2017-12-03T02:49:31.214484: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:5, “mountPoint”:"/run/lock" }
2017-12-03T02:49:31.301581: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:155, “mountPoint”:“5a500f0368bd01ae8dc965a89133d5b3” }
2017-12-03T02:49:31.329746: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:2, “mountPoint”:"/run/shm" }
2017-12-03T02:49:31.357484: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:20480, “iused”:82, “mountPoint”:"/tmp" }
2017-12-03T02:49:31.393643: { “msgid”:“inodeUsage”, “filesystem”:“ramlog-tmpfs”, “inode”:1815, “iused”:118, “mountPoint”:"/var/log" }
2017-12-03T02:49:31.422046: { “msgid”:“inodeUsage”, “filesystem”:"/dev/sda4", “inode”:182996992, “iused”:233906, “mountPoint”:"/DataVolume" }
2017-12-03T02:49:31.554920: { “msgid”:“inodeUsage”, “filesystem”:“tmpfs”, “inode”:1815, “iused”:5, “mountPoint”:“4940db6e1da83a57bf143cf9700c7e43” }
2017-12-03T02:49:39.308136: { “msgid”:“usageSize”, “totalB”:1286320656958, “photos”:795366851, “video”:139292964049, “music”:2245445301, “other”:1143986880757 }
2017-12-03T03:01:02.448874: deviceInfoCollect: dryrun=0, system=0, configuration=1
2017-12-03T03:01:06.119432-05:00 di=wHxsG70otX notice deviceInfoCollect: { “msgid”:“configuration”, “ftp_enabled”:0, “volume_encryption_enabled”:0, “dlna_enabled”:0, “cloud_access_config”:“disabled”, “drive_standby_enabled”:1, “language”:“DEFAULT”, “RAID_mode”:“na”, “time_machine_enabled”:0, “network_config”:“static”, “auto_update_enabled”:0, “iTunes_enabled”:0, “ssh_enabled”:1 }
2017-12-03T03:05:02.509175: disable lazy init
2017-12-03T03:09:57.943787-05:00 di=wHxsG70otX notice getNewFirmwareUpgrade.sh: begin script: immediate send_alert auto
2017-12-03T03:09:57.978735-05:00 di=wHxsG70otX notice getNewFirmwareUpgrade.sh: http://support.wdc.com/nas/list.asp?devtype=sq&devfw=04.05.00-320&devlang=eng&devsn=&auto=0&devid=*****

[B???]
2017-12-03T03:20:55.259412: exit standby after 7 (since 2017-12-03 03:20:47.993437002 -0500)
2017-12-03T03:35:11.635716: exit standby after 245 (since 2017-12-03 03:31:06.203437002 -0500)
2017-12-03T04:17:11.687218: exit standby after 1909 (since 2017-12-03 03:45:22.643437002 -0500)

[atop activity -8am]
2017-12-03T08:01:11.018708: exit standby after 12828 (since 2017-12-03 04:27:22.663437002 -0500)
2017-12-03T08:01:21.223651: Rotated atop, atop_size=3255513 atop_upload_size=1654

[C???]
2017-12-03T09:01:32.874602: exit standby after 3010 (since 2017-12-03 08:11:22.213437002 -0500)

[atop activity - 4pm]
2017-12-03T16:01:11.062688: exit standby after 7819 (since 2017-12-03 13:50:52.083437002 -0500)
2017-12-03T16:01:21.229712: Rotated atop, atop_size=4392524 atop_upload_size=3445

[atop activity - midnight]
2017-12-04T00:01:11.299250: exit standby after 20548 (since 2017-12-03 18:18:43.333437002 -0500)
2017-12-04T00:01:21.051728: Rotated atop, atop_size=4404084 atop_upload_size=670
2017-12-04T00:13:48.037255: exit standby after 146 (since 2017-12-04 00:11:22.433437002 -0500)

2017-12-04T00:30:11.720172: exit standby after 373 (since 2017-12-04 00:23:58.973437002 -0500)
2017-12-04T00:42:32.903773: exit standby after 7 (since 2017-12-04 00:42:25.573437002 -0500)

[A???]
2017-12-04T01:17:11.779495: exit standby after 1467 (since 2017-12-04 00:52:43.993437002 -0500)


Firmware Release 04.05.00-320 (11/28/2017) Discussion
#22

Listed below is the cron jobs and when they are executed. I have not checked the list in a while so the newest firmware may have changed some. As for your ABC times There is a cron job set to run at 17 minutes after the hour. But the /etc/cron.hourly is empty. It is normal for the 7 second sleep to occur at B. This is due IMHO to the fact that all of the cached data that the system normally retains in memory. Gets over written during the processing done at the 3:00AM time. Such that those processes that normally run while the disk is a sleep need to be cached again. Once they are cached the drive will go back to sleep until around 8:00AM when the rotate log is run.
crontab (file). As for C not enough information to know why. I’ve noticed that my system is now waking up more frequent than it used to wake up. I guess I will have to look into why it is waking up.

At every 17th minute past every hour.
17 * * * * root cd / && run-parts --report /etc/cron.hourly
At 03:00 every day.
0 3 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
At 03:10 every day.
10 3 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
At 03:20 on the 1st of every month.
20 3 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly
)

cron.d (directory)
20-checkRAID
At 03:05 every day.
05 3 * * * root /usr/local/sbin/20-checkRAID.sh

WDSAFE
At 00:00 on Sun.
0 0 * * 0 root sudo perl /usr/local/NSPT/WDSafe/safeptExec.pl --operation=update --handle=1823638533
38136281313974967723235549772

auto_update
At 03:00 every day.
00 3 * * * root /usr/local/sbin/getNewFirmwareUpgrade.sh immediate send_alert auto; /usr/local/sbin
/checkAutoUpdate.sh

ga_cron_d
At 03:00 every day.
0 3 * * * root ga_cron.sh daily

mdadm
At 00:57 on Sun.
57 0 * * 0 root if [ -x /usr/share/mdadm/checkarray ] && [ $(date +%d) -le 7 ]; then /usr/share/mda
dm/checkarray --cron --all --idle --quiet; fi

php5.dpkg-dist
At every 9 and 39th minute past every hour.
09,39 * * * * root [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean

rescan_internal_volumes
At 03:10 every day.
10 3 * * * root [ -f /tmp/wdmc_rescan ] && /usr/local/sbin/wdmc_rescan_volume.py

ssl_cert_update
At 00:30 every day.
30 0 * * * root /usr/bin/php5 /var/www/rest-api/api/Remote/src/Remote/Cli/ssl_cert_job.php start > /
var/log/ssl_cert_cron.out 2>&1

sysstat
At every 5, 15, 25, 35, 45 and 55th minute past every hour.
5-55/10 * * * * root command -v debian-sa1 > /dev/null && debian-sa1 1 1
At 23:59 every day.
59 23 * * * root command -v debian-sa1 > /dev/null && debian-sa1 60 2

wdlog
At 03:01 every day.
01 3 * * * root /usr/local/sbin/PullWdlogConfig.sh
At 03:01 every day.
01 3 * * * root /usr/local/sbin/LogDataSize.sh
At 00:01 08:01 16:01
01 */8 * * * root [ -f /etc/init.d/atop ] && /etc/init.d/atop rotate
At 03:01 every day.
01 3 * * * root [ -f /usr/local/sbin/deviceInfoCollect.py ] && /usr/local/sbin/deviceInfoCollect.py
-c
At 03:01 every Tuesday
01 3 * * 2 root [ -f /usr/local/sbin/deviceInfoCollect.py ] && /usr/local/sbin/deviceInfoCollect.py
-s

cron.daily (directory)
apache2 aptitude cracklib-runtime logrotate mdadm passwd sysstat
apt bsdmainutils dpkg man-db ntpdate ramlog

cron.hourly (directory)

cron.monthly (directory)

cron.weekly (directory)
man-db


#23

I’m fairly sure that this was part of WD trying to fix the overflowing logs back in the day. A second possibility of rotating logs are the logs are now on the ram drive and they needed a copy of the logs in case you re-boot the drive.

I’m not sure why everyone is still keeping the cron alive as I have killed the cron for years now without any consequences. Of course if you need sync, you will need the cron.

I have forgotten how I turned off the cron in my old Cloud, but because I’m on busybox, I’m just using
killall cron

This gets rid of the routine wakeups including the checking for firmware update despite the fact that it is turned off on the dashboard.

Good job everyone on their sleuthing. Too bad I cannot join you anymore since I’m on the new cloud box.

my old script… of which I’m sure everyone has their own and better version now. However back in the day, my WD cloud would sleep for 2 or 3 days solid; absolutely no wakeups. If my mac was mapped to the drives, it would potentially wake up the drives so if the drives were not mapped on any device, it should sleep. My entertainment mac mini does have the drive mapped but since it too was asleep, my cloud remained asleep.

> #!/bin/bash
> /etc/init.d/nfs-kernel-server stop
> /etc/init.d/nfs-common stop
> /etc/init.d/upnp_nas stop
> /etc/init.d/mDNSResponder stop
> /etc/init.d/wdphotodbmergerd stop
> /etc/init.d/wdnotifierd stop
> /etc/init.d/wdmcserverd stop
> /etc/init.d/wddispatcherd stop
> /etc/init.d/restsdk-serverd stop
> mount -o remount,noatime,nodiratime /dev/root /

my new version for revision 2 Cloud

> #!/bin/bash
> /etc/init.d/wdphotodbmergerd stop
> /etc/init.d/wdmcserverd stop
> /etc/init.d/wdnotifierd stop
> /etc/init.d/wddispatcherd stop
> killall crond
> drive_sleep.sh off
> sleep 1
> drive_sleep.sh on
> hd_standby.sh 5

#24

Thanks for your further input…

I did some more looking through the various logs and found something in the “kern” log at 3:05 that involves disk mounting. Also the “Ram Log” states:
“Dec 06 03:00:08 Restarting ramlog = saving logs to hdd: [ok]”

The only thing I found for around 9am was an entry in the “atop_upload.log.1” file. It’s not an exact match to the time I was concerned with, but it does indicate some further “atop” activity. FYI Here it is in its entirety:

-------------------------- analysis date: 2017/12/06 --------------------------

2017-12-06T08:01:21-0500
2017-12-06T09:03:21-0500 di=wHxsG70otX { mi:cpu,total:201.3%,n1:atopacctd-5649,c1:201.3% }
2017-12-06T09:03:21-0500 di=wHxsG70otX { mi:mem,tot:162,buf:7,cache:40,swp:103,n1:apache2-13091,KB1:16256,pf1:0,n2:apache2-8283,KB2:10176,pf2:0,n3:apache2-30937,KB3:9408,pf3:0,n4:atop-22864,KB4:7488,pf4:0,n5:smbd-6053,KB5:4672,pf5:0,n6:winbindd-6069,KB6:3776,pf6:0,n7:rsyslogd-4166,KB7:3520,pf7:0,n8:nmbd-6013,KB8:3520,pf8:0,n9:smbd-6017,KB9:3008,pf9:0,n10:winbindd-6065,KB10:2944,pf10:0 }

Finally I looked in the (downloaded log files) “current/config/etc/cron.d” folder in the hope of finding scheduled cron jobs but all that was there was one file - “WDSAFE” but it was completely empty (zero bytes).

Can I find the cron jobs by SSHing in? - where would I look?

One last thing I want to mention is that it’s since become clear that regardless of the state of Network Discovery, that a PC can wake the MC upon its own wakening - although, as mentioned earlier, it only does this after 2+ hrs of being asleep. (Also the PC only has to wake - not necessarily be logged into to wake the MC.)

I think I’ve gotten as far as I can on this!

Thanks all…


#25

More investigation. Don’t know if this has been mentioned/asked in past discussions on the missing dynamicconfig.ini but has anyone post a link to that file if they have one on their My Cloud unit? It appears there are (on my v4.x version My Cloud) two other dynamicconfig.ini files in the firmware. One located at /etc/wdcomp.d/admin-rest-api/saved_settings/var/www/rest-api/config/ and the other at /var/www/rest-api/config/.

It appears to be related to UPnP ports (possibly port mapping) apparently if this WD Knowledgebase article is correct.

My Cloud uPnP Port Mapping
My Cloud external uPnP ports are radomly assigned between the port range of 9000 - 9999.

Run the following command to see what Internal and External My Cloud and uPnP ports are being assigned.

cat /tmp/dynamicconfig.ini | grep PORT

Format of the output is

EXTERNAL_PORT=“9000
EXTERNAL_SSL_PORT=“9446
INTERNAL_PORT=“80
DEVICE_SSL_PORT=“443
DEFAULT_PORTS_ONLY=“FALSE”
MANUAL_PORT_FORWARD=“FALSE”
MANUAL_EXTERNAL_HTTP_PORT=""
MANUAL_EXTERNAL_HTTPS_PORT=""

For giggles I’ve copied the /var/www/rest-api/config/dynamicconfig.ini version (since it has values and the other one didn’t) to the /tmp/ folder to see what happens and if dynamicconfig.ini error message in the logs goes away in the User.log.

Edit to add: While one can copy the dynamicconfig.ini into the /tmp/ folder the file is not retained upon reboot even when using the 98user-start file to copy the file into the /tmp/ folder. It appears the /tmp/ folder is created after the 98user-start file is run. With the dynamicconfig.ini file in the /tmp/ folder it does appear the User.log no such file or directory entries for dynamicconfig.ini that show up every 10 seconds does stop.


#26

Not sure why the S98user-start file fails. The /tmp directory is used by several of the scripts in /etc/rc2.d before the S98user-start file is called.
I thought that the problem with the dynamicconfig.ini file. Only existed if remote access was enabled.
My testing of the sleep issue seems to show that samba is accessing a couple of files every minute or so. This is with my gen1 on firmware 04.04.02-105. If I stop samba the device will sleep up to several hours at a time. I thought that this problem was fixed previously. I can’t find any information on the fix or work around.


#27

I have remote access disabled through the Dashboard and was still getting those error messages fillling the user.log file every 10 seconds. With the file there the error messages no longer appear. Not sure why using the CP command to copy the file to the /tmp/ directory is failing. Going to do some more investigating. Perhaps putting the file in a Share directory and copying it from there might work (edit: that didn’t work either).

Now I’m getting a few periodic wake ups every 25 to 28 seconds every now and then with similar messages as this:

2017-12-09T21:35:11.410389-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 26 (since 2017-12-09 21:34:45.944906000 -0500)
2017-12-09T21:47:56.230858-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 153 (since 2017-12-09 21:45:23.294906000 -0500)

And the investigation continues. :slight_smile:


#28

Still having the notice logger thing happening periodically every 25 seconds or so to wake the My Cloud up once it goes to sleep. Some fooling around with the monitorio.sh by adding several more: sync and sleep 5 entries yields lengthening the time those previous 25 second wakeups were occurring.

12 10 06:47:31 07:08:38  1267  0:21:07
12 10 07:45:31 07:45:56    25  0:00:25
12 10 08:11:26 08:11:51    25  0:00:25
12 10 10:13:03 10:13:29    25  0:00:25
12 10 10:27:46 10:28:12    26  0:00:26
12 10 10:38:24 10:41:03   159  0:02:39
12 10 10:55:22 10:55:47    25  0:00:25
12 10 11:05:59 11:06:24    25  0:00:25
12 10 11:16:36 11:17:08    32  0:00:32
12 10 11:27:21 11:27:46    25  0:00:25
12 10 11:37:58 11:38:22    24  0:00:24
12 10 11:48:34 11:53:21   287  0:04:47
12 10 12:13:44 12:14:10    25  0:00:25
12 10 12:24:22 12:39:19   897  0:14:57
12 10 12:51:34 12:51:59    25  0:00:25
12 10 13:17:31 13:17:57    26  0:00:26 <-- added several lines to Mmonitorio.sh to lengthen time out
12 10 16:15:59 16:16:45    45  0:00:45 <-- results in time out being moved longer
12 10 16:26:57 16:50:27  1410  0:23:30
12 10 17:05:45 17:06:30    45  0:00:45
12 10 17:24:52 17:25:38    46  0:00:46
12 10 17:35:50 17:36:36    46  0:00:46
12 10 17:46:48 17:50:27   219  0:03:39
12 10 18:00:39 18:01:25    46  0:00:46

#29

This is strange. Here is a script that you can run for a few hours. It will tell you what files are being accessed when it wakes up. I call it checkgen1.sh

#!/bin/bash
function test () {
if [ “$3” != “$2” ]; then
da=date +%k-%M-%S
A=$2
B=1
ior_sda=${A#-}
iow_sda=${A%-
}
A=$3
ior_sdaold=${A#-}
iow_sdaold=${A%-
}
let a=ior_sda-ior_sdaold
let b=iow_sda-iow_sdaold
if [ $4 -ne 1 ]; then
echo -n $da " "
fi
printf "%4s %4s %4s " “sda”$1 $a $b
fi
}

function GetData {
for (( i=1; i<8;i++ ));
do
y=printf "%s%s" $3 $i
x=awk -v disk="$y" '{if ($3==disk) printf "%s-%s",$10,$6}' /proc/diskstats
sda[$i]=$x
done
}
while :; do
GetData ior_sda1 iow_sda1 “sda”
B=0
for (( i=1; i<8;i++ ));
do
test $i “${sda[$i]}” “${sdb[$i]}” $B
done
sdb=("${sda[@]}")
if [ $B -eq 1 ]; then
echo
find / -path /proc -prune -o -path /sys -prune -o -cmin -1
fi
sleep 4
done


#30

It is strange. It’s also rather frustrating we users have to go to such lengths to fix problems with the My Cloud firmware, but I digress. LOL Running the checkgen1.sh was next on my list of things to do to try and find out what is causing the first gen unit to not sleep consistently.

My problem is that I use both Samba and Twonky so I cannot disable those services. I know Samba has in the past been the cause of some issues with the My Cloud. Will probably have to test disabling both Samba and Twonky at some point too.


#31

Last night when I was testing I found that the /etc/samba/smbpasswd file was having its permissions changed every 20 seconds. The version of samba on my system is 4.0.0rc5. I’m running firmware 04.04.02-105. What I don’t understand is that this same firmware was sleeping well in the past. When I ran the sleep script last night it showed that the system last slept at 9:57 in the morning. So it had been awake for about 15 hours. I the past I found that there was some code in samba that would do a chmod 0600 on the /etc/samba/smbpasswd file even thought it was already set to 0600. What I’m currently doing is stopping samba when I’m not using it.


#32

Let Checkgen1.sh run for a few hours. Pretty much the same set of entries throughout. Will have to output the results to a log file since the command window only shows the last portion of the capture.

10-42-01  sda1 -286704    0 sda2 3989386 -2013928 sda3 -22229146 1272408 sda4 26237410 786856 sda6 1024    0 sda7  384    0
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-42-44  sda1 -255664   16 sda2 4004522 -2013912 sda3 -22302178 1274328 sda4 26309930 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-43-26  sda1 -242784   16 sda2 4020338 -2015816 sda3 -22374698 1275480 sda4 26385874 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-44-06  sda1 -249768    0 sda2 4052626 -2016968 sda3 -22445394 1276632 sda4 26457370 786856 sda6 1024    0 sda7  384    0
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-44-49  sda1 -271224   16 sda2 4089746 -2018104 sda3 -22511002 1278168 sda4 26532378 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-45-31  sda1 -300568   16 sda2 4119026 -2019624 sda3 -22582298 1278168 sda4 26610362 786856 sda6 1024    0 sda7  384    0
/dev/xconsole
/tmp
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-46-12  sda1 -304120    0 sda2 4122018 -2019624 sda3 -22658106 1278680 sda4 26684458 786856 sda6 1024    0 sda7  384    0
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-46-55  sda1 -277704   16 sda2 4135746 -2020120 sda3 -22731178 1278808 sda4 26757626 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-47-36  sda1 -269600   16 sda2 4157938 -2020232 sda3 -22804346 1278808 sda4 26834730 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-48-17  sda1 -280416    0 sda2 4181954 -2020232 sda3 -22877354 1278808 sda4 26908010 786856 sda6 1024    0 sda7  384    0
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-48-59  sda1 -282800   16 sda2 4204674 -2020216 sda3 -22949866 1278808 sda4 26982626 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-49-40  sda1 -295664   16 sda2 4239714 -2020200 sda3 -23023586 1278936 sda4 27060738 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-50-24  sda1 -275920    0 sda2 4257650 -2020328 sda3 -23031042 1282904 sda4 27141530 786856 sda6 1024    0 sda7  384    0
/dev/xconsole
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/apache2/access.log
/var/log/atop/atop_current
/proc
/sys
10-51-08  sda1 -256848   16 sda2 4211642 -2024280 sda3 -23106714 1284440 sda4 27220034 786856 sda6 1024    0 sda7  384    0
/dev/xconsole
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/apache2/access.log
/var/log/atop/atop_current
/proc
/sys
10-51-50  sda1 -270856   16 sda2 4245290 -2025800 sda3 -23178818 1291992 sda4 27298658 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-52-33  sda1 -290904    0 sda2 4262866 -2033352 sda3 -23255522 1303896 sda4 27372458 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-53-15  sda1 -303336   16 sda2 4293466 -2045240 sda3 -23328170 1306456 sda4 27446690 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-53-57  sda1 -301648   16 sda2 4310850 -2047784 sda3 -23399458 1308888 sda4 27524130 786856 sda6 1024    0 sda7  384    0
/etc/samba/msg.sock
/run/samba/msg.lock
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-54-40  sda1 -275272    0 sda2 4313226 -2050216 sda3 -23469090 1311064 sda4 27598706 786856 sda6 1024    0 sda7  384    0
/etc/samba/msg.sock
/run/samba/msg.lock
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-55-22  sda1 -261960   16 sda2 4335218 -2052376 sda3 -23537266 1311064 sda4 27672234 786856 sda6 1024    0 sda7  384    0
/dev/xconsole
/tmp
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-56-04  sda1 -281608   16 sda2 4365674 -2052360 sda3 -23610410 1311064 sda4 27750426 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-56-45  sda1 -311880    0 sda2 4398354 -2052360 sda3 -23688602 1311064 sda4 27823138 786856 sda6 1024    0 sda7  384    0
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-57-28  sda1 -324880   16 sda2 4424002 -2052344 sda3 -23760034 1311576 sda4 27895290 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-58-09  sda1 -302368   16 sda2 4429634 -2052840 sda3 -23830266 1311704 sda4 27973018 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-58-50  sda1 -293384    0 sda2 4450890 -2052968 sda3 -23907610 1312344 sda4 28045770 786856 sda6 1024    0 sda7  384    0
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
10-59-32  sda1 -298552   16 sda2 4482706 -2053592 sda3 -23977930 1312856 sda4 28118522 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
11-00-14  sda1 -313136   16 sda2 4522858 -2054088 sda3 -24047354 1315800 sda4 28196330 786856 sda6 1024    0 sda7  384    0
/dev/xconsole
/tmp
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
11-00-56  sda1 -340024    0 sda2 4543394 -2057032 sda3 -24124778 1315800 sda4 28267554 786856 sda6 1024    0 sda7  384    0
/dev/xconsole
/tmp
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
11-01-38  sda1 -354384   16 sda2 4580442 -2057016 sda3 -24192162 1317208 sda4 28340258 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
11-02-20  sda1 -373560  256 sda2 4608050 -2058168 sda3 -24263970 1317208 sda4 28417730 786856 sda6 1024    0 sda7  384    0
/dev/xconsole
/tmp
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/lib/logrotate
/var/lib/logrotate/status
/var/log/atop/atop_current
/proc
/sys
11-03-01  sda1 -389568   64 sda2 4632226 -2058104 sda3 -24341442 1317720 sda4 28490162 786856 sda6 1024    0 sda7  384    0
/dev/xconsole
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
11-03-44  sda1 -389896   40 sda2 4654682 -2058576 sda3 -24413106 1317720 sda4 28561858 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
11-04-26  sda1 -378824   16 sda2 4669122 -2058560 sda3 -24480578 1317848 sda4 28638826 786856 sda6 1024    0 sda7  384    0
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys

#33

Putty has the option window scrollback. I usually set mine to 10000 or more depending on what I’m trying to capture. But you can also log the putty session.
I see two things in the output. One is the problem with msg.sock which has been discussed before. We had to move the msg.sock to a tmp directory using a symbolic link. The other problem maybe the atop program. Not sure if this is a issue for sleep. I’ve seen the same files on my checkgen1 output. To me this problem seem to come and go. Why is it that the system will sleep fine, then at some point in the future with no apparent changes it starts to act up. This samba problem is not consistent. Also unless a work around can be found the only way to fix the problem is to recompile samba. A few people may be able to do this. But the rest of the users need WD to recompile samba with a fix. But they don’t really care if the device sleeps or not.


#34

Forgot about the log feature in Putty. Was calling the script with plink through a BAT file. Used the code to move the msg.sock to a tmp directory in the past but removed it. Added it back in to see if it changes anything. Guess I could put an atop stop into the user-start file and then setup an automated reboot so the My Cloud is rebooted every eight hours to stop that service from running. Overkill I think. LOL.

Have to wonder why WD included an enable/disable sleep option when the device doesn’t sleep without having to stop all sorts of services and make additional modifications at the firmware level.


#35

Don’t know about WD. Not sure they care. I just checked my atop_current it has not been touched since dec 6th. The stat command shows all three times for a file. I wonder why your system is showing atop_current when my system is not currently showing? You could make a temp change to the cron file for atop to only run once a day at 3AM. That way the system is already awake. Then after a few minutes kill atop.

#stat /var/log/atop/atop_current
File: `/var/log/atop/atop_current’
Size: 2604541 Blocks: 5120 IO Block: 65536 regular file
Device: 14h/20d Inode: 4456577 Links: 1
Access: (0644/-rw-r–r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2017-12-07 03:00:18.585675001 -0500
Modify: 2017-12-06 12:05:31.955675001 -0500
Change: 2017-12-06 12:05:31.955675001 -0500
Birth: -


#36

I would think if one is stopping the atop service (/etc/rc2.d/S03atop stop) in the user-start file they’d only see the atop run once (maybe twice) a day due to the eight hour cycle it apparently restarts when it is stopped. I’ll add the /etc/rc2.d/S03atop stop to my user start and see what if anything changes.

My atop listing:

# stat /var/log/atop/atop_current
File: `/var/log/atop/atop_current'
Size: 6933186         Blocks: 13568      IO Block: 65536  regular file
Device: 14h/20d Inode: 6612        Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2017-12-11 12:37:30.060591002 -0500
Modify: 2017-12-11 15:51:30.204689001 -0500
Change: 2017-12-11 15:51:30.204689001 -0500
Birth: -

#37

I just checked my system and atop is not running. I do have a stop atop in the S98user-start script.


#38

I don’t know why I didn’t see this but the /var/log/atop/atop_current file in on a tmpfs file system. So that will not create any disk activity. Since everything is in the tmp directories. The only thing left is the msg.sock.

PS if you want to look at the atop_current file. just issue
atop -r /var/log/atop/atop_current

It will display information about what has been run on the system. The bottom half of the screen can be scrolled to see information about each process.


#39

I’ve found a possible problem with the smbpasswd file. On my system the smbpasswd file has one user george. On my gen2 system is has two users nobody and admin. Not that familiar with samba to know if this is a problem.


#40

Have the same on my first gen. One user account (admin) and that’s it. Currently looking through the atop_current results. Interesting to see what processes are running.

With just the ISP router and My Cloud active on the local network for 6 hours there were still lots of periodic My Cloud wake ups beyond the standard wake up for log rotation (atop) and firmware check. And the experimenting/investigation continues.

12 11 23:55:59 23:56:24    25  0:00:25
12 12 00:06:35 00:13:26   411  0:06:51
12 12 00:23:37 00:24:15    38  0:00:38
12 12 00:41:34 00:42:00    26  0:00:26
12 12 00:52:11 01:15:21  1390  0:23:10
12 12 01:25:32 01:45:43  1211  0:20:11
12 12 01:55:54 02:00:11   257  0:04:17
12 12 02:10:21 02:14:55   274  0:04:34
12 12 02:25:06 02:29:06   240  0:04:00
12 12 02:39:17 02:48:11   534  0:08:54
12 12 03:16:37 03:17:02    25  0:00:25
12 12 03:27:13 03:31:16   243  0:04:03
12 12 03:41:27 03:47:27   360  0:06:00
12 12 03:57:38 04:04:29   411  0:06:51
12 12 04:14:39 05:19:45  3906  1:05:06
12 12 05:29:56 06:02:52  1976  0:32:56

User.log results for that same time period:

2017-12-11T23:56:24.448071-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 25 (since 2017-12-11 23:55:59.004689001 -0500)
2017-12-12T00:01:02.389882-05:00 di=8ZV9Y8qLUS notice logger: Rotated atop, atop_size=43013 atop_upload_size=109
2017-12-12T00:13:26.224083-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 411 (since 2017-12-12 00:06:35.294689001 -0500)
2017-12-12T00:24:15.823106-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 38 (since 2017-12-12 00:23:37.044689001 -0500)
2017-12-12T00:42:00.203903-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 26 (since 2017-12-12 00:41:34.884689001 -0500)
2017-12-12T01:15:21.302945-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 1390 (since 2017-12-12 00:52:11.124689001 -0500)
2017-12-12T01:45:43.647927-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 1211 (since 2017-12-12 01:25:32.194689001 -0500)
2017-12-12T02:00:11.076588-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 257 (since 2017-12-12 01:55:54.524689001 -0500)
2017-12-12T02:14:55.783742-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 274 (since 2017-12-12 02:10:21.964689001 -0500)
2017-12-12T02:29:06.843404-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 240 (since 2017-12-12 02:25:06.724689001 -0500)
2017-12-12T02:48:11.422834-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 534 (since 2017-12-12 02:39:17.744689001 -0500)
2017-12-12T02:57:25.444717-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/", "capacityK":1968336, "totalK":669840, "partition":"rootfs" }
2017-12-12T02:57:25.472283-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/", "capacityK":1968336, "totalK":669840, "partition":"/dev/root" }
2017-12-12T02:57:25.499781-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/run", "capacityK":40960, "totalK":4672, "partition":"tmpfs" }
2017-12-12T02:57:25.527618-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/run/lock", "capacityK":40960, "totalK":64, "partition":"tmpfs" }
2017-12-12T02:57:25.729509-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"5a500f0368bd01ae8dc965a89133d5b3", "capacityK":10240, "totalK":0, "partition":"tmpfs" }
2017-12-12T02:57:25.757326-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/run/shm", "capacityK":5120, "totalK":0, "partition":"tmpfs" }
2017-12-12T02:57:25.784963-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/tmp", "capacityK":102400, "totalK":9728, "partition":"tmpfs" }
2017-12-12T02:57:25.820558-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/var/log", "capacityK":40960, "totalK":10368, "partition":"ramlog-tmpfs" }
2017-12-12T02:57:25.848493-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/DataVolume", "capacityK":7747781188, "totalK":465722764, "partition":"/dev/sda4" }
2017-12-12T02:57:26.034345-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"4940db6e1da83a57bf143cf9700c7e43", "capacityK":1024, "totalK":0, "partition":"tmpfs" }
2017-12-12T02:57:26.090542-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"rootfs", "inode":125184, "iused":25401, "mountPoint":"/" }
2017-12-12T02:57:26.117992-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"/dev/root", "inode":125184, "iused":25401, "mountPoint":"/" }
2017-12-12T02:57:26.145180-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"tmpfs", "inode":1815, "iused":224, "mountPoint":"/run" }
2017-12-12T02:57:26.173079-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"tmpfs", "inode":1815, "iused":5, "mountPoint":"/run/lock" }
2017-12-12T02:57:26.258646-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"tmpfs", "inode":1815, "iused":153, "mountPoint":"5a500f0368bd01ae8dc965a89133d5b3" }
2017-12-12T02:57:26.286451-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"tmpfs", "inode":1815, "iused":2, "mountPoint":"/run/shm" }
2017-12-12T02:57:26.314082-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"tmpfs", "inode":20480, "iused":86, "mountPoint":"/tmp" }
2017-12-12T02:57:26.349826-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"ramlog-tmpfs", "inode":1815, "iused":103, "mountPoint":"/var/log" }
2017-12-12T02:57:26.377614-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"/dev/sda4", "inode":244043776, "iused":37486, "mountPoint":"/DataVolume" }
2017-12-12T02:57:26.564186-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"tmpfs", "inode":1815, "iused":5, "mountPoint":"4940db6e1da83a57bf143cf9700c7e43" }
2017-12-12T02:57:32.439872-05:00 di=8ZV9Y8qLUS notice BaseOSlog: { "msgid":"usageSize", "totalB":488095539446, "photos":363821751, "video":218964987162, "music":251204323990, "other":17562406543 }
2017-12-12T03:01:02.701032-05:00 di=8ZV9Y8qLUS notice logger: deviceInfoCollect: dryrun=0, system=0, configuration=1 
2017-12-12T03:01:02.716812-05:00 di=8ZV9Y8qLUS notice logger: deviceInfoCollect: dryrun=0, system=1, configuration=0 
2017-12-12T03:01:03.321628-05:00 di=8ZV9Y8qLUS notice deviceInfoCollect: { "msgid":"deviceinfo", "fwupdatedate":"1512672808", "eula":"1512673734", "csrv":"www.wd2go.com", "total_memK":232320, "fwversion":"04.05.00-320", "modelnumber":"sq", "total_swapK":500672 }
2017-12-12T03:01:06.180457-05:00 di=8ZV9Y8qLUS notice deviceInfoCollect: { "msgid":"configuration", "ftp_enabled":0, "volume_encryption_enabled":0, "dlna_enabled":1, "cloud_access_config":"disabled", "drive_standby_enabled":1, "language":"DEFAULT", "RAID_mode":"na", "time_machine_enabled":0, "network_config":"dhcp", "auto_update_enabled":0, "iTunes_enabled":0, "ssh_enabled":1 }
2017-12-12T03:02:31.592183-05:00 di=8ZV9Y8qLUS notice getNewFirmwareUpgrade.sh: begin script: immediate send_alert auto
2017-12-12T03:02:31.629850-05:00 di=8ZV9Y8qLUS notice getNewFirmwareUpgrade.sh: http://support.wdc.com/nas/list.asp?devtype=sq&devfw=04.05.00-320&devlang=eng&devsn=&auto=0&devid=*****
2017-12-12T03:05:02.022967-05:00 di=8ZV9Y8qLUS notice logger: disable lazy init
2017-12-12T03:17:02.430097-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 25 (since 2017-12-12 03:16:37.044024001 -0500)
2017-12-12T03:31:16.836317-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 243 (since 2017-12-12 03:27:13.254024001 -0500)
2017-12-12T03:47:27.941269-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 360 (since 2017-12-12 03:41:27.694024001 -0500)
2017-12-12T04:04:29.171962-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 411 (since 2017-12-12 03:57:38.744024001 -0500)
2017-12-12T05:19:45.251256-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 3906 (since 2017-12-12 04:14:39.904024001 -0500)
2017-12-12T06:02:52.992592-05:00 di=8ZV9Y8qLUS notice logger: exit standby after 1976 (since 2017-12-12 05:29:56.024024001 -0500)