Linkstation Duo LS-WXL media server issue

[tejaswi]

Product: Linkstation Duo LS-WX2.0TL/RI
Firmware: 1.34

 

I recently upgraded the firmware from 1.3 to 1.34 and now am unable to view the contents of the media server on my Sony BDP-S570.

I had some issues with 1.3 previously where few of the folders were accessible. Some of the video files were not being streamed even though they were in MPEG-2 format. Setting the refresh interval to 15 mins & force refresh did not help.

 

I even tried restarting the media server after the firmware upgrade as well as rebooting the NAS, but without success.

 

Any help in resolving this is appreciated.

 

 

[hubertusw]

I'm facing the same problems. After I've updated my LinkStation Due to firmware 1.34 the MediaServer is not visible for the clients (Philips TV 37PFL8605) anymore. The does also not see the DNLA clients anywore. Unfortunately, I can't find the old firmware in order to do fallback. Is there any other option to get it working again?

 

Thanks in advance!

[tejaswi]

I went back to an older firmware (1.24) and it works. This is not the ideal solution, but what the heck. Atleast my media server is up & running.

I specifically bought this device for the media server capabilities and am very disappointed. Hoping to see this fixed soon

 

[hubertusw]

As there was no solution available and I could even find an older firmware version for a rollback I've investigeted the problem by myself.

 

After I've found a way to logon to my LinkStation Duo running firmware 1.34 I've found the following error messages in /var/log/messages:

 

login as: root
root@LS-WXLF88:~#
root@LS-WXLF88:~# vi /var/log/messages
- /var/log/messages 60/60 100%
Sep 15 23:03:04 LS-WXLF88 smbd[7637]:   getpeername failed. Error was Transport endpoint is not connected
Sep 15 23:03:04 LS-WXLF88 smbd[7637]: [2010/09/15 23:03:04, 0] lib/util_sock.c:write_data(562)
Sep 15 23:03:04 LS-WXLF88 smbd[7637]:   write_data: write failure in writing to client 192.168.69.4. Error Connection reset by pe
Sep 15 23:03:04 LS-WXLF88 smbd[7637]: [2010/09/15 23:03:04, 0] lib/util_sock.c:send_smb(761)
Sep 15 23:03:04 LS-WXLF88 smbd[7637]:   Error writing 4 bytes to client. -1. (Connection reset by peer)
Sep 15 23:03:14 LS-WXLF88 file_smb[7638]: [User:hubertus(192.168.69.4)] File Open(Read) /mnt/array1/www/htdocs/index.php
Sep 15 23:05:58 LS-WXLF88 syslogd 1.5.0: restart.
Sep 15 23:05:58 LS-WXLF88 logchkd[1683]: 000 : log file (/var/log/lighttpd.webui.access.log) is newly rotated
Sep 15 23:06:12 LS-WXLF88 twonky: Media Server script is begun. type=restart
Sep 15 23:06:12 LS-WXLF88 twonky: stop Media Server
Sep 15 23:06:16 LS-WXLF88 twonky: Media Server begins starting. contentbase=/mnt/array1/share diskinfo=/mnt/array1
Sep 15 23:06:27 LS-WXLF88 dbrescan[10489]: dbrescan: start sleep [3600]
Sep 15 23:06:28 LS-WXLF88 twonky: Media Server does not start yet.[1] Retry call ...
Sep 15 23:06:30 LS-WXLF88 twonky: Media Server does not start yet.[2] Retry call ...
Sep 15 23:06:32 LS-WXLF88 twonky: Media Server does not start yet.[3] Retry call ...
Sep 15 23:06:35 LS-WXLF88 twonky: Media Server does not start yet.[4] Retry call ...
Sep 15 23:06:37 LS-WXLF88 twonky: Media Server does not start yet.[5] Retry call ...
Sep 15 23:06:39 LS-WXLF88 twonky: Media Server does not start yet.[6] Retry call ...
Sep 15 23:06:41 LS-WXLF88 twonky: Media Server does not start yet.[7] Retry call ...
Sep 15 23:06:43 LS-WXLF88 twonky: Media Server does not start yet.[8] Retry call ...
Sep 15 23:06:45 LS-WXLF88 twonky: Media Server does not start yet.[9] Retry call ...
Sep 15 23:06:47 LS-WXLF88 twonky: Media Server start was failed in the start.
Sep 15 23:06:50 LS-WXLF88 mt-daapd[10865]: Firefly Version svn-1586: Starting with debuglevel 2
- /var/log/messages 28/60 46%
...

 

The above error of the media server can be easily reproduced. You just have to execute the startup script /etc/init.d/twonky.sh or restart the server from the web interface. The problem occurs with both version 1.33 and 1.34.

 

I would expect the vendor to provide a bugfix, as this is obviously a configuration bug in firmware release younger than 1.24.

 

 

[gantcliff]

Interesting investigation, well done.

 

