LS-WXL Tftp download link

[hamoramo]

Hi

I am using LS-WXL series Linkstation  -Duo for more than 6 years.

Recently I received a notification which is saying that I have bad sectors in one my HDDs in the array. So I have decided to delete raid array, dismounted all the HDDs, deleted all the partitions and checked the disks.

Then I have installed one old HDD and one brand new identical HDD into the enclosure. Unfortunatley it did not boot up and red light started to flash. (I could not count it so I do not know that the code is) and Nas Navigator could not see it.

Tried to hard reset the device by following the procedures, but that did not also work.

Tried to open the Lsupdater in debug mode,  I was not succesfull in this attempt also.

AS for the last resort I was planning to go through with TFTP procedure but then I could not find the download link and procedure guıideline for it. ( I did it couple of times before but those were daysa)

So currently I am desperate to make my device up and running again.

I need your advices and support.

Thanks

[1000001101000]

there are resources in this pinned post:
http://forums.buffalotech.com/index.php?topic=30419.0

It includes a link to how to do TFTP recovery with generic tools:
https://buffalonas.miraheze.org/wiki/Restoring_Stock_Firmware_via_TFTP

[hamoramo]

Thanks for the help but the problem is still going on.

I have followed every single step but the device is not booting:(

[1000001101000]

I recommend the alternate method of loading the boot files to a drive. TFTP is a pain to troubleshoot.

[hamoramo]

I will try it but unfortunately I am not good at using Linux. Let me give it a shot

[hamoramo]

When I am trying to transfer the files via tftpd64 there is an error message about the failurof initrd.buffalo file transfer

I recommend the alternate method of loading the boot files to a drive. TFTP is a pain to troubleshoot.

I have tried to use another tftp file LS421DE before do you think that could be reason and the system is not overwriting the other one?

[1000001101000]

I'd need more detail of what you're doing to know what's going on.

I can tell you that the *.buffalo files are specific to different groups of devices, ls421 and ls-wxl files are not interchangeable.

If you were trying to send the LS400 files to a LS-WXL it disconnecting after a point might make sense if the bootloader is failing to load them because they are too big. I'm not confident that's what would happen though. The difficulty in untangling this type of thing with TFTP is part of why I don't like it.

I believe there is a way to make the needed ext3 partition with a windows utility if that helps. I'm not familiar with it personally but I believe I've heard form someone who has used it.

[hamoramo]

1) I have downloaded related FW (In this case it LS-WXL 1.75)
2) I have extracted related files from the stockware
3) Tried to transfer the *.buffalo file to the device (w/o HDD) via tftp program
4) It transfers only one of them to the device

Then I have tried to format the HDD to ext3 and created one partition with 1 gb size, transferred the files to those partitions and this did not work either

I do not know whether I am missing an important step or not?

I'd need more detail of what you're doing to know what's going on.

I can tell you that the *.buffalo files are specific to different groups of devices, ls421 and ls-wxl files are not interchangeable.

If you were trying to send the LS400 files to a LS-WXL it disconnecting after a point might make sense if the bootloader is failing to load them because they are too big. I'm not confident that's what would happen though. The difficulty in untangling this type of thing with TFTP is part of why I don't like it.

I believe there is a way to make the needed ext3 partition with a windows utility if that helps. I'm not familiar with it personally but I believe I've heard form someone who has used it.

[hamoramo]

Now it looks like I transferred the files via TFTP as described in your manuals

I do now know how long do I need to wait for the device to reboot?

I'd need more detail of what you're doing to know what's going on.

I can tell you that the *.buffalo files are specific to different groups of devices, ls421 and ls-wxl files are not interchangeable.

If you were trying to send the LS400 files to a LS-WXL it disconnecting after a point might make sense if the bootloader is failing to load them because they are too big. I'm not confident that's what would happen though. The difficulty in untangling this type of thing with TFTP is part of why I don't like it.

I believe there is a way to make the needed ext3 partition with a windows utility if that helps. I'm not familiar with it personally but I believe I've heard form someone who has used it.

[1000001101000]

within about a minute or two of the transfer finishing you should be able to see the device in LSUpdater, you should then be able to follow the steps to do the install.

[hamoramo]

Could not see

Now I will try with other image file because there were 2 uImage files

within about a minute or two of the transfer finishing you should be able to see the device in LSUpdater, you should then be able to follow the steps to do the install.

[hamoramo]

Now I have moved to another level.

I can see the device in LS updater it keeps failing during the formatting the HDDs:(

within about a minute or two of the transfer finishing you should be able to see the device in LSUpdater, you should then be able to follow the steps to do the install.

[1000001101000]

Try and start with completely blanks drives. Not formatted, with the partition table removed.

Also enable the formatting debug options if you haven't already.

[hamoramo]

New level:)

Everything is gone fine LS updater says it is booting but after a while new message is saying that "no response from linkstation for 1200 seconds. Do you want to try again"

REd lamp is blinking 7 times (but not like I25) :(

Try and start with completely blanks drives. Not formatted, with the partition table removed.

Also enable the formatting debug options if you haven't already.

[hamoramo]

I do not know how but finally I solved the problem.

Device is up and running now:)

Thanks for your help and patience man....