On mine, msg.sock is nine minutes old right now.
Interesting. Now my system has stopped doing this for the last 15 minutes.
On my system there are 5 sockets. 4 were created when I restarted samba.
The last one has a create date of 15 minutes ago.
It finally updated after thirty minutes.
I have nine, four of which one second apart when it was first powered up this morning.
Question is this samba socket action keeping the disk spinning or just keeping the MC awake.
This is the activity that I was logging when the msg.sock was being updated. It is a repeating pattern every 60 seconds. This output is from blktrace.
9,0 1 414 1801.999977405 439 Q WS a47fb602 1578840 + 8 [kjournald]
9,0 1 415 1802.529933515 439 Q WS a47fb603 1578848 + 8 [kjournald]
9,0 1 416 1802.529945225 439 Q WS a47fb603 1578856 + 8 [kjournald]
9,0 1 417 1802.529953240 439 Q WS a47fb603 1578864 + 8 [kjournald]
9,0 1 418 1802.529961040 439 Q WS a47fb603 1578872 + 8 [kjournald]
9,0 1 419 1802.529969010 439 Q WS a47fb603 1578880 + 8 [kjournald]
9,0 1 420 1802.529975450 439 Q WS a47fb603 1578888 + 8 [kjournald]
9,0 1 421 1802.530823035 439 Q WBS a47fb603 1578896 + 8 [kjournald]
9,0 1 422 1832.549907460 326 Q W a47fb621 264792 + 8 [flush-9:0]
9,0 1 423 1833.099056995 326 Q W a47fb622 264808 + 8 [flush-9:0]
9,0 1 424 1833.099095015 326 Q W a47fb622 285184 + 8 [flush-9:0]
9,0 1 425 1833.099132740 326 Q W a47fb622 0 + 8 [flush-9:0]
9,0 1 426 1833.099142825 326 Q W a47fb622 8 + 8 [flush-9:0]
9,0 1 427 1833.099165100 326 Q W a47fb622 263144 + 8 [flush-9:0]
9,0 1 428 1862.000181600 439 Q WS a47fb63f 1578904 + 8 [kjournald]
9,0 1 429 1862.034817535 439 Q WS a47fb63f 1578912 + 8 [kjournald]
9,0 1 430 1862.034837135 439 Q WS a47fb63f 1578920 + 8 [kjournald]
9,0 1 431 1862.034844560 439 Q WS a47fb63f 1578928 + 8 [kjournald]
9,0 1 432 1862.034851395 439 Q WS a47fb63f 1578936 + 8 [kjournald]
9,0 1 433 1862.034858405 439 Q WS a47fb63f 1578944 + 8 [kjournald]
9,0 1 434 1862.034865435 439 Q WS a47fb63f 1578952 + 8 [kjournald]
9,0 1 435 1862.035603890 439 Q WBS a47fb63f 1578960 + 8 [kjournald]
9,0 0 281 1892.060113200 326 Q W a47fb65d 263144 + 8 [flush-9:0]
9,0 0 282 1892.581755725 326 Q W a47fb65d 264792 + 8 [flush-9:0]
9,0 0 283 1892.581768330 326 Q W a47fb65d 264808 + 8 [flush-9:0]
9,0 0 284 1892.581788265 326 Q W a47fb65d 285184 + 8 [flush-9:0]
9,0 0 285 1892.581819780 326 Q W a47fb65d 0 + 8 [flush-9:0]
9,0 0 286 1892.581827200 326 Q W a47fb65d 8 + 8 [flush-9:0]
9,0 0 287 1922.999982155 439 Q WS a47fb67b 1578968 + 8 [kjournald]
9,0 0 288 1923.028716585 439 Q WS a47fb67c 1578976 + 8 [kjournald]
9,0 0 289 1923.028727620 439 Q WS a47fb67c 1578984 + 8 [kjournald]
9,0 0 290 1923.028734490 439 Q WS a47fb67c 1578992 + 8 [kjournald]
9,0 0 291 1923.028741555 439 Q WS a47fb67c 1579000 + 8 [kjournald]
9,0 0 292 1923.028749250 439 Q WS a47fb67c 1579008 + 8 [kjournald]
9,0 0 293 1923.028756155 439 Q WS a47fb67c 1579016 + 8 [kjournald]
9,0 0 294 1923.029502675 439 Q WBS a47fb67c 1579024 + 8 [kjournald
It was writting to the disk every 60 seconds. Since it requires that there be no disk activity for 10 minutes.
The disk is never put in standby mode. This is my sleep activity today. It woke up at 8:30 didn’t go back to sleep until 15:30 but then woke up 8 seconds later. The first time is the time it put the disk in standby mode. The second time is the time that the disk woke up. The last two number give the number of seconds and the time in hour/minutes/seconds.
04 23 00:22:56 00:23:04 8 0:00:08
04 23 01:15:18 01:15:26 8 0:00:08
04 23 01:25:42 01:32:28 406 0:06:46
04 23 03:15:47 03:15:55 8 0:00:08
04 23 03:26:12 03:32:32 380 0:06:20
04 23 08:06:53 08:07:01 8 0:00:08
04 23 08:17:18 08:18:45 87 0:01:27
04 23 08:29:01 08:33:06 245 0:04:05
04 23 15:30:58 15:31:06 8 0:00:08
04 23 15:41:22 15:54:51 809 0:13:29
04 23 16:05:07 16:09:45 278 0:04:38
1 Like
Yes aware of that. I updated the firmware back on the 13th when WD initially released it. There’s only about 400GB on the drive at the moment so it should have long been done rescanning/reindexing.
Mine sleeps like a baby!
Well, I don’t live in this forum, not real tech savvy, I have this folder/sockets and all I can say is that mine spins and sleeps. I haven’t added anything to it that didn’t come with it either.
Actually I’m not the first person to complain about the drive not sleeping. This is when my disk entered standby today. Notice the 4:43 times.
04 23 00:22:56 00:23:04 8 0:00:08
04 23 01:15:18 01:15:26 8 0:00:08
04 23 01:25:42 01:32:28 406 0:06:46
04 23 03:15:47 03:15:55 8 0:00:08
04 23 03:26:12 03:32:32 380 0:06:20
04 23 08:06:53 08:07:01 8 0:00:08
04 23 08:17:18 08:18:45 87 0:01:27
04 23 08:29:01 08:33:06 245 0:04:05
04 23 15:30:58 15:31:06 8 0:00:08
04 23 15:41:22 15:54:51 809 0:13:29
04 23 16:05:07 16:09:45 278 0:04:38
04 23 16:20:02 16:24:55 293 0:04:53
04 23 16:35:12 16:39:55 283 0:04:43
04 23 16:50:12 16:52:50 158 0:02:38
04 23 17:13:21 17:13:29 8 0:00:08
04 23 17:23:46 17:24:56 70 0:01:10
04 23 17:35:13 17:39:56 283 0:04:43
04 23 17:50:12 17:54:56 284 0:04:44
04 23 18:05:12 18:09:56 284 0:04:44
04 23 18:20:13 18:24:56 283 0:04:43
04 23 18:35:12 18:39:56 284 0:04:44
04 23 18:50:13 18:54:56 283 0:04:43
04 23 19:05:12 19:09:56 283 0:04:43
04 23 19:20:13 19:24:56 283 0:04:43
04 23 19:35:13 19:39:56 283 0:04:43
04 23 19:50:13 19:54:56 283 0:04:43
04 23 20:15:29 20:17:11 102 0:01:42
The latest firmware is disgrace. Automatic updates is turned off. But still updated.
The device is crashing frequently. I am constantly having problems reaching. Everything is normal after restart. But after a while it happens again. Performance is not stable. Reading speed is decreasing by 0mb/sec. The device becomes useless.
Wd My Cloud 3TB via Gigabit Ethernet, Windows 10 1703
@Bill_S so can you check whether anyone at WD is getting this info? or are we going to wait for another year to get another update that doesn’t address any of these issues?
You need to contact support with this, and specifically tell them this happened after the update. They will make some recommendations to troubleshoot, but once that’s done, and if the issue continues, they will forward it to the correct product people for further investigation.
Is anyone else having problems with the DNLA service after this firmware upgrade? My device has no media indexed, and when I try to rebuild the DNLA database it gets to just over 13000 media files then reverses back down to 0
Firmware upgrades regularly mess up the media server. Check that media sharing is enabled for all shares containing media, and that media server is enabled.
@cpt_paranoia - Thanks for responding. When the DNLA Database rebuild is in progress, I can see the content on the Bose app we use, so I have evidence that the content is being made available. I’ll check the Media sharing for the actual share we keep the content on
What I noticed is that most of the “regular” users mistake “sleep mode problems” with the inability of the device to enter sleep mode. Except in some cases, it does so. The thing is a lot of people do not stay near the device long enough to notice that it wakes up for no reason every minute or more often. Checking the log is even less likely to happen.
I’m disappointed WD is unwilling (but not unable) to sacrifice their curiosity and greed for Big Data and let users be really happy. And the environment clean, too.
Yes, that’s what happens; media appears in the database, and then when the scan is complete, it realises sharing is not enabled, and it takes it all away again…
Have a read of the FAQ
One does not have to sit in front of the device to see that it sleeps or wakes up. The information is in the log.
Here is the sleep status of My device. I have two clouds The one on the previous firmware sleeps about 82% and is awake 18% of the time. As you can see from the output of the system with the newer firmware it is the opposite where it sleeps 11% of the time and awake 89% of the time. An interesting pattern shows up where it wakes up after 4 minutes and 43 seconds a lot of the time. Also at 03:58 it woke up and has been awake since. It is 07:51 now. This device has nothing on it yet. Just the stock firmware. The only thing I have done is to stop the restsdk-serverd process because it causes tons of messages to be logged.
04 23 00:22:56 00:23:04 8 0:00:08
04 23 01:15:18 01:15:26 8 0:00:08
04 23 01:25:42 01:32:28 406 0:06:46
04 23 03:15:47 03:15:55 8 0:00:08
04 23 03:26:12 03:32:32 380 0:06:20
04 23 08:06:53 08:07:01 8 0:00:08
04 23 08:17:18 08:18:45 87 0:01:27
04 23 08:29:01 08:33:06 245 0:04:05
04 23 15:30:58 15:31:06 8 0:00:08
04 23 15:41:22 15:54:51 809 0:13:29
04 23 16:05:07 16:09:45 278 0:04:38
04 23 16:20:02 16:24:55 293 0:04:53
04 23 16:35:12 16:39:55 283 0:04:43
04 23 16:50:12 16:52:50 158 0:02:38
04 23 17:13:21 17:13:29 8 0:00:08
04 23 17:23:46 17:24:56 70 0:01:10
04 23 17:35:13 17:39:56 283 0:04:43
04 23 17:50:12 17:54:56 284 0:04:44
04 23 18:05:12 18:09:56 284 0:04:44
04 23 18:20:13 18:24:56 283 0:04:43
04 23 18:35:12 18:39:56 284 0:04:44
04 23 18:50:13 18:54:56 283 0:04:43
04 23 19:05:12 19:09:56 283 0:04:43
04 23 19:20:13 19:24:56 283 0:04:43
04 23 19:35:13 19:39:56 283 0:04:43
04 23 19:50:13 19:54:56 283 0:04:43
04 23 20:15:29 20:17:11 102 0:01:42
04 23 20:27:27 20:32:07 280 0:04:40
04 23 20:42:24 20:54:56 752 0:12:32
04 23 21:24:44 21:24:52 8 0:00:08
04 23 21:35:09 21:39:57 288 0:04:48
04 23 21:50:14 21:54:57 283 0:04:43
04 23 22:05:12 22:09:51 279 0:04:39
04 23 22:20:07 22:25:01 293 0:04:53
04 23 22:35:18 22:40:01 283 0:04:43
04 23 22:50:17 22:51:10 53 0:00:53
04 23 23:01:27 23:01:35 8 0:00:08
04 23 23:11:51 23:14:36 165 0:02:45
04 23 23:24:53 23:25:00 7 0:00:07
04 23 23:35:16 23:35:22 6 0:00:06
04 23 23:45:39 23:55:01 562 0:09:22
04 24 00:05:16 00:08:55 219 0:03:39
04 24 00:19:11 00:23:41 270 0:04:30
04 24 00:33:58 00:34:05 7 0:00:07
04 24 00:44:22 00:48:48 266 0:04:26
04 24 00:59:04 01:01:00 116 0:01:56
04 24 03:16:01 03:16:09 8 0:00:08
04 24 08:13:06 08:13:14 8 0:00:08
04 24 08:33:45 08:40:03 378 0:06:18
04 24 08:50:20 08:55:03 283 0:04:43
04 24 14:12:26 14:12:34 8 0:00:08
04 24 14:22:51 14:32:43 592 0:09:52
04 24 14:43:00 14:47:43 283 0:04:43
04 24 14:58:00 15:02:43 283 0:04:43
04 24 15:12:59 15:17:43 284 0:04:44
04 24 15:31:05 15:32:43 98 0:01:38
04 24 15:43:00 15:44:49 109 0:01:49
04 24 15:55:05 16:01:05 360 0:06:00
04 24 16:11:21 16:17:43 382 0:06:22
04 24 16:28:00 16:32:43 283 0:04:43
04 24 16:43:00 16:47:43 283 0:04:43
04 24 16:58:00 17:01:23 203 0:03:23
04 24 17:11:40 17:17:43 363 0:06:03
04 24 17:28:00 17:32:43 283 0:04:43
04 24 17:43:00 17:47:44 284 0:04:44
04 24 17:58:00 18:02:43 283 0:04:43
04 24 18:13:00 18:17:43 283 0:04:43
04 24 18:28:00 18:32:43 283 0:04:43
04 24 18:43:00 18:47:43 283 0:04:43
04 24 18:58:00 19:02:43 283 0:04:43
04 24 19:13:00 19:17:43 283 0:04:43
04 24 19:28:00 19:32:43 283 0:04:43
04 24 19:43:00 19:47:43 283 0:04:43
04 24 19:58:00 20:02:43 283 0:04:43
04 24 20:13:00 20:17:43 283 0:04:43
04 24 20:28:00 20:32:43 283 0:04:43
04 24 20:42:58 20:44:21 83 0:01:23
04 24 20:54:38 21:02:43 485 0:08:05
04 24 21:23:11 21:25:07 116 0:01:56
04 24 21:35:24 21:39:01 217 0:03:37
04 24 22:09:45 22:09:53 8 0:00:08
04 24 22:20:09 22:28:21 492 0:08:12
04 24 22:38:38 22:43:21 283 0:04:43
04 24 22:53:38 22:58:21 283 0:04:43
04 24 23:08:36 23:13:21 285 0:04:45
04 24 23:23:38 23:28:21 283 0:04:43
04 24 23:38:38 23:43:21 283 0:04:43
04 24 23:53:38 23:58:21 283 0:04:43
04 25 00:08:37 00:12:40 243 0:04:03
04 25 00:22:57 00:28:21 324 0:05:24
04 25 03:16:08 03:16:17 9 0:00:09
04 25 03:26:33 03:28:17 104 0:01:44
04 25 03:38:33 03:43:21 288 0:04:48
04 25 03:53:38 03:58:22 284 0:04:44
Total Sleep Time: 6:04:44
Start 1492920130
End 1493107102
Total Up Time: 51:56:12 11% Sleep 89% Wake
