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


#41

ps -eaf:

UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 Dec03 ?        00:00:10 init [2]
root         2     0  0 Dec03 ?        00:00:00 [kthreadd]
root         3     2  0 Dec03 ?        00:00:00 [cpu1_hotplug_th]
root         4     2  0 Dec03 ?        00:00:05 [ksoftirqd/0]
root         7     2  0 Dec03 ?        00:00:00 [migration/0]
root         8     2  0 Dec03 ?        00:00:00 [migration/1]
root        10     2  0 Dec03 ?        00:00:02 [ksoftirqd/1]
root        11     2  0 Dec03 ?        00:00:00 [khelper]
root        12     2  0 Dec03 ?        00:00:00 [kworker/u:1]
root       230     2  0 Dec03 ?        00:00:00 [sync_supers]
root       232     2  0 Dec03 ?        00:00:00 [bdi-default]
root       234     2  0 Dec03 ?        00:00:00 [kblockd]
root       240     2  0 Dec03 ?        00:00:00 [ata_sff]
root       251     2  0 Dec03 ?        00:00:00 [khubd]
root       257     2  0 Dec03 ?        00:00:00 [md]
root       280     2  0 Dec03 ?        00:00:00 [rpciod]
root       293     2  0 Dec03 ?        00:00:01 [kswapd0]
root       294     2  0 Dec03 ?        00:00:00 [fsnotify_mark]
root       295     2  0 Dec03 ?        00:00:00 [nfsiod]
root       296     2  0 Dec03 ?        00:00:00 [crypto]
root       334     2  0 Dec03 ?        00:00:00 [scsi_eh_0]
root       337     2  0 Dec03 ?        00:00:00 [scsi_eh_1]
root       340     2  0 Dec03 ?        00:00:00 [kworker/u:2]
root       351     2  0 Dec03 ?        00:00:00 [comcerto_spi.1]
root       353     2  0 Dec03 ?        00:00:00 [comcerto_spi.0]
root       402     2  0 Dec03 ?        00:00:08 [btn_t]
root       412     2  0 Dec03 ?        00:00:09 [a3gblink_t]
root       418     2  0 Dec03 ?        00:00:00 [scsi_eh_2]
root       419     2  0 Dec03 ?        00:00:23 [usb-storage]
root       435     2  0 Dec03 ?        00:00:11 [kworker/0:2]
root       447     2  0 Dec03 ?        00:00:01 [md1_raid1]
root       449     2  0 Dec03 ?        00:00:00 [kjournald]
root      2082     1  0 Dec03 ?        00:00:00 udevd --daemon
root      2219     2  0 Dec03 ?        00:00:03 [kworker/1:2]
root      2511     2  0 Dec03 ?        00:02:45 [pfe_ctrl_timer]
root      2563  2082  0 Dec03 ?        00:00:00 udevd --daemon
root      2566  2082  0 Dec03 ?        00:00:00 udevd --daemon
root      4152     1  0 Dec03 ?        00:00:00 /sbin/rpcbind -w
root      4427     1  0 Dec03 ?        00:00:00 dhclient -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0
root      4699     1  0 Dec03 ?        00:00:01 /usr/sbin/rsyslogd -c5
root      4773     1  0 Dec03 ?        00:00:04 /usr/sbin/apache2 -k start
root      4803     1  0 Dec03 ?        00:00:00 /sbin/mdadm --monitor --pid-file /run/mdadm/monitor.pid --daemonise --scan --syslog
root      5257     1  0 Dec03 ?        00:00:34 /usr/local/bin/upnp_nas_device -webdir /var/local/upnp_nas_device -desc nasdevice.xml
root      5260     2  0 Dec03 ?        00:00:00 [jbd2/sda4-8]
root      5271     2  0 Dec03 ?        00:00:00 [ext4-dio-unwrit]
root      5948     1  0 Dec03 ?        00:00:04 /usr/sbin/ifplugd -i eth0 -q -f -u0 -d5 -w -I
root      5992     1  0 Dec03 ?        00:00:00 /usr/local/bin/wd-btnd /dev/input/button system 4 /usr/local/sbin/resetButtonAction.sh
www-data  6556  4773  0 Dec03 ?        00:00:10 /usr/sbin/apache2 -k start
root      6670     2  0 Dec03 ?        00:00:23 [knetatop]
root      6678     1  0 Dec03 ?        00:00:22 /usr/bin/atopacctd /tmp/atopacct
root      6740     1  0 Dec03 ?        00:00:00 /usr/sbin/sshd
root      6773     1  0 Dec03 ?        00:00:00 /bin/sh /usr/local/sbin/monitorTemperature.sh
root      6832     1  0 Dec03 ?        00:01:44 /bin/bash /usr/local/sbin/monitorio.sh
root      6991     2  0 Dec03 ?        00:00:00 [lockd]
root      6992     2  0 Dec03 ?        00:00:00 [nfsd]
root      6993     2  0 Dec03 ?        00:00:00 [nfsd]
root      6994     2  0 Dec03 ?        00:00:00 [nfsd]
root      6995     2  0 Dec03 ?        00:00:00 [nfsd]
root      6996     2  0 Dec03 ?        00:00:00 [nfsd]
root      6997     2  0 Dec03 ?        00:00:00 [nfsd]
root      6998     2  0 Dec03 ?        00:00:00 [nfsd]
root      6999     2  0 Dec03 ?        00:00:00 [nfsd]
root      7003     1  0 Dec03 ?        00:00:00 /usr/sbin/rpc.mountd --manage-gids
root      7048     1  0 Dec03 ?        00:00:02 /usr/sbin/nmbd -D
root      7052     1  0 Dec03 ?        00:00:01 /usr/sbin/smbd -D
root      7054  7052  0 Dec03 ?        00:00:00 /usr/sbin/smbd -D
root      7085  7052  0 Dec03 ?        00:00:00 /usr/sbin/smbd -D
root      7102     1  0 Dec03 ?        00:00:00 /usr/sbin/winbindd
root      7106  7102  0 Dec03 ?        00:00:00 /usr/sbin/winbindd
root      7215     1  0 Dec03 ?        00:00:00 /usr/local/bin/mDNSResponderPosix -b -f //etc/nas/mDNSResponder.conf -P /var/run/mDNSResponder.pid
root      7718     1  0 Dec03 ?        00:00:00 /usr/local/bin/lld2d eth0
root      7748     1  0 Dec03 ?        00:00:49 /usr/local/bin/wdnotifier
root      7825     1  0 Dec03 ?        00:00:00 /usr/local/bin/wdAutoMounter
root      8048     2  0 Dec03 ?        00:00:00 [ufsd_sdb2]
root      8206     1  0 Dec03 ttyS0    00:00:00 /sbin/getty -L ttyS0 115200 vt100
root      8475     1  0 16:01 ?        00:00:40 /usr/bin/atop -a -w /var/log/atop/atop_current 60
root      8512     1  0 Dec03 ?        00:00:03 /usr/sbin/netatalk -F /etc/netatalk/afp.conf
root      8513  8512  0 Dec03 ?        00:00:00 /usr/sbin/afpd -d -F /etc/netatalk/afp.conf
root      8514  8512  0 Dec03 ?        00:00:00 /usr/sbin/cnid_metad -d -F /etc/netatalk/afp.conf
www-data 11932  4773  0 Dec03 ?        00:00:06 /usr/sbin/apache2 -k start
www-data 13262  4773  0 Dec03 ?        00:00:04 /usr/sbin/apache2 -k start
root     13649  6740  0 Dec03 ?        00:00:09 sshd: root@pts/0
root     13712 13649  0 Dec03 pts/0    00:00:00 -bash
nobody   14719  7052  0 17:49 ?        00:00:12 /usr/sbin/smbd -D
www-data 18321  4773  0 18:36 ?        00:00:01 /usr/sbin/apache2 -k start
root     19930  6773  0 18:54 ?        00:00:00 sleep 1800
root     20381     1  0 00:30 ?        00:00:01 /usr/sbin/cron
root     20476     2  0 19:00 ?        00:00:00 [kworker/1:1]
root     20663     2  0 19:01 ?        00:00:00 [flush-9:1]
root     21214  6832  0 19:07 ?        00:00:00 /bin/bash /usr/local/sbin/monitorio.sh
root     21215 21214  0 19:07 ?        00:00:00 /bin/bash /usr/local/sbin/getSmartTestStatus.sh
root     21216 21214  0 19:07 ?        00:00:00 awk {print $1}
root     21217 21215  0 19:07 ?        00:00:00 /bin/bash /usr/local/sbin/getSmartTestStatus.sh
root     21228 13712  0 19:07 pts/0    00:00:00 ps -eaf
root     30532     2  0 13:02 ?        00:00:01 [kworker/0:1]

