Linkstation LS-XHL Not connecting

[scruffymonkey]

We updated our Linkstation to version 1.34 and found that we could no longer stream files through our Xbox. We decided to try and roll-back the firmware to 1.31 and since then have been unable to access the NAS.

We are now getting a  rapid blue flashing power light when we switch on. We have tried pressing the Function button to get it into EM mode but it just then starts flashing with 6 red lights.

We have tried doing a TFTP boot but are not sure that we are using the correct version (LS.1 is the one we tried) We managed to get the message "blocks served" but then the drive would not be recognised by either LSUpdater or NAS Navigator.

It is accepting requests on 192.168.11.150 but we can't Ping it or make a connection with it.

Can anyone help us with this one as we seem to have done everything possible to get it working again!!!

 

P.S We have managed to gain access to it by physically removing the hard drive and connecting via Linux and have retrieved all the data from it.

 

Thanks in anticipation!

[Dustrega]

Try the TFTP again (the blocks being served is an indication you have the right software) and the a force firmware update with the "Rebuild Partition Table" option enabled (since you got the data backed up) with the 1.31 firmware.  However, it has been stated that XBOX is not a legitimate DLNA client, so it's not really something I would say is supported, but you did have it working previously so rolling back to 1.31 via the steps I just mentioned might work.  Good luck to you :)

[scruffymonkey]

Thanks for the reply.

 

We have tried forcing the firmware but it is saying "linkstation not found". We have even tried altering the updater so that it ignores version number and goes into Debug mode. Whatever we do, we can't get either Nas navigator or LSupdater to recognise the Linkstation.

[Dustrega]

Firewall software running at all?  Which OS?

[scruffymonkey]

We are running Bitdefender (disabled) but we have run the PC in safe mode with networking as well and this made no difference. The OS is Windows 7 Ultimate.

It's stressing us out as we have trawled the forums and tried everything!

 

[Dustrega]

With Bitdefender disabled it may have re-instated the Windows firewall (as it's disabled to prevent "firewall double up") but if you're able to make ping requests to the device the firmware updater should find it.  Provided, of course you have the correct updater.  Which version did you download?

[scruffymonkey]

Hi,

All virus checkers and firewalls have definately been disabled. We have been using the TFTP Boot Recovery LS-XL 1.00 . We weren't sure if this is the right one for the LS-XHL. We have read that the LS-CH is similar but the FTP site went down before we could download it.

[Dustrega]

The LS-CH TFTP boot is for the LS Live.  You have an LS Pro, but I was asking which firmware you have downloaded not the TFTP software.

[scruffymonkey]

Sorry! We have tried both the 1.31 and 1.33 from the UK section of the site.

[Dustrega]

Hmmmm, if the device is receiving ping requests it should be responding to a firmware update.  If all of the countermeasure software is disabled then the PC should be communicating to any ports necessary on the NAS without hindrance.  Furthermore, the TFTP boot serves the blocks required.  Is the device able to boot into http://forums.buffalotech.com/t5/Storage/FAQ-1-of-5-EM-Mode-boot-procedures-please-read-this/td-p/11008" target="_self" rel="nofollow">EM mode?

[scruffymonkey]

we are not sure that it is going into EM mode. We have followed the instructions in ths FAQ but we get the following:

Switch on

Rapid Blue flashing lights

Goes to 6 slow red flashing lights

Press down function button - goes back to rapid blue flashing lights.....this is when the tftp boot kicks in. After that. the lights just stay flashing quickly. Is this EM mode?? We can't seem to get it doing anything different to this sequence.

 

[scruffymonkey]

p.s it is not responding to Ping requests but we can find it using a Netscan tool where it appears with the default IP. It also sometimes can't be found on the scan. We have tried connecting direct to PC using Ethernet and crossover cable and also through the router. We have found that it gets picked up by the netscan best when it is connected through the router. 

[Dustrega]

It's possible the sectors within the boot partition may be irreparable (hence the sketchy result from the netscan).  It is most likely necessary to replace the device under your regional warranty for which you will need to contact your regional support.

[scruffymonkey]

ok, thanks for your help. We have voided the warranty already as we took it apart to make sure we saved the data. Looks like we have a very expensive doorstop!

[Dustrega]

Sorry about that, I wish I could offer something more, but the diagnostic code you're referring to means that the NAS can't find a drive to boot from.  Since you were able to pull the data the control board on the HDD seems to be intact and the problem lies with the system board.  Feel free to post if you find anything else or have questions.  You could try replacing the HDD (since you took it apart already) and attempt the TFTP and force firmware procedure and see if that yields any results.