Buffalo Forums

So, logged in after a while, saw a new 2.11 firmware to fix the ages old DLNA problem, wanted to try it.

Downloaded it, ran LSUPdater.  Transferred the first file (~1.6Mb). Transferred the second file (~4.6Mb), then died with an ACP_STATE_ERROR.  

Rebooted Linkstation. Tried again.  LSUpdater did not try to transfer the first file (I assume the first file was applied OK). Transferred the second file (~4.6 Mb). Applied it. Started transfer for the "big" file (~99Mb). After transfer, it aborted with ACP_STATE_ERROR.

Figured I'd try the reboot again.  Rebooted Linkstation. Tried again... LsUpdater did NOT try and transfer the second file (So, again, I assume it was applied).  Immediately started transfer of the 3rd file (~99Mb).  After transfer, got an ACP_STATE_ERROR problem.

Now, unable to see the Linkstation on the usual IP Address. Manually reboot it with the switch on the unit.  Cannot see network shares when it comes up. LsUpdater IS able to see the device and says that it has no firmware installed on it (firmware version is listed as "---".  So, I hit the "Upgrade" button and it is trying, again, to upload the ~99Mb file.  No real confidence that this will work.

HOST: HS-DHGL-EM82

WORKGROUP: UNKNOWN (used to be an actual workgroup...)

IP-addres: 192.168.11.x.x (this is correct)

SUBNETMASK: 255.255.255.255.0 (This is correct)

MAC: (Looks reasonable)

Firmware Ver:"----" (This seems bad)

Does anyone have any advice on how to put a new firmware on this fantastic product....?

Jad

This is the same post that edd created here:

http://forums.buffalotech.com/buffalo/board/message?board.id=0101&thread.id=3957

Have you tried plugging the LS and computer directly to your router or switch, or connected them directly together? 

Also if you know how, have you tried to force update the FW with the unit booted into EM mode? 

This issue can sometimes be solved with redownloading FW to a different computer, turn off firewalls and  change some certain debug options when doing a FW update (Uncheck update BOOT. Check: (All other "Update" options) Do not check Version, Delete userconfig, Force Update), then update FW with unit plugged directly into the computer.

You could also try a TFTP BOOT.

Hi Kevin

I connected LS directly to computer, but I do no know how to do "force update the FW with the unit booted into EM mode".

Please can you explain.

Thanks

Hi Davo

Where I can find local support team?

Thanks

Booting into EM (Emergency mode):

You want to power down the unit. Then press and hold the reset button as power the unit up (you can let go of the reset button after the unit has been booting for a few seconds).

Then plug the unit directly into your computer and open up the Nas Navigator. You then want to set your computer's IP address to match the subnet of the IP (first three sets of numbers must be the same and the last set must be a different number) the Navi is giving you, also make sure the subnetmask is the exact same.

Force Updating Firmware:

1. To force the firmware update to the unit, users will need to enable Debug support on the Updater.exe. 
2. To do this open the lsupdater.ini or nasupdater.ini file from the firmware. Whether you have nasupdater.ini or lsupdater.ini will depend on the firmware version.
3. Open the .ini file and Change: Version check = 1 to Version Check = 0 then hit Enter twice and add the following two lines to the of the text file:

[SpecialFlags]
Debug = 1

1. Save the .ini file and run the Updater.exe.
2. Click on the top left corner of the Updater window (on the small picture) and select "Debug (D)". This will bring up the Debug options.
3. Select either "Ignore Current Version", or "Force Update" and click OK. This will have the program force the update even if it detects the same version was already installed.

Having just been through this with a Linkstation Live 500GL all I can say is "DON'T PANIC" it's not bricked.....

I've tried just about all the forums and can I say that not one of the fixes I tried including forced download and ticking various options or re-booting with reset buttons pressed seemed to make any difference - I still had a paperweight with a flashing information light.

What did bring the unit back to life was simply to re-apply the 2.10 firmware and at least that got the unit back albeit in Japanese and the unit had reverted to the admin/password state and 192.168.x.x so simply a question of going into the box (guessing at all the buttons) and changing the language - but beware if you do this, all the shares seem to have dissappeared.

I've got most of my data back by removing the drive, plugging it in as a Sata drive and using Ext2Fsd to mount a partition under Windows and recovered data using  Recover My Files or something similar.   Alternatively look at Linux Recovery by DiskInternals which is free.

Bearing this in mind I see the 2.11 file is still up there for download.

My question is why is it still up there if the potential for wiping out a server is so great????

Mine was coming up with HS-DHGL-EM452, other than that it was the same issue as the original post.

Tried kevin's remedy - worked like a charm. It does take a few minutes to reboot after, but it's worth it in the end.

Never having registered for this type of forum before, I had to this time to say thanks to kevin, and to give others some confidence this method has a chance of working.