S98user-start file:

/etc/rc2.d/S85wdmcserverd stop
/etc/rc2.d/S86wdphotodbmergerd stop
/etc/rc2.d/S20restsdk-serverd stop
/etc/rc2.d/S84itunes stop
/etc/rc2.d/S85twonky stop
mount -o remount,noatime,nodiratime /dev/root /

#42

Are you using a mac PC. If not you don’t need netatalk. If you are not using nfs mounted file system. You don’t need nfs.
Winbind is a program that allows users in a heterogeneous network to log in using workstations that have either Unix or Windows NT operating systems. The program makes workstations using Unix functional in NT domains, by making NT appear to look like Unix to each Unix workstation.


#43

I have a few macs and a few PCs. I use NFS to stream to my WDTV. I could probably get away with disabling Winbind though, maybe? Iol. I’m not sure, but I could try disabling a few more services. The sleep times are actually much better than they were (7 second wake up was ridiculous) but they are still pretty bad. Under no normal usage would you be waking up a drive every 30 minutes on a desktop or server, so I’d rather just keep the thing spinning until it dies.

I figure if it’s waking up every 20 minutes or so, it COULD get a little better, but it won’t get to 5 hours without being isolated on it’s own network (because that’s why I purchased a NAS). They should really just disable the sleep function all together and call it a day.


