News:

Buffalo provides Data Recovery services. Read about it here.

Main Menu

No access to Linkstation mini, Blue light flashes continuously

Started by hr1179, February 14, 2012, 01:50:58 AM

Previous topic - Next topic

hr1179

I have a problem with my Linkstation Mini (LS-WSXL).

 

When starting the unit, the blue light flashes continuously but no other light (normally the green lights blinks) sometimes there are some drive access sounds, but very quiet and only a few.

The NASNavigator does not show the unit and it do not answer to ping requests.

I let the drive run more than 12 hours but nothing changed. 

 

By the way I didn't made any firmware updates and had no access errors. The unit is running with Raid 1 (2 500gb drives mirrored).

 

Can you tell me what the problem might be. Do I need to recover the data, or is it a firmware problem?

 

 

 

 


skaiware

I think I have exactly the same issue than you:
View My Video
http://tinypic.com/r/rihfua/5

The NASNavigator does not show the unit.
The power on/off/auto does not work anymore.
I can just ping it successfully but that's all as my router gives me his IP address.
I am surprised that you did n't receive any reply.
Buffalo are you here ?

skaiware

I have connected the Mini directly to my computer.
I have changed my Ethernet IP setting to 192.168.11.1 mask 255.255.0.0.
The blue light stopped to blink.
The Buffalo softs find it in EM mode.
Strangely Firmware version is : ----
But when trying to update firmware:
"
No response from LS-WSXL-EM621. Please check your network settings.
The LS and your comp should be on the same subnet.
Temporaly disable any firewalls and try again.
"

Of course : no firewall, I have even turned off Microsoft Security Essentials.
And now both are on 255.255.0.0.

[/img]

skaiware

Much more strange :
- rebooting the Mini
- Relaunching LSUpdater
- Find
- found mini on 192.168.0.150 on 255.255.0.0
- try to update
- no way as usal
- then refind
- LSUpdater found the mini on 192.168.11.150 on 255.255.255.0

Just like the mini is changing network config dynamically and randomly.
This is worst and worst hours after hours.


skaiware

By the way even if LSUpdater (1.65) seems to find a Mini I cannot ping it anymore...

skaiware

Just to proof: here is my ipconfig output:

Carte Ethernet Connexion au réseau local :

   Suffixe DNS propre à la connexion. . . :
   Adresse IPv6 de liaison locale. . . . .: fe80::607e:fc19:8816:3ed4%12
   Adresse IPv4. . . . . . . . . . . . . .: 192.168.11.1
   Masque de sous-réseau. . . . . . . . . : 255.255.0.0
   Passerelle par défaut. . . . . . . . . :

skaiware

Here it is, dont know why but I can now ping the mini :
ping 169.254.23.90
Envoi d'une requête 'Ping'  169.254.23.90 avec 32 octets de données :
Réponse de 169.254.23.90 : octets=32 temps=2 ms TTL=64
Réponse de 169.254.23.90 : octets=32 temps<1ms TTL=64
But cant still LSupdate : "No response from LS........"

skaiware

Of course no way to access my files :
\\LS-WSXL-EM621
\\169.254.23.90
nor
http://169.254.23.90

I suppose the Mini does not run any http nor samba server when in EM mode, does it ?

skaiware

On the other side, I dont really want to upgrade firmware, so is there anyway just to ask the mini to mute from EM mode to normal mode ?

skaiware

Tried to change a little bit LSUpdater.ini params to:
Title = BUFFALO LinkStation Series Updater Ver.1.63
WaitReboot = 1200
WaitFormat = 600
WaitFileSend = 900
WaitDiscover = 190

but no way: "No response from LS........................................."

skaiware

Found in some obscure docs:
"The subnet masks should be the same and the first three numbers of the IP addresses should be the same. "
Let s change the ip of my windows to follow the ip of the Mini...

My mini is currently on 169.254.200.116
Let s move to for example 169.254.200.1

Carte Ethernet Connexion au réseau local :

   Suffixe DNS propre à la connexion. . . :
   Adresse IPv6 de liaison locale. . . . .: fe80::607e:fc19:8816:3ed4%12
   Adresse IPv4. . . . . . . . . . . . . .: 169.254.200.1
   Masque de sous-réseau. . . . . . . . . : 255.255.0.0
   Passerelle par défaut. . . . . . . . . :

retesting LSupdater....
success.
To resume it was too hard for Buffalo to write these 2 lines:
- subnet must be the same : exple: 255.255.0.0
- first 3 IP must be the same : exple: 169.254.200.1 for the PC, and 168.254.200.100 for the Mini.
Rebooting...

skaiware

After firmware update, the Mini has reboot once.
Then, (new), the red blinks like that: 2 times long, then 5 shorts blinks.
Then after few minutes, the Mini reboots again.
Now the blue LinkStation blinks (no connection) and of course Buffalo softs cant find it.
Switching to 'off' does not work anymore: the Mini does not want to switch off. Dont know what to do.
In other words going back to the state I was 6 hours ago.
It is 2AM in the morning. I m starting working at 7AM.
Thanks Buffalo.

skaiware

Here it is:
- replug directly the mini to my PC
- used NASNavigator2 version 2.69 (very important)
- searching
- seen few warnings : "The IP setting is wrong, would you like to fix ?" or "The clock is wrong, ...."
- accepted changes
- waiting 15mn
- no more EM mode
- get access to my files
To conclude:
- would have been a better choice to offer the possibility to upgrade firmaware through USB key
- the LSUpdater could definitely detailed in the popup : "The mask between Mini and your PC must be the same and both must have the same schema types of IP : x.y.z.?"
- why turning off DHCP in EM mode ?

skaiware

I m going to do what I should nt but if anyone needs such help, send me an email.

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: 368 (show)
Files included: 35 - 1354KB. (show)
Memory used: 1088KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]