"Due to its simple design, TFTP can be implemented in a very small amount of memory - an important consideration [in the past]. It was therefore useful for booting computers such as routers which did not have any data storage devices. It is still used to transfer small amounts of data between hosts on a network, such as IP phone firmware or operating system images when a remote X Window System terminal or any other thin client boots from a network host or server. The initial stages of some network based installation systems (such as Solaris Jumpstart, Red Hat Kickstart and Windows NT's Remote Installation Services) use TFTP to load a basic kernel that performs the actual installation."
Thank you, Wikipedia.
TFTP in this case is used for replacing a failed boot image on the NAS. When the NAS is first booted and gets an E04, E06, or stays at "system now booting" for a while, it sends a request to the IP address 192.168.11.1 to replace blocks of data for the missing boot image. This is usually a last resort to getting a NAS to work when these errors are prevalent, and is not a guaranteed fix.
Performing a TFTP boot:
A TFTP boot requires a little bit of finesse and a tiny bit of luck. 9 times out of 10 when a NAS constantly says "System Now Booting", E04/E06 (or 4/6 DIAG light flashes depending on the NAS) or doesn't show up on the NAS Navigator after a long period of time after an EM boot attempt, then chances are that you need to perform this method. So, without further delay let's get to it.
What you'll need:
- The NAS Navigator client ( Found here )
- Your NAS model's latest firmware ( Found here )
- Your NAS model's TFTP boot image( Download for Firefox/Chrome ) ( Download for IE )
***(NOTE: Some older NAS models may not have a TFTP solution available, if you cannot find your model in the listing please DO NOT attempt to use the TFTP program of another model.)***
Make sure your firewall/anti-virus software is disabled.
Performing the TFTP boot:
1. Directly connect your NAS to your computer via an Ethernet cable (crossover isn't necessary).
2. Set your computer's NIC (Network Interface Card) to a static IP address of 192.168.11.1
3. Disable your any other active network adapters (i.e. your computer's wireless card)
NOTE: If you don't know how to change your IP address on your computer you can find out how to do that for Windows (XP, Vista or 7).
4. Run the TFTP program for your respective NAS and have the files extracted to your desktop
5. If your unit has a Reset button, attempt to boot into EM mode using the directions found here - if you have only a Function button, skip this step.
5. Open the TFTP folder and run the program TFTP Boot.exe with the icon:
6. A command prompt similar to the one shown below should appear:
7. When the NAS boots up it will make a request to the IP address 192.168.11.1 (which is what your computer should be set at). If you do not see "listening On: 192.168.11.1:69" in the terminal, then you will need to restart the program (possibly your computer, too).
8. If you have a unit with only a Function button (i.e. X and V series units), press and hold that button for 5 seconds; otherwise, skip this step.
9: Your terminal should now show two lines ending in "Blocks Served" - if they do not, then you will need to reboot your computer and your NAS and repeat the TFTP boot process.
After you see blocks of data being served the NAS typically boots to Emergency Mode at which point you can perform a force firmware update following FAQ 2 of 5 here where it talks about changing the ini file to get to the debug settings (don't forget to remove your static IP address).
You may have to wait up to 10 minutes before the unit is found by the NAS Navigator. If your unit reboots and has the same error code, you can retry the TFTP boot procedure.
If your errors or issues persist after a few attempts, I would suggest contacting your regional technical support or posting on this forum.
-OP : Dustrega.
