New Release - My Book Live Duo Firmware Version 2.41.05-034 (2/28/13)

Further to my last post, the follwoing is the message I keep recieving when trying to access MBLD from my Mac:

  • Something wrong with the volume’s CNID DB, using temporary CNID DB instead.Check server messages for details. Switching to read-only mode.

What happens if you try access files using SMB?

@ ChasingAdonai The other day I created a custom firmware deb for  Techflaws of the WD forums so that he could downgrade his MBLDuo back to version 024006-048-20121206. His downgrade was 100% successful. All that I modified was the firmware control file that holds the version number to allow the MBLDUO to THINK it’s upgrading to a newer firmware when in fact it’s downgrading. The rootfs.img (OS partition file is untouched)

I have to say ahead of time that it worked for him, but if something goes wrong, I am NOT responsible. You downgrade of your own free will. That being said, here’s the link

DOWNLOAD REMOVED AS I DON’T WANT TO HARM ANYBODY’S DUO

 

If anybody REALLY wants it, PM me and I’ll hook you up but I’m NOT responsible for any damage done to your drive

Good point for being cautious. When the upgrade is performed a set of scripts are also run and there is no way to know how those post upgrade scripts will behave when they are changing stuff on an unexpected firmwaew version.

Just for all to keep this in mind.

Myron, you are absolutely correct. Preinstall and postinstall scripts are run upon the upgrade/downgrade from dashboard. I need to get ahold of Techflaw’s update.log file from /CacheVolume and see if it hit any snags on him (even though his downgrade was successful) I’ll try to get ahold of him and see if I can get that file…

The other thing to consider is that such a downgrade maybwork now and there may be no adverse affects, but that action may break something later on down the line.

nfodiz wrote:

@ ChasingAdonai The other day I created a custom firmware deb for  Techflaws of the WD forums so that he could downgrade his MBLDuo back to version 024006-048-20121206. His downgrade was 100% successful. All that I modified was the firmware control file that holds the version number to allow the MBLDUO to THINK it’s upgrading to a newer firmware when in fact it’s downgrading. The rootfs.img (OS partition file is untouched)

I have to say ahead of time that it worked for him, but if something goes wrong, I am NOT responsible. You downgrade of your own free will. That being said, here’s the link

http://www.mediafire.com/download.php?agn38gml211d821

@ChasingAdonai

Let me make this a little more official.  This is an open forum, and as such, we don’t try to control how you use your device, or what you do with it.  So, you must remember that it is your responsibility if something happens to your device.  WD won’t take sides in matters like this.  Also, before trying anything, always make sure that you have your data backed up. That way if you brick the device, you’re only looking at replacing it and not all your data.  Both nfodiz and Myron have been around for a while, and have helped a lot of other users.  So, I’m confident you’re in good hands.  But if they are hesitant about doing something, I would pay attention.  You might want to let nfodiz look at Techflaws logs before jumping on this.

Well said Bill… I am awaiting a response from Techflaws and will report back my findings.
I have a question for both yourself and Myron…
Would reinstalling the CURRENT firmware on his device from the dasbboard possibly remedy his issues? I have done this many many times on a MyBookLive with no adverse effects.
Just a nice clean factory OS with all settings intact.

nfodiz wrote:
Well said Bill… I am awaiting a response from Techflaws and will report back my findings.
I have a question for both yourself and Myron…
Would reinstalling the CURRENT firmware on his device from the dasbboard possibly remedy his issues? I have done this many many times on a MyBookLive with no adverse effects.
Just a nice clean factory OS with all settings intact.

That I don’t know.  But I don’t think it’s something we would recommend or support.  To be honest, doing a rollback could be problematic in and of itself.  You may end up with pieces of firmware left behind that could adversely affect the drive’s function.

[edit]

What I mean by it being something we don’t recommend, is trying to reinstall the previous firmware over the update firmware.  That’s problematic.  I don’t know if you even can reinstall current firmware over itself.  Doing resets may help, but doing a Factory Restore is data destructive, I believe. However, it still keeps the current firmware on the drive.

On the MBL you can reinstall the same version over itself. DUO may be different though…

@Bill_S send me a DUO to play with :slight_smile:

I’ll tear this thing apart in no time :stuck_out_tongue:

I went over Techflaws update.log with a fine toothed comb… The only error with upgrade vs downgrade in the log was…