#44

The seven second wake ups seem to be after the system is busy like at 03:00 am. During this busy time
the system cache is flushed. As soon as the system puts the disk to sleep some process needs to access an inode or a code segment that has been flushed. So it goes to disk which wakes it up. After looping thru the code for a few minutes all of the data needed to run has been cached. Now the system does not need to access the disk.


#45

Not sure what’s waking up my disk every 20 to 30 minutes though. I do have
backups taking place on it and media streaming though, so it could be
anything.


#46

It is difficult to determine what is causing the disk to wake up. Here is script I call checkgen1.sh. It sleeps for 4 seconds then checks /proc/diskstats to see is any disk activity has occurred. If it has it then does a find to list those files that have been accessed in the last minute. Since it wakes up every 4 minutes it will display the same file names during that minute. You just need to run it for a couple of minutes if the system is not sleeping. If the system is sleeping you can let it run a little longer. If you are using putty turn on logging. So that it will save the output.

file 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


Nach so viel Jahren Standby Problem weg?
#47

If you use Firmware Release 04.05.00-320 (11/28/2017), I wonder how WD Mycloud sleep and wake up. Thank you


#48

I’m not using Firmware Release 04.05.00-320 (11/28/2017). Right no my device is not sleeping much. So
I’m troubleshooting the sleep problem again.


#49

Thank you for answer.


#50

I have this option disabled actually since the beginning - this unit sits in the study - and judging by experience of others I don’t think I’m missing anything here.


#51

Thank you for answer. So the drive is sleeping for a long time? Which
version of firmware do you use?


#52

No, my drive does not go to sleep at all - or at least it’s set up this way.

I am on 4.05.00-320, obviously.


#53

Thank you.


#54

Interesting when I run that code script (after fixing I hope the characters the site is stripping out or converting) I get the following entries pretty consistently.

/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys

Raw dump (with some text redacted) of the script being run for several minutes.

