LS-WX6.0TL/R1 6 red flashing LEDs of death

[TeKKiE]

Hello everyone.

I purchased this 6TB NAS some years ago, while on a deployment in Afghanistan. It served me well, and I had very few issues with it. For some reason or another, I had pulled the drives out of it when I got back stateside, probably to use them to deploy my server in my basement. those drives have since been borked, and I replaced them with WD drives in the server (18TB, quad processor, 64GB ram, etc. etc.)

The server's purpose is for content aggregation and delivery for our house, and a few family members in remote areas.

I decided I wanted to give the NAS a new mission, so I slapped a couple WD 3TB barracuda drives in it and fired it up. Both drives were brand new with no partition table. When booting, I get the typical fast blinking blue light for around 10 seconds give or take, then end up with the 6 red led flash cycle. I had tried to TFTP boot the device from a windows box and direct connection, and you could see the device pull the files it requires, however it still doesn't show up in any software designed to communicate with it (LSUpdater, etc. etc.)

My primary OS's in the house are *nix based, so the windows machine was a long shot and I'd rather not use it.

What I'm currently trying to figure out, is what the partition table should look like for each drive in the device? Would this matter, even if I can't access it with LSUpdater? Is there an alternative I can use to reflash firmware from my *nix devices? I'd rather not continually attempt (fail) to get it working with LSUpdater on a windows box which I despise.

Any assistance is appreciated. I'd like to get it up and running as a local NAS rather than use my MediaServer for things like family photos and music storage (kids have iPhones and I want their iTunes libraries to be synced with the NAS). Thanks in advance for any assistance you can provide. I tried to follow quite a few faq's and ended up with the same 6 flashing led issue as before.

[TeKKiE]

Update:

So with using some guides around these parts (again) and using specific TFTP Boot v. 1.53, I was able to get the Duo to pull the files as before however this time the blue LED switches to a solid blue after around 90 seconds to two minutes.

Using the NasNavi software provided with the Boot Recovery 1.53 package, I can identify the Duo.  Good step in the right direction as I haven't been able to see the device at all.

The next issue:  The IP Address.

The IP address is the usual Zero Config IP address (169.254.x.x). I then change the IP of my temporary windows machine to the same subnet, and attempt to search for the device using the LSUpdater program in the firmware zip, and the LSUpdater software does not detect the device, even in debug mode.

I have tried 137,141,154,168 and 169 firmwares, and none detect the device.

So, back to my other question:

What is the default partition layout of each drive? What are the default contents of the first partition which I assume to be the boot partition with the boot specific parameters for the hardware?

Thanks

[joma90]

Run in safe mode or try disabling any firewall/antivirus. and try the update again.

There are a total of 5 partitions. a roots, the main and whatever the other 3 are. forgot. Each drive should carry a boot partition.

[TeKKiE]

Run in safe mode or try disabling any firewall/antivirus. and try the update again.

There are a total of 5 partitions. a roots, the main and whatever the other 3 are. forgot. Each drive should carry a boot partition.

Norton Security was disabled, as were the OEM Windows Defender and Firewall services. I had not tried safe mode yet, simply because I was able to communicate with the device .

I suppose I will give it another shot this evening and see if my luck is any better. I'm beginning to wonder if these issues are what led me to strip it in the first place, in order to populate empty bays in the server...It's been so long and I've slept since then :D

[TeKKiE]

Trial and error, with a bit of persistence...

Using FAQ 2 of 5 (forced firmware update) worked.

http://forums.buffalotech.com/index.php?topic=22603.msg82311#msg82311

For all others that follow and find the same issues I encountered, follow that FAQ to the letter.

For the record, I used the Buffalo LinkStation Series Updater (Firmware) version 1.54, with the TFTP Boot Recovery version 1.53.  This combo seemed to work best, as any other recovery version did not send the correct length files to the device. That's just my thoughts on the matter. :)

Now I have access to the web interface, although I also have a solid amber information light (which I will research now).

[TeKKiE]

Solid amber = firmware update available.

Thought I would update with that as well.

One thing I noticed...

When checking for additional firmware updates beyond 1.56, the NAS web portal tells me that my firmware is up to date. So that is likely why I had issues with the > 1.54 firmware install to begin with. :)

[joma90]

The Latest firmware is 1.69 I believe, You want to get out of the 1.5x as there are many issues with them that causes units to stop responding. From my experience at least.