The media server issues have been discussed a lot on here but no reliable solutions found apart from using an earlier version of the firmware.  If you haven't already, make sure you vote for this idea to ensure that the media server problems come to the attention of the firmware developers.

[hubertusw]

Finally, I've found a solution for the problem: When updating the firmware (e.g. to 1.34)  the LinkStation also downloads the latest version of the twonky media server automatically from the internet. It appears as if the most recent version of the twonky server does not work with newer versions of the LinkStation firmware anymore.

 

Solution: Update of firmware while being disconnected from the internet. By cutting the connection to the internet the firmware update script cannot download the latest twonky media server and thus takes the given one which works fine.

 

See also (in German): http://forum.discountnetz.com/buffalo-linkstation-duo/probleme-mit-media-server-nach-firmware-update-auf-1-34-t588-10.html

 

But, do not press the button 'Update DTCP-IP function' afterwards, as this will update your twonky server with the latest version too.

 

I'd would need to revise my recent comment regaring the firmware requiring a bugfix. It's obvoiously the twonky server which is buggy. Neverthess, the firmware could be made a bit smarter by downloading only those versions of the twonky server which proofed to be working.

 

Good luck!

[hubertusw]

There is one thing I'd like to add.

 

The twonky media server is being updated automatically upon start/restart of the LinkStation and the Twonky version from firmware 1.34. is being replaced by latest not working version. To avoid this the script '/etc/init.d/twonky.sh needs to bemodified.

 

By disabling the call of 'do_majishanzu ${1} ${2} ${3}'  in line 250 through inserting a '#' at the beginning of the line the automatic update procedure will not be called anymore.

 

Root access to the device can be easily achieved as described here: http://buffalo.nas-central.org/wiki/Category:LS-WXL#Gain_Root_Access

 

Good luck!

[ndg_uk]

How did you manage to roll the firmware back to 1.24?  I tried following the instructions on the sticky (http://forums.buffalotech.com/t5/Storage/FAQ-3-of-5-TFTP-boot-procedure-please-read-this/td-p/11015) but no joy.

 

Any help would be appreciated!

[tejaswi]

The instructions can be found @ http://forums.buffalotech.com/t5/Storage/FAQ-2-of-5-Force-Firmware-update-procedure-please-read-this/td-p/11011

[Unhappy09]

Hubertusw, I am not trying to disagree with you but I dont think that updating the firmware installs the latest version of Twonky. I think it might install a version of twonky but it is not the latest. We have been asking for an update to twonky on these forums for at least 1 year now and we are all still stuck with the a version that is at least 2-3 versions too old. So I think the problem still lies in the firmware 1.34. Alot of people have had issues with it, there seems to be problems with the media server and the web access when you update to 1.34.

 

***Maybe someone from Buffalo can confirm this, it would be interesting to find out if its true, since I have updated my firmware but my Twonky is still an old version. The latest version of twonky is 6.0.1 and I have 4.4.19 which like I said is very old. Does anyone have anything else apart from 4.4.19?

[hubertusw]

@Unhappy09: Please check /var/log/messages on your LinkStation. During start-up procdure you will find some rows inserted by a program called 'majishanzu'. Depending on whether there is an internet connection available or not this tool will update your twonky server to a version newer than 4.4.19_e2, which is the version that comes with firmware 1.34. Inserting a # at the beginning of line 250 in twonky.sh you can disable this call.

 

 

[hubertusw]

@ndg_uk: I did not roll back to 1.24 but to 1.33 which you can download from the vendor. In order to install 1.33 on a 1.34 you would need to update 'LSUpdater.ini' like this:

 

 

---------------------------------

[Application]
Title = BUFFALO LS-CHL / LS-XHL / LS-WXL / LS-WSXL Series Updater Ver.1.33
WaitReboot = 1200
WaitFormat = 600
WaitFileSend = 600

[Target]
ProductID = 0x00000011
ProductID2 = 0x00000012
ProductID3 = 0x00003006
ProductID4 = 0x00003007
Name = LinkStation

[Flags]
VersionCheck = 0
NoFormatting = 1

[SpecialFlags]
Force = 1
---------------------------------------------------

 

But, I newer saw the dialog with the different checkboexs titled 'Debug Mode' although I've also tried to switch into debug mode by adding a special flag 'debug = 1'. As it also works in normal mode this doesn't actually matter.

 

BTW: All data and configuration settings remain unchanged during firmware updates (1.34 -> 1.33, 1.33 -> 1.34).

 

[ndg_uk]

Thanks  hubertusw

 

Could you post the link where you downloaded 1.33 from?  I can only find 1.24

Thanks!

[hubertusw]

Here you go:

 

1.24 http://www.buffalo-technology.com/support/getfile/?LS-WXL-fw124.zip

 

1.33: http://www.buffalo-technology.com/support/getfile/?LS-%28W%29X_series-fw133.zip

 

1.34: http://www.buffalo-technology.com/support/getfile/?LS-%28W%29X_series-fw134.zip

 

Cheers

[ndg_uk]

Thanks!