New FW 4.00.00 upgrade results


#1

While I’m one of the owners who is running a very old FW (03.01.04-139). I’ve had zero issues with both of my WD drives.

For the people who’ve been having issues with previous FWs, if you pull the trigger and update to the latest sfotware. Please report back here with the issue you had and if it has been resolved in this update or not so that it can benefit others.

Thanks


#2

I didn’t really have problems before but I have noticed a few differences. 

I am using a UE55F7005 Samsung TV btw.

For streaming movies I noticed they load alot faster now, almost instant, so the performance seems to have gone up. Also now subtitles always work and I always have the option of chosing different subtitle files which didn’t always work previously.

One thing still on wishlist: I wish you were able to fastfoward when playing movies that is still not an option. I can use the arrow keys on the remote to kind of skip like 20secs ahead each click, and it seems to be abit faster now, but still not a prober way to do it.

That’s it so far.


#3

I updated without any hitch. The only problem i had with the previous fw was that Mobile connection streaming Video

= H+ or 4g connection wasnt all that smooth when playing mkv. This still remains with this update.

Uploading files, atm didnt notice any speed difference. 

If i come along some more info i will let u know.


#4

I updated today, hoping the new firmware would improve the speed of the WDMyCloud. No such luck. The thing is just as mind-numbingly slow as it was using the previous firmware.


#5

First reboot no issues. Second reboot got it stuck in intermitent white light.

Now I’m starting panicking… Any idea how to bring it back to life?

Edit: Turns out it wasn’t perma-stuck, but only for over 30 minutes and then got back to life… So if anyone else experiences this… Don’t kill yourself before that.  :P  But… issues continues.


#6

@rocketjsquirrel. Are you sure it’s not your network. Have you ruled out all other elements.


#7

Updated without a hitch, but no chance to test tonight.

Hopefully I’ll have some time tomorrow evening to do some testing.


#8

I updated to the new firmware. Now I cannot access the UI at all. Quickview does not see the drive. I can access the folderw within it fine, just not the UI


#9

bradbort wrote:

I updated to the new firmware. Now I cannot access the UI at all. Quickview does not see the drive. I can access the folderw within it fine, just not the UI

Same thing here: I’m still not able to access the dashboard.


#10

JoaquinAR wrote:

First reboot no issues. Second reboot got it stuck in intermitent white light.

 

Now I’m starting panicking… Any idea how to bring it back to life?

 

Edit: Turns out it wasn’t perma-stuck, but only for over 30 minutes and then got back to life… So if anyone else experiences this… Don’t kill yourself before that.  :P  But… issues continues.

It sounds like your drive may have initiated a fsck (similiar to chkdsk) and verified the file system prior to booting up.  This is a precautionary measure that the drive will take if for some reason it believes that it needs to.


#11

I am in same situation.

I can’t access web UI, but other functions are going well.


#12

daytrdr wrote:


It sounds like your drive may have initiated a fsck (similiar to chkdsk) and verified the file system prior to booting up.  This is a precautionary measure that the drive will take if for some reason it believes that it needs to.

Thanks for the info. Always good to know.

But now I’m still not able to access the Dashboard. :frowning:


#13

JoaquinAR wrote:


daytrdr wrote:


It sounds like your drive may have initiated a fsck (similiar to chkdsk) and verified the file system prior to booting up.  This is a precautionary measure that the drive will take if for some reason it believes that it needs to.


Thanks for the info. Always good to know.

 

But now I’m still not able to access the Dashboard. :frowning:

Yes I read your earlier post and wasn’t sure what to make of it…  Have you modified your drive at all via SSH?

I’m curious to see if the drive recovers at all, so please PM me if it does not.  I will have our support team contact you and we will figure out how to rectify the situation.


#14

daytrdr wrote:



Yes I read your earlier post and wasn’t sure what to make of it…  Have you modified your drive at all via SSH?

 

I’m curious to see if the drive recovers at all, so please PM me if it does not.  I will have our support team contact you and we will figure out how to rectify the situation.

No, I haven’t modified anything – yet. It just “woke up” from the update like that.

The shares are working and I can even see it using the WD Tools. I can also connect through SSH (yeah!). But the Dashboard is gone. And for what I read in the forum it seems I’m not alone.

