News:

RAID is not a replacement for a backup! Here's why.

Main Menu

LinkStation EZ LS-L320GL Stuck in EM Mode

Started by Pez, December 07, 2009, 04:32:46 AM

Previous topic - Next topic

Pez

   

Hello,

 

A few days ago I encountered a problem with my Buffalo Linkstation EZ (LS-L320GL) storage unit. It seems, completely out of the blue, that I am unable to access my files stored on it. When I try access it through 'My Computer', I get the error message saying:

"An error occured while reconnecting L: to \LS-LSL80Ashare Microsoft Windows network : The network path was not found. The connection had not been restored"

This has never happened before. I've had this NAS for about a years time now. Also, when I open up the Buffalo NAS Navigator
program, I get the error message saying:

"LS-LGL-EM80A has wrong IP settings.
LS-LGL-EMO80A shared folder cannot be accessed.
Configure IP address again"

When it asks me to automatically re-configure my IP address again, it just fails and goes to another error message saying:

"LS-LGL-EM80A is under EM mode. Update firmware of contact your local technical support"

I've tried updating my firmware via the appropriate LSUpdater program which keeps on failing the update process while saying it couldn't confirm a response from LS-LGL-EM80A. Updating is aborted.

As far as I'm aware, no IPs or network changes have occured recently so I'm not sure what could have suddenly caused this problem. I'm running Windows XP SP3 and I have tried all the above steps with my antivirus/firewall on AND off to no avail. I've run ping tests on both my router and NAS with the following results:


- Router = 192.168.1.1 (IP)
\- pings fine, 0% loss, all 4 packets received
 
- NAS = 192.168.11.150 (IP)
\- All 4 requests were timed out, 100% loss, and 0 packets received (?)

 

 

I'd greatly appreciate any assistance, as I'm out of ideas on what to do next. Thanks for your time.


PCPiranha

It can't update because of that IP conflict.  Try connecting directly to your NIC, setting a static IP of 192.168.11.1 and then try updating the firmware.


Pez

   

I was fairly sure that I tried that before, but when I did all that again, it worked! The firmware update was successful and a few minutes later my NAS was up and running again.

 

Thanks!


Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 146 (show)
Files included: 35 - 1354KB. (show)
Memory used: 997KB.
Tokens: post-login.
Queries used: 15.

[Show Queries]