Firmware 2.30.165 Discussion

New firmware for the v2.x single bay My Clouds:
https://community.wd.com/t/new-release-my-cloud-firmware-versions-4-05-00-315-2-30-165-4-13-17/202231

Feel free to discuss below.

What’s new in Version 2.30.165!

Enhanced dashboard to fit all top menu items on one screen without scroll bar.
Enhanced SMB server (samba) to support Apple Time Machine protocol extensions.
Enhanced SMB server (samba) to operate using SMB-3 protocol by default.
Resolved critical security vulnerabilities.
Improved MyCloud Cloud connectivity across MyCloud web, mobile & client apps.
Improved directory browsing latency over AFP when device wakes up from standby.
Improved latency of displaying thumbnails on mobile & web app.
Added analytics for network connection configuration.
Resolved issue where analytics logs were not updated as expected.
Enhanced UPnP support to pass updated UPnP certification tests
Resolved issue of unable to connect macOS Sierra (v10.12) ssh client.
Resolved issue where extra shares were created on system restore.
Improved dashboard network graph's X-Axis to be at least 125 MB/s.
DLNA Media Server and iTunes configuration now also available under Apps.

Release Notes: http://support.wdc.com/download/notes/WD_My_Cloud_Firmware_Release_Notes_2.30.165.pdf?v=816

Firmware Release 2.30.165 (04/12/2017) Link: http://download.wdc.com/nas/My_Cloud_GLCR_2.30.165.bin

hmmmm the firmware doesn’t seem to be available… and when did you become the firmware announcer @Bennor?

No Update over the Air?

There is no link to this new firmware for version 4, only the old one released back in December.

MyCloud doesn’t report new firmware required. Not that I’d trust an OTA firmware upgrade; download and manual install for me…

Someone’s got to do it; WD don’t seem keen to…

Figured people would want to know and discuss in one place. :wink:

Shortly after I pulled the links yesterday the old links were back up, don’t know if it was a caching problem with my ISP as its happened before.

Same thing happened yesterday on my first gen My Cloud, auto update didn’t show a new firmware version available. Had to use the manual update to install the firmware from the download link I provided in the first gen firmware thread.

Even today (this morning) when trying to use the WD Support website to download the firmware it shows the December firmware for both first gen and second gen single bay My Cloud units. [Face Palm]

Perhaps like the updated firmware released for a couple of other units previously that were released then pulled, WD will be doing the same with the single bay firmware.

Also noticed this firmware announcement sticky at the top of the subforum AND the latest news and announcement section is now gone as well. Maybe this firmware was released too soon (again).

[face palm] indeed…

They never managed to take down the old v2 firmware notice sticky, so there have been two ‘latest firmware’ stickies in the thread list for months. They must try really hard to be that feckless…

Keep up the good work Bennor and as cpt_paranoia says,

@Bill_S popped in yesterday answering my IP questions alongside the firmware update announcement.

When I finally had the chance to try to get the OTA firmware update it was gone and came back here to see if I was seeing things and saw your announcement by itself and I thought I must have saw your announcement and you have taken over the job of firmware announcer. :stuck_out_tongue:

Things haven’t change around here, have they…

So… in regards to this new firmware update, although not available OTA but if you click on Bennors link that he provided, you will get the 2.30.165 FW.

  1. Has anyone tried it yet?
  2. Was the announcement pulled because it doesn’t work and the actual download was not suppose to be up? @Bill_S
  3. is it a virus???
  4. is WD being bought out by Seagate?
  5. ???

I tried it ,It looks legit
although It seems to have a issue with it not comming out of sleep mode now
I’m flashing back to 126 and see if I can replicate it

one step forward… one step backward…

Not sure what puts the disk to sleep. The Gen1 uses monitorio.sh to check
disk activity. On the Gen2 there is a script disk_monitorio.sh but it does not
get started.

These are the programs that turns sleep on/off and the amount of time before sleep.

I use this in my script to toggle sleep on.
drive_sleep.sh on

the following sets the amount of minutes before sleep of which I’m using 5 minutes.
hd_standby.sh 5

Waking the drive should be a natural occurrence because monitorio.sh use to be in a loop waiting for the drive to have activity to reset its count. Now the program to put it to sleep is a binary or perhaps just a compiled version of a script.

Only one entry in the crontab was causing the drive not to sleep in the previous version. Is it possible to someone dump here the crontab list from the latest temporary version?

This is the crontab on my gen2 2.21.126

0 3 * * * /usr/sbin/daily_log_upload.sh &
0 3 * * * /usr/sbin/traceroute_wd.sh &
*/30 * * * * /usr/sbin/quota_monitor &
*/10 * * * * /usr/sbin/rlog -s /usr/local/modules/files/syslog_rotate.conf
01 */8 * * * [ -f /etc/init.d/atop ] && /etc/init.d/atop rotate
30 0 * * * /usr/local/sbin/ssl_cert_job.sh start > /var/log/ssl_cert_cron.out 2>&1
58 2 * * * /usr/local/sbin/PullWdlogConfig.sh
30 0 * * 1 logwdmsg -e &
0 3 * * * logwdmsg -o &
01 3 * * * /usr/local/sbin/LogDataSize.sh
30 2 * * * /usr/sbin/stime&
0 3 * * * wd_crontab.sh&
0 4 * * * auto_fw -a -c&
0 0 * * * auto_clear_recycle_bin.sh &
30 3 * * * /usr/sbin/chk_wfs_download&
0 0 * * * random_check -s &
0 0 * * * expire.sh
34 17 * * * auto_fw -c 1 &

          • sysinfo_update.sh
            0 3 * * 1 getHddWhiteList.sh
            0 */4 * * * sync_tm_to_hd.sh &

Crontab in 2.30.165 looks the same to me:

0 3 * * * /usr/sbin/daily_log_upload.sh &
0 3 * * * /usr/sbin/traceroute_wd.sh &
*/30 * * * * /usr/sbin/quota_monitor &
0 */4 * * * /usr/sbin/rlog -s /usr/local/modules/files/syslog_rotate.conf
01 */8 * * * [ -f /etc/init.d/atop ] && /etc/init.d/atop rotate
30 0 * * * /usr/local/sbin/ssl_cert_job.sh start > /var/log/ssl_cert_cron.out 2>&1
58 2 * * * /usr/local/sbin/PullWdlogConfig.sh
30 0 * * 1 logwdmsg -e &
0 3 * * * logwdmsg -o &
01 3 * * * /usr/local/sbin/LogDataSize.sh
30 2 * * * /usr/sbin/stime&
0 3 * * * wd_crontab.sh&
0 4 * * * auto_fw -a -c&
0 0 * * * auto_clear_recycle_bin.sh &
30 3 * * * /usr/sbin/chk_wfs_download&
0 0 * * * random_check -s &
0 0 * * * expire.sh
0 1 * * * dropnasctl --chk_all_owner &
12 23 * * * auto_fw -c 1 &
* * * * * sysinfo_update.sh
0 3 * * 1 getHddWhiteList.sh
0 */4 * * * sync_tm_to_hd.sh &

rlog changed from */10 * * * * to 0 */4 * * *
auto_fw changed from 34 17 * * * to 12 23 * * *
dropnasctl was added

that’s the dropbox app, you can ignore it I guess.

The rlog was the one that prevented the previous version to go into sleep because it ran every 10 min and the drive should went into sleep after 10 min of inactivity. So they change from every 10 minute to every 4 hours. This should fix the drive not going into sleep mode.