News:

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

Main Menu

Continuous blue flashing led ls-xhl

Started by gmw, August 01, 2010, 11:05:01 PM

Previous topic - Next topic

gmw

Is it possible to manually partition the disk and install firmware, (eg under linux) and then connect back to LS-XHL as a working system. I would need to know the partition and format info and how to install the firmware into the "/boot" partition. Does anyone know if this is possible?


AngelsAbys

There is no way to manually set a partition on the device, the partition set up is decided via the firmware upon load/write.  As for the 6 red flashes, if you press and hold the function button for 2 seconds does it continue to flash blue per previous posts?  After the blocks become served try running the forced FW while the TFTP is still active, this has been proven to help in some instances.


scruffymonkey

We are having the exact same problem - now have a completely blank disk and it just won't connect / stop flashing blue.


Dustrega

Posting in another thread doesn't change the response chief.


secaboy

i have the exact same problem how ever Nas Navigator rekonises that there is a drive there, but still a flashing blue light. Please help a newbie to NAS


Dustrega

Have you tried the suggestions mentioned previously in this thread?


stuey

Downloaded the 1.33 as basically the bit torrent in 1.31 was not workin and the unit very slow.

 

Downloaded  the updater

Disabled the firewall on the laptop

ran the updater it found my LS-CHL V2 and reminded me to disable the firewall

 

Updater ran sucessfully and told me to wait.

 

Still waiting....

 

Left the laptop and nas "as is" over night and went and checked the nas it was flashing a blue light on the top  no other error codes

 

Powered down the NAS and Powered up  ( this was 8 hours after the upgrade BTW) and still quick flashing blue light.

 

Does anyone have any thoughts on what to do next, I have read threads about EM mode and will try that later

 

 


Dustrega

I would have suggested an EM boot attempt since the firmware didn't take.  I would also check and make sure you don't have any countermeasure software (firewall, anti-virus, etc.) running stealth in the background.  Usually, that's the cause for firmware update failure.


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

[Show Queries]