Some support already contacted me through email and I replied back to him. Still no news, though. I’m thinking maybe applying the firmware update again, or even downgrading to previous firmware version. Since SSH and shares are working, it should be possible.


#15

I am having the same issue. I just upgraded the firmware. After reboot and waiting, things were not right. folders were not properly shared etc. So reboot again. Problems… I realize now I didn’t wait long enough. Now dashboard is not accesible. Twonky is up, fileshare is working, have SSH access. No dashboard. Hope we can fix this problem. 

Thanks!


#16

JoaquinAR wrote:


daytrdr wrote:



Yes I read your earlier post and wasn’t sure what to make of it…  Have you modified your drive at all via SSH?

 

I’m curious to see if the drive recovers at all, so please PM me if it does not.  I will have our support team contact you and we will figure out how to rectify the situation.


No, I haven’t modified anything – yet. It just “woke up” from the update like that.

 

The shares are working and I can even see it using the WD Tools. I can also connect through SSH (yeah!). But the Dashboard is gone. And for what I read in the forum it seems I’m not alone.

 

Some support already contacted me through email and I replied back to him. Still no news, though. I’m thinking maybe applying the firmware update again, or even downgrading to previous firmware version. Since SSH and shares are working, it should be possible.

Can you post the output of TOP?


#17

daytrdr wrote:


Can you post the output of TOP?

I didn’t see anything strange. But is not my area of expertise. :slight_smile:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
22483 root 28 8 10880 6848 4736 R 14.2 2.9 0:00.43 convert
 7358 root 20 0 34816 8640 3136 S 1.3 3.7 4:38.60 wdmcserver
22430 root 20 0 4544 3328 1280 R 0.7 1.4 0:00.26 top
 2371 root 20 0 0 0 0 D 0.3 0.0 0:23.06 pfe_ctrl_timer
 4070 root 20 0 32384 1984 1088 S 0.3 0.9 0:00.70 rsyslogd
 4258 root 20 0 52608 1408 768 S 0.3 0.6 0:02.54 apache2
    1 root 20 0 2752 768 512 S 0.0 0.3 0:08.64 init
    2 root 20 0 0 0 0 S 0.0 0.0 0:00.07 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 0:01.75 ksoftirqd/0
    5 root 20 0 0 0 0 S 0.0 0.0 0:01.44 kworker/0: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:01.78 kworker/1:0
   10 root 20 0 0 0 0 S 0.0 0.0 0:00.95 ksoftirqd/1
   11 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper
   12 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/u:1
   37 root 20 0 0 0 0 S 0.0 0.0 0:02.38 kworker/1:1
  214 root 20 0 0 0 0 S 0.0 0.0 0:00.04 sync_supers
  216 root 20 0 0 0 0 S 0.0 0.0 0:00.00 bdi-default
  218 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd
  224 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 ata_sff
  235 root 20 0 0 0 0 S 0.0 0.0 0:00.21 khubd
  241 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 md
  264 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 rpciod
  265 root 20 0 0 0 0 S 0.0 0.0 0:02.63 kworker/0:1
  277 root 20 0 0 0 0 S 0.0 0.0 0:06.68 kswapd0
  278 root 20 0 0 0 0 S 0.0 0.0 0:00.00 fsnotify_mark
  279 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 nfsiod
  280 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto
  318 root 20 0 0 0 0 S 0.0 0.0 0:00.15 scsi_eh_0
  321 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_1
  324 root 20 0 0 0 0 S 0.0 0.0 0:00.01 kworker/u:2
  335 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 comcerto_spi.1
  337 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 comcerto_spi.0
  370 root -2 0 0 0 0 D 0.0 0.0 0:01.29 btn_t
  380 root -2 0 0 0 0 S 0.0 0.0 0:00.00 a3gblink_t
  415 root 20 0 0 0 0 S 0.0 0.0 0:00.02 md1_raid1
  419 root 20 0 0 0 0 S 0.0 0.0 0:00.23 md0_raid1
  421 root 20 0 0 0 0 S 0.0 0.0 0:00.09 kjournald
 1955 root 20 0 4160 448 448 S 0.0 0.2 0:00.37 udevd
 2418 root 20 0 4096 448 448 S 0.0 0.2 0:00.02 udevd
 2421 root 20 0 4096 384 384 S 0.0 0.2 0:00.00 udevd
 3707 root 20 0 3328 1024 640 S 0.0 0.4 0:00.17 rpcbind

