Firmware 4.05.00-315 Discussion

No I haven’t had time to go back and look at the sleep issue on my v4.x My Cloud. Probably in a few days I will. Its obvious something new, or a value that has changed, is now keeping the My Cloud awake.

My v4.x MC does sleep but doesn’t seem to be anything abnormally wrong compared to before the upgrade.

@Bennor, don’t forget that the device will re-scan/index all your files on a firmware update.

If you check you will see that a new directory called /etc/samba/msg.sock has been created. This
directory gets updated every minute. It appears to be creating a new socket every minute. I see kjournal
writes every minute updating the inode of /etc/samba/msg.sock.
The new firmware has a newer version of samba.

@rac8006, alright… good find I guess, workaround? redirect to temp perhaps? stop and re-start samba? something in the samba config? is this also true for gen2?

Have not upgraded the gen2 yet. No known work around. restarting samba does not fix the problem. I also noticed that smbd creates a new process every minute. If you look at the sockets listed in /etc/samba/msg.sock. You will see that a new socket is created every minute. The name of the socket is the pid of the new smbd process.

I posted a email on the samba technical group asking about the msg.sock.

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!

Really? According to @rac8006 it ain’t happening.

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?

@Emrah_Karacam

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.