[GUIDE] Transmission 2.82

I’ve had no problems accessing the WD My Cloud dash…  I havent tried to retro-fit to v3, however; still working with v4.

Since the package is really a ‘.deb’ file, you may be able to ssh install it (???) Murky waters, there… try doing a reboot for your dash, first.  

Ouglee wrote:

I’ve had no problems accessing the WD My Cloud dash…  I havent tried to retro-fit to v3, however; still working with v4.

 

Since the package is really a ‘.deb’ file, you may be able to ssh install it (???) Murky waters, there… try doing a reboot for your dash, first.  

You think you can make Transmission work with v4? I’ll be looking forward to it. MiniDLNA displays almost the same error, so I guess same fix may apply…

Dashboard seems totally broken (error 500). Several other users are mentioning the same issue. Hopefuly, WD will come up with some fix.

Why the *** did I have to update it? :frowning:

Try closing your web browser and re-opening it.  I know, sounds shady, but it sometimes works…

I fixed it by refrashing firmware.

It made me available to access web UI.

However, transmission and minidlna are still not working.

You can try this as follwing this command on SSH :

# /usr/local/sbin/updateFirmwareFromFile.sh /DataVolume/shares/Public/sq-030401-230-20140415.deb

Before run this command, you should download and unzip like this.

wget  http://download.wdc.com/nas/sq-030401-230-20140415.deb.zip

unzip  http://download.wdc.com/nas/sq-030401-230-20140415.deb.zip

I will try firmware downgrade…

I’m having little luck…

Nothing in the logs.  /usr/bin/transmission-daemon, when run from shell, results in an immediate ‘killed’.  (sigh)  There is some sort of  whitelist of programs installed…?  No matter what app you put in, you get ‘killed’…!

I tried to downgrade firmware to 230 version(04/15/2014), but I couldn’t.

MyCloud said that the older firmware was “invalid firmware package.”

However, when i put the latest firmware, MyCloud accpeted it.

It seems like that it doesn’t allow to downgrade firmware. :frowning:

kdh812 wrote:

I fixed it by refrashing firmware.

It made me available to access web UI.

However, transmission and minidlna are still not working.

 

You can try this as follwing this command on SSH :

 

# /usr/local/sbin/updateFirmwareFromFile.sh /DataVolume/shares/Public/sq-030401-230-20140415.deb

 

Before run this command, you should download and unzip like this.

 

wget  http://download.wdc.com/nas/sq-030401-230-20140415.deb.zip

unzip  http://download.wdc.com/nas/sq-030401-230-20140415.deb.zip

 

I will try firmware downgrade…

Were you able to downgrade? I always end up with:

updateFirmwareFromFile.sh:07/10/14 01:23:51:: ( /DataVolume/shares/Public/sq-030401-230-20140415.deb )
updateFirmwareFromFile.sh:07/10/14 01:23:51:upgrade start: /DataVolume/shares/Public/sq-030401-230-20140415.deb
updateFirmwareFromFile.sh:07/10/14 01:23:51:check_size=
updateFirmwareFromFile.sh:07/10/14 01:23:52:version_current=040000607
updateFirmwareFromFile.sh:07/10/14 01:23:52:version_newfile=030401230
updateFirmwareFromFile.sh:07/10/14 01:23:52:package_newfile=sq
updateFirmwareFromFile.sh:07/10/14 01:23:52:master_package_name=sq
updateFirmwareFromFile.sh:07/10/14 01:23:52:master_package_new=sq
updateFirmwareFromFile.sh:07/10/14 01:23:52:update_container=
Error fw_update_status: failed 200 "invalid firmware package"
updateFirmwareFromFile.sh:07/10/14 01:23:52:failed 200 "invalid firmware package"

Seems updateFirmwareFromFile.sh has several controls in place. Including:

# ITR#34229: don't allow down rev code to be applied
    # -but allow 'patch updates" with any version
    if [-z "${update_container}"] && ["${vnew}" -lt "${vnow}"]; then
            error="failed 200 \"invalid firmware package\""