#18

this is mine. 

12862 root 20 0 4544 3712 1664 R 0.7 1.6 0:02.46 top                                           
 2372 root 20 0 0 0 0 D 0.3 0.0 0:09.72 pfe_ctrl_timer                                
 5462 root 20 0 71232 2432 1216 S 0.3 1.0 0:01.80 upnp_nas_device                               
 7682 root 20 0 37312 11m 2560 S 0.3 4.9 2:46.29 twonkyserver                                  
    1 root 20 0 2752 1024 768 S 0.0 0.4 0:08.48 init                                          
    2 root 20 0 0 0 0 S 0.0 0.0 0:00.07 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 0:01.04 ksoftirqd/0                                   
    5 root 20 0 0 0 0 S 0.0 0.0 0:00.88 kworker/0: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:00.67 kworker/1:0                                   
   10 root 20 0 0 0 0 S 0.0 0.0 0:00.89 ksoftirqd/1                                   
   11 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper                                       
   12 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/u:1                                   
   37 root 20 0 0 0 0 S 0.0 0.0 0:01.15 kworker/1:1                                   
  214 root 20 0 0 0 0 S 0.0 0.0 0:00.01 sync_supers                                   
  216 root 20 0 0 0 0 S 0.0 0.0 0:00.00 bdi-default                                   
  218 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd                                       
  224 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 ata_sff                                       
  235 root 20 0 0 0 0 S 0.0 0.0 0:00.21 khubd                                         
  241 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 md                                            
  264 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 rpciod                                        
  266 root 20 0 0 0 0 S 0.0 0.0 0:00.70 kworker/0:1                                   
  277 root 20 0 0 0 0 S 0.0 0.0 0:02.32 kswapd0                                       
  278 root 20 0 0 0 0 S 0.0 0.0 0:00.00 fsnotify_mark                                 
  279 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 nfsiod                                        
  280 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 crypto                                        
  318 root 20 0 0 0 0 S 0.0 0.0 0:00.15 scsi_eh_0                                     
  321 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_1                                     
  324 root 20 0 0 0 0 S 0.0 0.0 0:00.02 kworker/u:2                                   
  335 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 comcerto_spi.1                                
  337 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 comcerto_spi.0                                
  370 root -2 0 0 0 0 D 0.0 0.0 0:01.10 btn_t                                         
  380 root -2 0 0 0 0 S 0.0 0.0 0:00.00 a3gblink_t                                    
  415 root 20 0 0 0 0 S 0.0 0.0 0:00.02 md1_raid1                                     
  419 root 20 0 0 0 0 S 0.0 0.0 0:00.13 md0_raid1                                     
  421 root 20 0 0 0 0 S 0.0 0.0 0:00.06 kjournald                                     
 1955 root 20 0 4160 768 768 S 0.0 0.3 0:00.38 udevd                                         
 2418 root 20 0 4096 768 768 S 0.0 0.3 0:00.02 udevd                                         
 2419 root 20 0 4096 704 704 S 0.0 0.3 0:00.00 udevd                                         
 3707 root 20 0 3328 1344 960 S 0.0 0.6 0:00.07 rpcbind                                       
 3966 root 20 0 32384 2304 1216 S 0.0 1.0 0:00.31 rsyslogd                                      
 4193 root 20 0 52608 1728 1088 S 0.0 0.7 0:02.24 apache2                                       
 4292 root 20 0 3328 1472 960 S 0.0 0.6 0:00.02 mdadm                                         
 4720 root 20 0 5120 1344 640 S 0.0 0.6 0:00.01 dhclient

#19

Thanks JoaquinAR and gereksiz…

Can you please do the following:  

getSystemLog.sh

This will put a system log zip into /CacheVolume/

Then you can either SCP the file to your computer or move it to /shares/Public/ and copy it that way.  I have sent a PM to you both with my email address.

I am going to head home in the glorious southern-California traffic jam, but I will check your system logs when I get home.

Thanks.


#20

I updated the firmware via SSH and it is back. Probably I messed it up during the previous attempt. 

Thank you! Hope you make it home soon. It is 5am here.