Buffalo Forums

Greetings to all (please excuse my ramblings) -

I, a fearless noob, come with my hat in my hand looking for help. I purchased this 'empty' diskless NAS off eBay hoping I was smart enough to get it running, alas I think not.
I have populated it with 4 brand new 3 TB drives in each of the 4 bays.
As you could assume by the title, when the NAS is powered on, it shows on one of the rotating displays "TFTP Mode E06 Lost Boot Image" along with a loud noise.
I realize the boot image is normally stored on 1 of the 4 drives in the NAS. Being that they have been replaced by me, I understand the error.

I think I have downloaded all appropriate software associated with this particular NAS, specifically:
NasNavigator2 ; TS Firmware Updater (my case TS-XEL v1.73) ; TFTP Boot Recovery (Mutlthread TFTP Server 1.4Beta) ; 'passwords' to extract 2 zipped files located with firmware updater

I have followed the steps as close as possible in -
https://www.reddit.com/r/sysadmin/comments/74xoju/how_to_fix_a_buffalo_terastation_tsxel_in_tftp/

I put the firmware files 'initrd.buffalo' and 1 of 3 files extracted 'uImage.buffalo' in the same directory as TFTP Boot Recovery app which is on my laptop.
I configured my wired network port (192.168.11.1) of my laptop to communicate with the NAS via LAN1 by plugging both cables into the same switch.

When I launch the 'TFTP Boot.exe' recovery app (TFTPServerMT.exe), I always get this immediate response and nothing else even after the NAS is fully powered up:
  Preparing to write TFTP configuration settings.
  TFTP Configuration settings have been written.
  TFTP Server Multithreaded Version 1.4 Windows Built 1.400

  127.0.0.1 Port 69, bind failed
  192.168.11.1 Port 69, bind failed
  No listening Interfaces available, stopping...

What should happen I think is that I should see 2 files being transferred at some point in my TFTP Server window... but I don't. And I don't get anything else.
The NAS LAN1, the Ethernet switch, and my laptop all show good LAN activity.
I have debugged both Ethernet cables as well as taken apart the NAS looking for loose cabling/connections
I have tried plugging the Laptop straight to the NAS unit.
When the NAS powers up all drives are green.

I wished I could have used the "Restoring Stock Firmware without TFTP Server" guide steps... but that requires some skill in Linux... The problem is I have no skill in Linux nor do I have the means/hardware to do it.

Reference Links:
https://buffalonas.miraheze.org/wiki/Restoring_Stock_Firmware_via_TFTP
https://buffalonas.miraheze.org/wiki/Extract_Boot_Files_from_Stock_Firmware
https://buffalonas.miraheze.org/wiki/Restoring_Stock_Firmware_without_TFTP

Please NAS gurus, I have spent hours upon hours trying and retrying different things.

Have I missed anything? Can anyone give me another option to try? Is this NAS just a brick now?

Thanks in advance,
randys69@hotmail.com

(I welcome direct contact)

Quote127.0.0.1 Port 69, bind failed
  192.168.11.1 Port 69, bind failed
  No listening Interfaces available, stopping.

This sounds like a permissions issue to me, if it were on Linux I'd say you need to run the program as root. If you're on windows I imagine you need to "run as administrator" or something of that nature. I suppose it could be a windows firewall issue, though I would expect that would block the traffic rather than prevent binding to the port. I suppose if you had multiple instances running by accident the second one would probably see that since the ports would be busy, you could try restarting before a next attempt.

Also, note that this is the device that uses uImage-88f6281.buffalo rather than uImage.buffalo.

@ 1000001101000

Your suggestions are very much appreciated.

I confirmed the firewall on the laptop is switched off.
I highlighted (aka selected) the program 'TFTP Boot.exe'  and chose 'Run as administrator'
and received the same text in the window as before...
"127.0.0.1 Port 69, bind failed
   192.168.11.1 Port 69, bind failed
   No listening Interfaces available, stopping."

Also... I did change the firmware name back to its original 'uImage-88f6281.buffalo'
(originally, I had made the assumption that there was a name constraint for this file that had to be kept.)

After these tweeks were done and re-tested, I have no change in the condition of my NAS.  :-(
This is making me wish I was a Linux guru...

(Help me, Obi-Wan Kenobi. You're my only hope)

Did you reboot? If those ports are in use for some reason that might clear it up.

You could also try a different tftp program. I've been hoping someone would try it out with an open-source one like this one and write up instructions to add to the wiki:
https://tftpd32.jounin.net/

If you have the means to connect one of the drives to a PC booting into a linux livecd side-steps any network issues. The guide includes all the commands needed.

@ 1000001101000

Thank you again for your suggestions. Here's everything I have done so far... (I am listing these steps in case it helps others.)

First suggestion 1) After reading your post... I re-checked and did a reboot just as you suggested just in case that indeed I did have blocked ports... but no help.

Next thing 2) I tried different TFTP Server programs... and sadly I had the same binding faults as before.

Third suggestion 3) Connect one drive to a PC and run linux liveCD... I am very weak in Linux but what the hell... I downloaded Fedora Desktop software and put it on a bootable DVD. In previous attempts to fix this problem... I had downloaded Paragon Partition Manager to my PC. With this software, I took the 1st of the 4 blank drives and removed it from the NAS box and then did a GPT drive format, and formatted partition 1 as Ext3. Now using Fedora linux desktop software, I could see that I had the disk set up properly but I was lacking the ability to move the files. (lack of linux knowledge on my part), I kept getting an error that I don't have permission everytime I tried to do a move/copy the files. So I failed here too.

Next, I downloaded and installed 'Ext2Fsd-0.69.exe' to my PC. I wanted to use this software (which reads/writes to linux formatted drives) to transfer the files that I needed to the NAS drive (drive #1)... specifically files: 'uImage-88f6281.buffalo' and 'initrd.buffalo'. After installing the software, I was able to mount the NAS hard drive (1 of 4) on my PC and then I copied those files over to the hard drive. I put the drive (#1) back in the NAS box and turned it on. The LCD on the NAS changed to a 'Welcome to TeraStation' screen.  (Happy dance!!!!)

Ok I realize now that I am getting somewhere... The rest is just following the steps located here... https://www.reddit.com/r/sysadmin/comments/74xoju/how_to_fix_a_buffalo_terastation_tsxel_in_tftp/

Next, I launch the TS Firmware Updater and it recognized the NAS box. I needed to relaunch the TS Firmware a couple of times as well as power cycling my NAS box.
When that all looked successful, I launched the 'NasNavigator2' and my NAS box showed up there. I clicked on properties and then open settings. and I was taken to the web based app of my NAS box... (because of my DCHP my unit became 192.168.0.28). (Yes, it was in Japanese but was fixable)

All that's left now is the configuration.  :-)

My sincere thanks to you for helping and sticking with me. Thanks to you I didn't quit and I was able to make this box a workable NAS again.

Cheers!

Sounds like a win.

I suppose another good guide for someone to write would be a windows-based non-TFTP process like what you just accomplished. It seems like a good compromise for folks who can't reconfigure their network for TFTP (or would just prefer the hassle) and don't have linux experience and would prefer avoid the hassle of a booting a liveCD etc.