Lines 256 through 259 of updateFirmwareFromFile.sh:

# if [-z "${update_container}"] && ["${vnew}" -lt "${vnow}"]; then
    # error="failed 200 \"invalid firmware package\""
    # pre-update_error $error
    # fi

 Aaand back to previous firmware. :wink:

(of course, I don’t take responsability if your disk crashes, your girlfriend leaves you or your nany goes homicidal)

sigh<

Softbricked mine while fuddling around… gonna have to rip it apart.  Might as well rollback to v3.

Its obvious that WD doesn’t want us having the ‘features’ of the more expensive mirror/ex2/ex4 models (which allow the installation of transmission via the dashboard).  I had every app I installed via apt-get auto-killed whenever I would try and run it, and was no closer to figuring out HOW it was being done when I borked the **bleep** out of it.  (which, honestly, I’m not sure how I even did…  I made no changes that would result in that)

Add to that the safeguard against rollbacks, and the message is clear; I’m only surprised they didn’t gank ssh while they were at it.

Cest la vie.  I’ll unbrick it with v3 and wait for someone smarter and/or wider than myself (or your average marmuset) to figure out how to get non-factory processes to function properly. 

umm. Wiser.  Dammit.

Ouglee wrote:

sigh<

 

Softbricked mine while fuddling around… gonna have to rip it apart.  Might as well rollback to v3.

 

Its obvious that WD doesn’t want us having the ‘features’ of the more expensive mirror/ex2/ex4 models (which allow the installation of transmission via the dashboard).  I had every app I installed via apt-get auto-killed whenever I would try and run it, and was no closer to figuring out HOW it was being done when I borked the **bleep** out of it.  (which, honestly, I’m not sure how I even did…  I made no changes that would result in that)

 

Add to that the safeguard against rollbacks, and the message is clear; I’m only surprised they didn’t gank ssh while they were at it.

 

Cest la vie.  I’ll unbrick it with v3 and wait for someone smarter and/or wider than myself (or your average marmuset) to figure out how to get non-factory processes to function properly. 

Ouch. What did you try to do? I just decided to downgrade… Is SSH dead as well?

1 Like

Wish I knew! Gonna let it sit overnight. It’ll either recover/ reboot or it will remain stubborn. I’ll fix it tomorrow

