Updated to Firmware 4.00.00-607 -> Dashboard not working (error 500)

Hey guys.

Just updated the thing:

Took about 10~15 minutes. First reboot was ok.

Second one got it stuck in intermitent white light. Took 30 minutes for it to finally boot while I was panicking over it.

After that, UI or shares were not responding. Using SSH I find that **bleep** wdmcserver is using 98% CPU so I shut it down. Now I’m able to access shares. But still unable to use the browser UI: Whenever you try access it, you end up with error 500 (“HTTP 500 Internal Server Error”).

Oh, and subsequent reboots will also take a huge amount of time.

So… System Restore pressing 40 seconds the back reset button?

Tried the 40 seconds reset but still nothing.

How can a do a “system restore” if I don’t have access to the UI? I thought that was the way.

JoaquinAR wrote:

 

So… System Restore pressing 40 seconds the back reset button?

Don’t go there just yet!

I tried this and I am having a very hard time struggling back to a usable state. Every single user action takes several minutes to complete, and I have not yet succeeded in logging back in to the drive. I am currently stuck re-creating my WDMyCloud.com login. It did not let me use my existing ID and is now just sitting there saying “Updating…”.

Well, I did go there but didn’t change a thing.

Seems that there is some kind of issue with the web app that Apache should be running. But I don’t have any idea on how to do some kind of system restore without having access to the dashboard of even if that might help.

I still have access to SSH and shares, so I’m still good… But I need to fix this.

Some help here would be appreciated.

Solution: re-run update through SSH.

# cd /DataVolume/shares/Public/# wget http://download.wdc.com/nas/sq-040000-607-20140630.deb.zip
# unzip sq-040000-607-20140630.deb.zip
# /usr/local/sbin/updateFirmwareFromFile.sh /DataVolume/shares/Public/sq-040000-607-20140630.deb

Cheers.

Edit: That is, of course, if you had SSH enabled. If not… I don’t know. :frowning:

1 Like

I’m able to access Twonky and my shares but not the main UI dashboard. I’m unable to make a connection on SSH, as I hadn’t turned it on. Is there a way to enable SSH other than through the dashboard?

hobbla wrote:

I’m able to access Twonky and my shares but not the main UI dashboard. I’m unable to make a connection on SSH, as I hadn’t turned it on. Is there a way to enable SSH other than through the dashboard?

No that I know of… Try to get in touch with support, maybe they have some way to “force” some automatic update.  :frowning:

I have same problems with extremely unresponsive Dashboard and all user interaction taking for ever. Can you explain this SSH process in a bit more detail please? I am assuming I will be able to turn it on at some point even if I have to wait for an hour!! Please help!

Think i’ll be sticking with my current FW for a bit longer…YIKES!

Is there an easy way to downgrade the firmware. Can access ssh fine but do not want v4 when it’s buggy and won’t allow the use of transmission anymore.

Awe DANG IT!!! Too late! Had it set to automaticly update!

 

Think the previous firmware is avail for dwnld somewhere on the site? It would be great if it is as simple as that.

Same issue…

After yesterday’s update torrent-daemon stopped working, made it reinstall (with errors). Tried reboot. After reboot dashboard stopped working.

After that made 40 second reset… Now I have no valid user and SSH access. Completely frustrated.

Now trying to re-execute 40 second reset and get to working credentials. Hopefully this will change something.

BR,

Jevgenijs

Doesn’t sound good, read through the Guide Transm** ission2.82** thread and you will find instructions on down grading the firmware if you so choose or re-apply the current V4 firmware in another recent thread, but both require ssh. Hopefully you can get ssh or the dashboard running.

Tried the steps in the guide and it didn’t work for me :frowning: luckily I enabled ssh beforehand though. Will have to keep trying.

Tried the steps in the guide and it didn’t work for me  :cry: luckily I enabled ssh beforehand though. Will have to keep trying.

Which part didn’t work? I had to manually download the 3.4 firmware from my web browser and then unzip it into the nas public folder as the wget command was killed by the abominbal V4 firmware (selinux?). Once the unzipped firmware was in place in the nas public folder/fileshare and I edited the  updateFirmwareFromFile.sh script and commented/hashed out the downgrade prevention and then ran the updateFirmwareFromFile.sh script on the firmware.

Yeah done all that unzipped it to public but when I point terminal to it I get a cannot find file message even though it’s the correct path

is it too much to ask for  a single file to use to roll back the firmware in the same way as an update?

1 Like

_ THANKFULLY  _, I haven’t had any problems…Hope all works out for everyone.

I applied the update again using Manual Update from the Dashboard. Gave it one night to sleep and catch up with content scanning. Everything seems to be working as earlier for me now. All user interactions are as it used to be (it was never superfast) and my internet connection seems to be holding up so far. I had a few conflicting port forwarding set up in my router and I removed them. So, fingers crossed for now. I am not going to be downgrading.