Alastair_Gordon wrote:
If anyone has an aswer to the constant spinning bug, I would love to hear it.
If the disk is spinning, something is still using it.
Mine sleeps soundly most of the day…
In fact, SSH’ing into it just now to look, I had to wait until the disk spun up…
That’s interesting, because I have NEVER had a spin-up delay with my My Cloud and I can always hear the quiet whir of the rotating platter. There seem to be a lot of posts elsewhere that make the same observation. Someone even claimed that their My Cloud kept spinning long after the Ethernet cable was disconnected, but I cannot verify that claim.
From SSH I can see that the “smbd” process runs briefly whenever the drive is accessed via its drive letter in Windows Explorer, but immediately goes away. I think if anything on the LAN was accessing the My Cloud, that “smbd” would be running. Am I wrong about that?
I am positive that NOTHING on the LAN (wired or wireless) is accessing the My Cloud drive, but maybe…
Do you know how long it takes after the last read/write for your My Cloud disk to stop spinning?
Alastair_Gordon wrote:
From SSH I can see that the “smbd” process runs briefly whenever the drive is accessed via its drive letter in Windows Explorer, but immediately goes away. I think if anything on the LAN was accessing the My Cloud, that “smbd” would be running. Am I wrong about that?
At least one smbd should be running at all times – even if nothing is connected, because there must be one process running to handle incoming NEW connections.
When an active connection (for example, a file open) is created, another smbd process can be spawned to service that request.
CloudNAS:~# ps aux | grep smb
root 5656 0.0 0.3 8568 828 ? Ss Jan07 1:27 /usr/sbin/smbd -D
root 5727 0.0 0.3 9064 896 ? S Jan07 0:04 /usr/sbin/smbd -D
root 18355 0.0 0.3 8568 800 ? S 14:10 0:00 /usr/sbin/smbd -D
root 18400 0.0 0.2 1604 560 pts/0 S+ 14:10 0:00 grep smb
root 27132 0.0 0.9 14716 2080 ? S Jan19 0:06 /usr/sbin/smbd -D
CloudNAS:~# cat /proc/5656/status | grep -i ppid
PPid: 1
CloudNAS:~# cat /proc/5727/status | grep -i ppid
PPid: 5656
CloudNAS:~#
At the time I executed that command, there were four SMB daemons running.
Since process 5656 has a “PPid” of 1, that’s the one that runs forever. (It was spawned by the parent process “init,” which is the ultimate parent of everything)
Process 5727, as you see, has parent 5656 which is the “main” SMB daemon above.
Unplugging the network cable has odd consequences. Unplugging the cable causes several errors, so it will probably spin up the disk to load up the error handling scripts which send e-mail notifications, changes the Web UI, etc.
It probably will continue to run because it can’t get anything out, but I’ve never tried that myself…
Looking at my log files, it looks like it’s about 10 minutes for it to go into standby…
Here’s today’s log so far:
Jan 24 03:00:08 CloudNAS logger: exit standby after 20189 (since 2014-01-23 21:23:39.305480001 -0600)
Jan 24 03:16:26 CloudNAS logger: exit standby after 314 (since 2014-01-24 03:11:12.047114001 -0600)
Jan 24 03:42:37 CloudNAS logger: exit standby after 967 (since 2014-01-24 03:26:30.867114001 -0600)
Jan 24 03:55:08 CloudNAS logger: exit standby after 146 (since 2014-01-24 03:52:42.187114001 -0600)
Jan 24 04:24:32 CloudNAS logger: exit standby after 1160 (since 2014-01-24 04:05:12.727114001 -0600)
Jan 24 06:54:35 CloudNAS logger: exit standby after 8399 (since 2014-01-24 04:34:36.907114001 -0600)
Jan 24 07:45:17 CloudNAS logger: exit standby after 1346 (since 2014-01-24 07:22:51.887114001 -0600)
Jan 24 07:57:30 CloudNAS logger: exit standby after 7 (since 2014-01-24 07:57:23.477114001 -0600)
Jan 24 08:09:14 CloudNAS logger: exit standby after 99 (since 2014-01-24 08:07:35.477114001 -0600)
Jan 24 08:23:46 CloudNAS logger: exit standby after 267 (since 2014-01-24 08:19:19.077114001 -0600)
Jan 24 08:34:11 CloudNAS logger: exit standby after 21 (since 2014-01-24 08:33:50.767114001 -0600)
Jan 24 08:52:45 CloudNAS logger: exit standby after 509 (since 2014-01-24 08:44:16.377114001 -0600)
Jan 24 09:05:08 CloudNAS logger: exit standby after 138 (since 2014-01-24 09:02:50.567114001 -0600)
Jan 24 09:15:54 CloudNAS logger: exit standby after 41 (since 2014-01-24 09:15:13.467114001 -0600)
Jan 24 09:26:24 CloudNAS logger: exit standby after 26 (since 2014-01-24 09:25:58.937114001 -0600)
Jan 24 09:38:13 CloudNAS logger: exit standby after 104 (since 2014-01-24 09:36:29.227114001 -0600)
Jan 24 09:48:56 CloudNAS logger: exit standby after 38 (since 2014-01-24 09:48:18.577114001 -0600)
Jan 24 10:20:41 CloudNAS logger: exit standby after 1299 (since 2014-01-24 09:59:01.997114001 -0600)
Jan 24 10:53:11 CloudNAS logger: exit standby after 1345 (since 2014-01-24 10:30:46.597114001 -0600)
Jan 24 11:11:01 CloudNAS logger: exit standby after 465 (since 2014-01-24 11:03:16.337114001 -0600)
Jan 24 11:39:02 CloudNAS logger: exit standby after 1076 (since 2014-01-24 11:21:06.257114001 -0600)
Jan 24 11:55:08 CloudNAS logger: exit standby after 362 (since 2014-01-24 11:49:06.827114001 -0600)
Jan 24 12:34:55 CloudNAS logger: exit standby after 1783 (since 2014-01-24 12:05:12.707114001 -0600)
Jan 24 13:05:46 CloudNAS logger: exit standby after 1246 (since 2014-01-24 12:45:00.087114001 -0600)
Jan 24 14:08:17 CloudNAS logger: exit standby after 3146 (since 2014-01-24 13:15:51.127114001 -0600)
Jan 24 14:27:21 CloudNAS logger: exit standby after 236 (since 2014-01-24 14:23:24.447114001 -0600)
So today, it’s gone to sleep 25 times Heck. Just noticed it went to sleep while I was logged in via SSH even… (That very last line…)
That very first line says that until 3:00AM (when CRON jobs start) the NAS had been peacefully sleeping since 9:23PM last night.
Thanks TonyPh12345. You clearly know a lot more about this stuff than I do. Many thanks for joining the hunt.
But my findings are different from yours. Have a look at this:
--------------------------------------------------------
SSH ‘top’ - Nothing accessing My Cloud:
ZERO instance of ‘smbd’ running
30105 root 20 0 2664 1196 804 R 0.7 0.5 0:00.76 top
2199 root 20 0 0 0 0 D 0.3 0.0 7:47.64 pfe_ctrl_timer
1 root 20 0 1688 108 84 S 0.0 0.0 0:12.06 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.02 kthreadd
3 root 20 0 0 0 0 D 0.0 0.0 0:00.00 cpu1_hotplug_th
4 root 20 0 0 0 0 S 0.0 0.0 2:17.41 ksoftirqd/0
7 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
8 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/1
9 root 20 0 0 0 0 S 0.0 0.0 0:24.90 kworker/1:0
10 root 20 0 0 0 0 S 0.0 0.0 1:47.83 ksoftirqd/1
11 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 cpuset
12 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper
13 root 20 0 0 0 0 S 0.0 0.0 0:00.02 kworker/u:1
38 root 20 0 0 0 0 S 0.0 0.0 0:23.43 kworker/1:1
215 root 20 0 0 0 0 S 0.0 0.0 0:01.02 sync_supers
217 root 20 0 0 0 0 S 0.0 0.0 0:00.03 bdi-default
219 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd
225 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 ata_sff
236 root 20 0 0 0 0 S 0.0 0.0 0:00.21 khubd
242 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 md
265 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 rpciod
278 root 20 0 0 0 0 S 0.0 0.0 9:08.44 kswapd0
279 root 20 0 0 0 0 S 0.0 0.0 0:00.00 fsnotify_mark
280 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 nfsiod
281 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto
319 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_0
322 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_1
325 root 20 0 0 0 0 S 0.0 0.0 0:00.09 kworker/u:2
--------------------------------------------------------
SSH ‘top’ - COPYING files from My Cloud to PC on LAN:
ONE instance of ‘smbd’ running (I think I briefly saw 2 instances of smbd running)
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
30209 nobody 20 0 18276 10m 9.8m S 28.8 4.7 0:14.46 smbd
30284 root 20 0 2664 1148 804 R 0.7 0.5 0:00.99 top
10 root 20 0 0 0 0 S 0.3 0.0 1:48.00 ksoftirqd/1
2199 root 20 0 0 0 0 D 0.3 0.0 7:48.16 pfe_ctrl_timer
18071 root 20 0 0 0 0 S 0.3 0.0 0:02.62 kworker/0:1
1 root 20 0 1688 108 84 S 0.0 0.0 0:12.07 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.02 kthreadd
3 root 20 0 0 0 0 D 0.0 0.0 0:00.00 cpu1_hotplug_th
4 root 20 0 0 0 0 S 0.0 0.0 2:17.42 ksoftirqd/0
7 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
8 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/1
9 root 20 0 0 0 0 S 0.0 0.0 0:24.90 kworker/1:0
11 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 cpuset
12 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper
13 root 20 0 0 0 0 S 0.0 0.0 0:00.02 kworker/u:1
38 root 20 0 0 0 0 S 0.0 0.0 0:23.50 kworker/1:1
215 root 20 0 0 0 0 S 0.0 0.0 0:01.02 sync_supers
217 root 20 0 0 0 0 S 0.0 0.0 0:00.03 bdi-default
219 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd
225 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 ata_sff
236 root 20 0 0 0 0 S 0.0 0.0 0:00.21 khubd
242 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 md
265 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 rpciod
278 root 20 0 0 0 0 S 0.0 0.0 9:08.52 kswapd0
279 root 20 0 0 0 0 S 0.0 0.0 0:00.00 fsnotify_mark
280 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 nfsiod
281 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto
319 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_0
--------------------------------------------------------
SSH ‘top’ - FINISHED copying files from My Cloud to PC on LAN:
ZERO instance of ‘smbd’ running, once again (normal resting state)
--------------------------------------------------------
Continued in next post…
Now here is the user log (/var/usr/user.log). As you can see, according to the log, My Cloud is entering and leaving Standby all the time, but I always can hear the disk platter spinning.
Jan 24 00:17:08 WDMyCloud logger: exit standby after 476 (since 2014-01-24 00:09:12.902930001 -0800)
Jan 24 00:39:44 WDMyCloud logger: exit standby after 147 (since 2014-01-24 00:37:17.532930001 -0800)
Jan 24 00:40:18 WDMyCloud REST_API[14723]: 192.168.0.10 OUTPUT SystemConfiguration\Controller\FactoryRestore GET SUCCESS
Jan 24 00:40:20 WDMyCloud REST_API[21340]: 192.168.0.10 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 00:40:30 WDMyCloud REST_API[21311]: 192.168.0.10 OUTPUT Alerts\Controller\Alerts GET SUCCESS
Jan 24 00:40:45 WDMyCloud REST_API[21402]: 192.168.0.10 OUTPUT TimeMachine\Controller\TimeMachine GET
Jan 24 00:40:45 WDMyCloud REST_API[21402]: 192.168.0.10 OUTPUT TimeMachine\Controller\TimeMachine GET
Jan 24 00:40:46 WDMyCloud REST_API[21339]: 192.168.0.10 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 01:02:09 WDMyCloud logger: exit standby after 13 (since 2014-01-24 01:01:56.902930001 -0800)
Jan 24 01:17:08 WDMyCloud logger: exit standby after 294 (since 2014-01-24 01:12:14.032930001 -0800)
Jan 24 01:45:04 WDMyCloud logger: exit standby after 1071 (since 2014-01-24 01:27:13.252930001 -0800)
Jan 24 02:35:08 WDMyCloud logger: exit standby after 582 (since 2014-01-24 02:25:26.492930001 -0800)
Jan 24 03:00:09 WDMyCloud logger: exit standby after 291 (since 2014-01-24 02:55:17.452930001 -0800)
Jan 24 03:05:02 WDMyCloud logger: disable lazy init
Jan 24 03:17:07 WDMyCloud logger: exit standby after 111 (since 2014-01-24 03:15:16.862930002 -0800)
Jan 24 03:37:03 WDMyCloud logger: exit standby after 591 (since 2014-01-24 03:27:12.522930002 -0800)
Jan 24 03:47:18 WDMyCloud logger: exit standby after 11 (since 2014-01-24 03:47:07.662930002 -0800)
Jan 24 04:03:09 WDMyCloud logger: exit standby after 346 (since 2014-01-24 03:57:23.582930002 -0800)
Jan 24 04:29:54 WDMyCloud logger: exit standby after 1001 (since 2014-01-24 04:13:13.642930002 -0800)
Jan 24 04:52:29 WDMyCloud logger: exit standby after 751 (since 2014-01-24 04:39:58.662930002 -0800)
Jan 24 05:18:19 WDMyCloud logger: exit standby after 945 (since 2014-01-24 05:02:33.622930002 -0800)
Jan 24 05:44:47 WDMyCloud logger: exit standby after 984 (since 2014-01-24 05:28:23.622930002 -0800)
Jan 24 06:10:13 WDMyCloud logger: exit standby after 922 (since 2014-01-24 05:54:51.592930002 -0800)
Jan 24 06:33:12 WDMyCloud logger: exit standby after 775 (since 2014-01-24 06:20:17.632930002 -0800)
Jan 24 07:00:14 WDMyCloud logger: exit standby after 1018 (since 2014-01-24 06:43:16.622930002 -0800)
Jan 24 07:22:43 WDMyCloud logger: exit standby after 745 (since 2014-01-24 07:10:18.652930002 -0800)
Jan 24 07:33:11 WDMyCloud logger: exit standby after 23 (since 2014-01-24 07:32:48.622930002 -0800)
Jan 24 07:53:33 WDMyCloud logger: exit standby after 13 (since 2014-01-24 07:53:20.242930002 -0800)
Jan 24 08:14:14 WDMyCloud logger: exit standby after 32 (since 2014-01-24 08:13:42.622930002 -0800)
Jan 24 08:28:14 WDMyCloud logger: exit standby after 236 (since 2014-01-24 08:24:18.642930002 -0800)
Jan 24 08:28:39 WDMyCloud REST_API[21311]: 192.168.0.49 OUTPUT SystemConfiguration\Controller\FactoryRestore GET SUCCESS
Jan 24 08:28:40 WDMyCloud REST_API[9566]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:28:50 WDMyCloud REST_API[9537]: 192.168.0.49 OUTPUT Alerts\Controller\Alerts GET SUCCESS
Jan 24 08:28:58 WDMyCloud REST_API[9497]: 192.168.0.49 OUTPUT TimeMachine\Controller\TimeMachine GET
Jan 24 08:28:58 WDMyCloud REST_API[9497]: 192.168.0.49 OUTPUT TimeMachine\Controller\TimeMachine GET
Jan 24 08:28:59 WDMyCloud REST_API[9497]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:29:24 WDMyCloud REST_API[9537]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:29:27 WDMyCloud REST_API[9545]: 192.168.0.49 OUTPUT SystemConfiguration\Controller\FactoryRestore GET SUCCESS
Jan 24 08:29:28 WDMyCloud REST_API[9537]: 192.168.0.49 OUTPUT Disk\Controller\SmartTest GET SUCCESS
Jan 24 08:29:59 WDMyCloud REST_API[9497]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:30:30 WDMyCloud REST_API[10027]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:31:30 WDMyCloud REST_API[21339]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:32:31 WDMyCloud REST_API[21339]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:33:31 WDMyCloud REST_API[9545]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:34:32 WDMyCloud REST_API[9545]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:35:32 WDMyCloud REST_API[9545]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:36:32 WDMyCloud REST_API[9545]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:37:33 WDMyCloud REST_API[9545]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:38:33 WDMyCloud REST_API[10785]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:39:34 WDMyCloud REST_API[10785]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:40:34 WDMyCloud REST_API[10785]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:41:35 WDMyCloud REST_API[10785]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:42:35 WDMyCloud REST_API[10785]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:43:35 WDMyCloud REST_API[11007]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:44:36 WDMyCloud REST_API[11393]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:45:36 WDMyCloud REST_API[10936]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:46:37 WDMyCloud REST_API[10785]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
exec: No such file or directory
Jan 24 08:47:37 WDMyCloud REST_API[11393]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:48:38 WDMyCloud REST_API[10936]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:49:38 WDMyCloud REST_API[11007]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:50:39 WDMyCloud REST_API[11007]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:51:39 WDMyCloud REST_API[11007]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:52:39 WDMyCloud REST_API[12197]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:53:40 WDMyCloud REST_API[12197]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:54:40 WDMyCloud REST_API[12197]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:55:41 WDMyCloud REST_API[12109]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:56:41 WDMyCloud REST_API[12554]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:57:42 WDMyCloud REST_API[12109]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:58:42 WDMyCloud REST_API[12554]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 08:59:42 WDMyCloud REST_API[12109]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:00:43 WDMyCloud REST_API[12554]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:01:43 WDMyCloud REST_API[12554]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:02:44 WDMyCloud REST_API[12553]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:03:44 WDMyCloud REST_API[12109]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:04:45 WDMyCloud REST_API[12197]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:05:45 WDMyCloud REST_API[13470]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:06:45 WDMyCloud REST_API[13470]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:07:46 WDMyCloud REST_API[12553]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:08:46 WDMyCloud REST_API[13709]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:09:47 WDMyCloud REST_API[13756]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:10:47 WDMyCloud REST_API[13470]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:11:48 WDMyCloud REST_API[13709]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:11:49 WDMyCloud logger: exit standby after 12 (since 2014-01-24 09:11:37.392930002 -0800)
Jan 24 09:12:48 WDMyCloud REST_API[13709]: 192.168.0.49 OUTPUT DlnaServer\Controller\Database GET SUCCESS
Jan 24 09:33:57 WDMyCloud logger: exit standby after 724 (since 2014-01-24 09:21:53.912930002 -0800)
Jan 24 10:03:46 WDMyCloud logger: exit standby after 1185 (since 2014-01-24 09:44:01.652930002 -0800)
Jan 24 10:33:09 WDMyCloud logger: exit standby after 1159 (since 2014-01-24 10:13:50.702930002 -0800)
Jan 24 10:46:07 WDMyCloud logger: exit standby after 174 (since 2014-01-24 10:43:13.652930002 -0800)
Jan 24 11:18:28 WDMyCloud logger: exit standby after 6 (since 2014-01-24 11:18:22.522930002 -0800)
Jan 24 11:49:57 WDMyCloud logger: exit standby after 317 (since 2014-01-24 11:44:40.622930002 -0800)
Jan 24 12:00:09 WDMyCloud logger: exit standby after 7 (since 2014-01-24 12:00:02.442930002 -0800)
exec: No such file or directory
Jan 24 12:19:06 WDMyCloud logger: exit standby after 351 (since 2014-01-24 12:13:15.772930002 -0800)
Jan 24 12:30:07 WDMyCloud logger: exit standby after 57 (since 2014-01-24 12:29:10.682930002 -0800)
Jan 24 12:43:07 WDMyCloud logger: exit standby after 175 (since 2014-01-24 12:40:12.522930002 -0800)
Jan 24 13:12:13 WDMyCloud logger: exit standby after 1142 (since 2014-01-24 12:53:11.622930002 -0800)
Jan 24 13:37:59 WDMyCloud logger: exit standby after 337 (since 2014-01-24 13:32:22.252930002 -0800)
Jan 24 14:04:50 WDMyCloud logger: exit standby after 1007 (since 2014-01-24 13:48:03.642930002 -0800)
Jan 24 14:28:57 WDMyCloud logger: exit standby after 843 (since 2014-01-24 14:14:54.652930002 -0800)
Jan 24 14:53:44 WDMyCloud logger: exit standby after 883 (since 2014-01-24 14:39:01.742930002 -0800)
exec: No such file or directory
Jan 24 15:18:57 WDMyCloud logger: exit standby after 909 (since 2014-01-24 15:03:48.642930002 -0800)
--------------------------------------------------------
There is no fan in a My Cloud, so I am assuming the only sound I could hear is the platter spinning. It seems that “standby” and “disk not spinning” are not the same state. Wrong?
Does the blue LED in the front fade in and out? Mine does, and the disk is certainly spun down. No noise at all.
TOP doesn’t show all processes, it just shows the busiest from the top down. The command ‘ps aux | grep smbd’ will show you the processes whether they’re active or not.
Aaaaargh, Unix! In SSH I did a standard # grndl fnafrl<=>schnek fadinkel grok and discovered that my framastat was ungrepped.
Just kidding! Thanks for the much more useful command, which showed up exactly what you had said earlier:
WDMyCloud:/var/log# ps aux | grep smbd
root 1812 0.0 0.2 1604 556 pts/0 S+ 16:56 0:00 grep smbd
root 5982 0.0 0.4 8288 944 ? Ss Jan22 0:07 /usr/sbin/smbd -D
root 5993 0.0 0.3 8412 856 ? S Jan22 0:01 /usr/sbin/smbd -D
root 30209 0.3 4.7 18200 10936 ? S 15:20 0:21 /usr/sbin/smbd -D
The blue LED is on steady when I enable the LED on in the My Cloud Dashboard, and off steady when I disable the LED in the My Cloud Dashboard. The LED does not seem to relfect disk activity at all.
Again, thank you for your help in figuring out why the platter never stops spinning on my My Cloud.
Do this:
smartctl -a /dev/sda
cut and paste the entire output, but don’t include the serial numbers (for security)
Here it is:
WDMyCloud:~# smartctl -a /dev/sda
smartctl 5.41 2011-06-09 r3365 [armv7l-linux-3.2.26] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: WDC WD30EFRX-68EUZN0
Serial Number: WD-xxxxxxxxxxxxxxxxxxxxxx
LU WWN Device Id: xxxxxxxxxxxxxxxxxxxxxx
Firmware Version: 80.00A80
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 9
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Fri Jan 24 18:39:26 2014 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (41160) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x703d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 182 181 021 Pre-fail Always - 5900
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 141
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 147
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 7
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 4
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 854
194 Temperature_Celsius 0x0022 114 101 000 Old_age Always - 36
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
WDMyCloud:~#
Observation: On another forum where people were complaining that the WD My Cloud would never spin down, a couple of people indicated that it would spin down if you disabled and re-enabled Drive Sleep in the My Cloud Dashboard. So I tried that, and some time later (maybe 30-60 minutes?), the platter stopped spinning.
However, others observed that after they accessed the My Cloud, it never spun down again until the next time they disabled and re-enabled Drive Sleep. I expect that will be the case with my My Cloud as well.
Don’t know if this helps.
Your smartctl data does show your drive going into standby – 141 times in the 147 hours it’s been powered on. Ovarall, that’s about the same rate as mine (roughly once per power-on-hour)
But if the drive is spinning even if it thinks it’s in standby, then my only guess is that there’s a possible firmware bug in the internal HD itself.
As to the LCCs: While an average of 4 or 5 LCC’s per power-on-hour isn’t anything to be concerned with, the folks that have higher-than-normal LCC counts seem to have either the 4TB or 3TB version. I have the 2TB version and my LCC count is about 1 per hour.
In fact, WD just released a utility to modify the firmware settings on certain internal WD RED drives:
Maybe there will be a change to the Cloud drive to modify the HD’s firmware.
Huh. I just clicked that link again – the utility is no longer there.
Captain_Panaka wrote:
I can load that page but I am not intelligent enough what to do. They have Linux 64bit and Linux32 not saying a single word about the platform it is built for!!!
Weird. It shows in IE11, but not in Chrome.
Anyway, yes, it does. x32 and x64 refer to Intel 32-bit and 64-bit.
TonyPh12345 wrote:
Your smartctl data does show your drive going into standby – 141 times in the 147 hours it’s been powered on. Ovarall, that’s about the same rate as mine (roughly once per power-on-hour)
But if the drive is spinning even if it thinks it’s in standby, then my only guess is that there’s a possible firmware bug in the internal HD itself.
As to the LCCs: While an average of 4 or 5 LCC’s per power-on-hour isn’t anything to be concerned with, the folks that have higher-than-normal LCC counts seem to have either the 4TB or 3TB version. I have the 2TB version and my LCC count is about 1 per hour.
In fact, WD just released a utility to modify the firmware settings on certain internal WD RED drives:
Maybe there will be a change to the Cloud drive to modify the HD’s firmware.
Thanks so much, Tony. You and Captain Panaka have been essential in helping me understand the SMART disk drive data.
So to summarize:
(1) The latest SMART data tells me that I have had 172 Spindle Start/Stop Counts in 160 hours, or about one per hour (normal). Yet my EAR tells me that the spindle has been spinning the whole time, except after I disable/re-enable Drive Sleep, after which it will sleep until the first access following which it spins again forever. You’re right, this has to be a firmware bug.
(2) The latest SMART data tells me that I have had 1045 Load Cycle Counts (LCCs) in 160 hours, or about 6.5 LCCs per hour (possibly excessive). My WD My Cloud is the 3TB version, which you indicated is known for generating a higher-than-normal LCC count.
The only conclusion I can reach for the ever-spinning spindle (and possibly the high LCC) is a WD firmware bug (even though the SMART data says the spindle starts/stops about once per hour). I wonder why that link disappeared that seemed to address this problem?
I’m not saying that it’s a Known Thing affecting all of the 3TBs, but that there appears to be a pattern…
Captain_Panaka wrote:
If after 4 months of users complaining about that situation WD does not pretty soon resolve those problems it will soon give a s.hit-storm like the one which was a few years ago when that unfortunate head unload stuff was introduced in green WD drives.
And yes I know, the messenger who brings up that information gets killed like in the Dark Ages
I’m not big on martyrdom, but we do appreciate your sacrifice 
Captain_Panaka wrote:
TonyPh12345 wrote:
I’m not saying that it’s a Known Thing affecting all of the 3TBs, but that there appears to be a pattern…
Who do you think said that it is affecting _ all _ of the 3 TBs?
No one said that, to my knowledge. I overstated the issue by saying that it is a “known problem”, but Tony corrected it above. Just an emerging pattern.
If it’s a known firmware bug why don’t they fix it?
I never figured out what MyCloud was. Got the app, never used it. I use a couple other apps to access my NAS.
I figured out MyCloud was their cloud, and I want my own cloud, not theirs, or I’d just store my stuff on Google drive.
I don’t trust anybody but me with storing my stuff, and sometimes I kind of wonder about me. I have a kind of shifty look when I stare at myself in the mirror, shaving. Maybe it’s because the foam makes it look like I have rabies.
Based on the SMART data results…Just a thought…Would it be possible that there is command line scheduling with CRON on WDMyCloud that creates logfile entries that are written to disk say once every hour ?
i just got mine 2Tb, how do you guys know if your disk gets to sleep?
mine in very quite, but blue led seems always on, should it flash when is in tand by?
| Forums | News and Announcements | Register | Help | Forum Guidelines |
Copyright © 2021 Western Digital Technologies, Inc. All rights
reserved.
|
Trademarks
|
Privacy
|
Community Terms of Service
|
Site Terms of Use
|
Copyright
|
Contact WD
|