And yes, ssh is unresponsive, too. ;(

Thanks  JoaquinAR

Your a life saver, I should of read Transamission issues before upgrading to V4 of firmware. 

As stated before, V4 firmware blocks new version’s or new programs from running within mycloud. 

And worse still, if you try to install transmission into a V4 firmware it stuffs-up the apache server such that

when you reboot the nas it still not startup… that is, no WD GUI UI is avaiable (real bad news), lucky ssh was available.

Solution as provided by  JoaquinAR is to reverted back to V3.4 which involves downloading the firmware, and altering the upgrade script.

Some tense moments today for sure… I will not be upgrading the firmware to V4 until I’m able to run transmission again.

So, for the moment transmission can’t be installed on the drive ?

Brilliant!!

Thank you so much,

My Cloud decided to update at 05:30 this morning and everything went **bleep** up - I can confirm by  hashing lines 256/259 will indeed allow you to revert to an older firmware.

thanks again :smiley:

Can someone please make a detailed guide for downgrading the firmware? 

 

(of course, I don’t take responsability if your disk crashes, your girlfriend leaves you or your nany goes homicidal)

Ok, Ill walk through the process of downgrading a My Cloud as I’ve had to unexpectedly experience this issue today after an automatic update over night!.

The info needed is already in this thread;

 As posted by kdh812

“You can try this as following this command on SSH :

# /usr/local/sbin/updateFirmwareFromFile.sh /DataVolume/shares/Public/sq-030401-230-20140415.deb

Before run this command, you should download and unzip like this.

wget  http://download.wdc.com/nas/sq-030401-230-20140415.deb.zip

unzip  http://download.wdc.com/nas/sq-030401-230-20140415.deb.zip

Thank you for the comment, you gave me the first of the info required; running the below in a terminal…

/usr/local/sbin/updateFirmwareFromFile.sh /DataVolume/shares/Public/sq-030401-230-20140415.deb

Lets break this down;

/usr/local/sbin/updateFirmwareFromFile.sh

This is the script My Cloud uses to install new firmware, (we will be using this later)

/shares/Public/sq-030401-230-20140415.deb

The above is the location of the firmware file,

Right now the My Cloud install script will not allow you to downgrade, as confirmed by JoaquinAR, with the following output when trying to downgrade.

“updateFirmwareFromFile.sh:07/10/14 01:23:51:: ( /DataVolume/shares/Public/sq-030401-230-20140415.deb )

updateFirmwareFromFile.sh:07/10/14 01:23:51:upgrade start: /DataVolume/shares/Public/sq-030401-230-20140415.deb

updateFirmwareFromFile.sh:07/10/14 01:23:51:check_size=

updateFirmwareFromFile.sh:07/10/14 01:23:52:version_current=040000607

updateFirmwareFromFile.sh:07/10/14 01:23:52:version_newfile=030401230

updateFirmwareFromFile.sh:07/10/14 01:23:52:package_newfile=sq

updateFirmwareFromFile.sh:07/10/14 01:23:52:master_package_name=sq

updateFirmwareFromFile.sh:07/10/14 01:23:52:master_package_new=sq

updateFirmwareFromFile.sh:07/10/14 01:23:52:update_container=

Error fw_update_status: failed 200 “invalid firmware package”

updateFirmwareFromFile.sh:07/10/14 01:23:52:failed 200 “invalid firmware package””

JoaquinAR again posted the final peace of the puzzle.

“Lines 256 through 259 of /usr/local/sbin/updateFirmwareFromFile.sh

    # if [-z “${update_container}”] && ["${vnew}" -lt “${vnow}”]; then    

    #         error=“failed 200 “invalid firmware package””    

    #         pre-update_error $error 

    # fi

Aaand back to previous firmware. 

The format above may be off, but what we need to do is include a hash (#) at the beginning of lines 256 through to 259 of the /usr/local/sbin/updateFirmwareFromFile.sh script;

Ok lets do that J

From the terminal type

nano /usr/local/sbin/updateFirmwareFromFile.sh

Locate the above code at lines 256 through to 259 and hash them out and save the file.

Upload the extracted firmware “sq-030401-230-20140415.deb” to a location on the My Cloud for example the Public directory. (/share/Public) ß on my device

Back to the terminal make sure you know the location to the downgrade file – in my case: /share/Public/ sq-030401-230-20140415.deb

Issue the final command:

/usr/local/sbin/updateFirmwareFromFile.sh /share/Public/ sq-030401-230-20140415.deb

This will initialise a downgrade to firmware version v03.04.01-230 –

Don’t panic this takes a few minutes with blinking lights – once complete (5-mins aprrox)

REMEMBER!! Turn off Auto Firmware update in settings J.

 your done:

if any doubts DONT DO THIS!! you have be warned!

2 Likes

Thank you for your feedback in this thread.

We have seen some users report that installing 3rd party applications through “apt-get” causes the WDMyCloud device to not function correctly.   For more information on this, we suggest users read the “Instructions to rebuild a Debian package” section of the WD-Readme.txt located within our GPL source package that can be downloaded here:

http://support.wd.com/product/download.asp?groupid=904&sid=233&lang=en

As a reminder, the following message is communicated to users when using SSH to access their WDMyCloud device:

Please note that modifying or attempting to modify this device outside the normal operation of the product voids your WD warranty.

 

Some users have asked how to reinstall the current firmware to stabilize their device.  Using SSH, the following commands can be issued, however, we recommend contacting WD Support ( http://support.wdc.com) if you are not comfortable issuing this command yourself.

updateFirmwareFromFile.sh /CacheVolume/updateFile.deb

1 Like