Upgrade

[apache-php-webdav.preinst] 03/02/13 11:29:58: update 02.00.01-88851
Remove all non-device users
Delete apache user pwd for user=admin id=1
- deleting apache user admin in /etc/nas/apache2/auth/htpasswd
Deleting password for user admin

Downgrade

[apache-php-webdav.preinst] 03/27/13 14:18:36: update 02.00.01-88851
Remove all non-device users
Delete apache user pwd for user=admin id=1
- deleting apache user admin in /etc/nas/apache2/auth/htpasswd
User admin not found

No other errors present

Also I believe Techflaws used updateFirmwareFromFile.sh instead of the dashboard to do the downgrade

updateFirmwareFromFile.sh:03/27/13 14:14:23:upgrade start: /CacheVolume/DOWNGRADE.ap2nc-024006-048-20121206.deb
updateFirmwareFromFile.sh:03/27/13 14:14:23:check_size=
updateFirmwareFromFile.sh:03/27/13 14:14:23:version_current=024105034
updateFirmwareFromFile.sh:03/27/13 14:14:23:version_newfile=044006048
updateFirmwareFromFile.sh:03/27/13 14:14:23:package_newfile=ap2nc
updateFirmwareFromFile.sh:03/27/13 14:14:23:master_package_name=ap2nc
updateFirmwareFromFile.sh:03/27/13 14:14:23:master_package_new=ap2nc
updateFirmwareFromFile.sh:03/27/13 14:14:23:update_container=
(Reading database ...

So far everything is running fine for him, but there is always the possibility you could run into issues later on down the line with an upgrade as Bill_S and Myron have stated. But even then you could fix the drive by pulling disk A and running a debrick script from my guide.

And as always have a backup of a backup :wink:

http://community.wdc.com/t5/My-Book-Live-Duo/GUIDE-Debrick-a-MyBookLive-DUO/td-p/544860

The update.log file may not show anything or for a downgrade there is a process that would need to be done, but there is no code there so nothing logged.

What the firmware designers/assemblers have in mind when the firmware was assembled. Did they consider that there may be downgrades going on?

As always… Do it at your risk.

Agreed, I ran the postinstall and preinstall scripts through IDM Ultracompare and there are indeed quite a few differences between both sets of scripts. So just to be on that safe side I’m gonna pull the firmware down. If anybody REALLY wants it, PM me and I’ll hook you up but I’m NOT responsible for any damage done to your drive.

Thanks again Myron and Bill_S

I have two MBLDs and the one I’ve downgraded with nfodiz’s script is the one that’s not permanently in use so I can’t guarantee any anomalies won’t pop up later down the road. However, since the files on it weren’t irreplacable, I decided to take the plunge since I’m too much of a Linux newbie to manually install Midnight Commander and Pyload with that many unmet depencies. Personally I find it totally weird that a Lenny distribution would refer to Squeeze and Sid sources.

Bill_S wrote:
To be honest, doing a rollback could be problematic in and of itself.  You may end up with pieces of firmware left behind that could adversely affect the drive’s function. […] Doing resets may help, but doing a Factory Restore is data destructive

Which makes no sense whatsoever. I mean, when nfodiz can change this with a few modified script lines so that only the firmware partition is deleted, why not do it like this? I can imagine that rolling back a NAS is more complex than rolling back a WDTV but this just **bleep**.

To be honest, the best thing would be to buy one of these Raspberry PI computers and use that for all the exotic stuff. at least from a secury stand point if Transmission on the MBL or MBLD gets hacked then the NAD is compromised. On a Raspberry PI if it gets hacked, replace the image on the SD card with a clean image. If you configure something on the PI that bricks it, replace the SD card’s file system with a working image. Both operate on Debian Linux

Sure, but since I’m not part of any swarm with pyload, I’m not too worried about getting hacked. I’ve tried Transmission once and it got only half the speed (on the same torrent) I got when downloading with utorrent instead so I ditched it and (rarely) do torrents with my laptop instead.

Re-opened this thread for now.  New update was postponed.

Hi

      what was change in new version of firmware

Thank you

Bill,

Without sifting through seven pages in this thread: is there anything known about connection problems to personal shares in Windows7? Is there anything coming in this regard for the next release … and when can this release be expected?

Many thanks,

Roger

I don’t know, but the next release is out.