15-46-03  sda1 1129594 33912 sda2 1111370 33912 sda3 1199488 1114752 sda4 8847562 1405672 sda5 1408    0 sda6 1408    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
/DataVolume/shares/redacted/checkgen1.sh
/nfs/redacted/checkgen1.sh
15-46-49  sda1 28776   16 sda2 -43286 -1080824 sda3 -7648074 -284520 sda4 8913626 1405752 sda6 1024    0 sda7  384    0 
/tmp
/tmp/browse.dat
/tmp/external_share_size
/tmp/share_size
/tmp/minutes_since_disk_access
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
/DataVolume/shares/redacted/checkgen1.sh
/nfs/redacted/checkgen1.sh
15-47-35  sda1 1160    0 sda2 -23982 -1087224 sda3 -7715546 -280504 sda4 8980082 1405752 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
15-48-19  sda1 25696   16 sda2 -19086 -1091304 sda3 -7779058 -275640 sda4 9046322 1405752 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
15-49-02  sda1 61408   16 sda2 -14478 -1096152 sda3 -7844658 -272824 sda4 9110050 1405752 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
15-49-45  sda1 79960    0 sda2 -2790 -1098968 sda3 -7908386 -251320 sda4 9174610 1405752 sda6 1024    0 sda7  384    0 
/tmp/atopacct/pacct_source
/var/log/atop/atop_current
/proc
/sys
15-50-29  sda1 101752   16 sda2 14882 -1120456 sda3 -7969874 -249400 sda4 9239194 1405752 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
15-51-14  sda1 121944   16 sda2 20290 -1122360 sda3 -8032794 -248632 sda4 9299378 1405752 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
15-51-58  sda1 158312   16 sda2 37322 -1123112 sda3 -8089138 -246968 sda4 9360954 1405752 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
15-52-40  sda1 154664    0 sda2 52490 -1124776 sda3 -8150714 -246968 sda4 9421402 1405752 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
15-53-25  sda1 174792   16 sda2 61530 -1124760 sda3 -8211162 -246968 sda4 9484538 1405752 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
15-54-08  sda1 172744   16 sda2 103162 -1124744 sda3 -8274298 -246968 sda4 9545482 1405752 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
15-54-51  sda1 136056    0 sda2 135346 -1124744 sda3 -8333194 -246968 sda4 9605706 1405752 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
15-55-35  sda1 139384   16 sda2 143586 -1124728 sda3 -8386634 -246328 sda4 9668530 1405752 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
15-56-18  sda1 136928   16 sda2 178658 -1125352 sda3 -8449458 -245816 sda4 9729570 1405752 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
15-57-00  sda1 95944    0 sda2 220282 -1125864 sda3 -8510498 -245432 sda4 9789658 1405752 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

#55

I think the files external_share_size share_size minutes_since_disk_access are used by the monitorio script
pacct_source atop_current is used by atop. I don’t think these files are causing a sleep problem.
The msg.sock file was causing problems in the past and was solved by createing a tmpfs.
Right now I’m leaning towards samba being the problem again. I found on my system that /etc/samba/smbpasswd
and /tmp/browse.dat files are being updated frequently. I’m now testing the system with samba stopped.
Today my system slept 56 second from 11:50am to 5:00pm.


#56

Any progress with sleep issue?


#57

Check out my post in this thread. In it I listed the things that made a difference for me - and my drive had hardly ever slept…

You can learn a lot by examining the logs as I describe there…

Good luck with it!


#58

Hi guys,
I’ve just upgraded to the latest V4…320 firmware. Everything seems to work as previously despite the mass of error, warnings, do not match messages, … in the update.log.
Also, the “tmp/dynamicconfig.ini: no such file or directory” is back again. I guess the update or the reboot has removed my manual created file.
I’ll run the sleeptime.sh later on because the system is rebooted since only 2 hours ago and reports 100% wakeup time now.


#59

We’ve been discussing the sleep issues that continue even with this latest firmware in this thread:

It appears, at least for me, the following code that I put in the S98user-start file seems to fix the missing file error messages in the log file(s) for the dynamicconfig.ini file.

touch /tmp/dynamicconfig.ini
cp /var/www/rest-api/config/dynamicconfig.ini /tmp/dynamicconfig.ini

#60

Thanks, I will try this also because just an empty ini-file (touch) causes the restsdk-serverd process to crash.