TFTP is a windows app you run to host the boot files. When I do TFTP, I run it from from a second PC. It just acts as a file server to pass the boot files to the linkstation. That's all it does.
The other way is to not use TFTP, it requires linux drive formatting from a linux pc, and in my experience, it has never worked.
TFTP is a protocol, there are clients available for pretty much every OS, See:
https://en.wikipedia.org/wiki/Trivial_File_Transfer_Protocol
Loading the installer files directly to the disk can be simpler than TFTP in some scenarios where making the required network changes is difficult but it does involve working in linux which many people don't have experience with. Most who have tried that route have eventually succeeded.
In your case neither is necessary, these are just methods to get the device to boot... but your is already booting. If you desire you can completely wipe and restore the device using LSUpdater in Debug mode which provides options for reformating/repartitioning.
For the sake of the conversation, TFTPBoot.exe certainly IS an APPLICATION. And I had no intention of confusing this user more than what he already is about what TFTP does in regards to the nas. And so debate about what TFTP is as a protocol AND an application, and splitting hairs over it, is completely irrelevant.
True, I forgot that he can just run the firmware updater app and just try to update the firwmare that way. Yet that way doesn't always work for everyone either.
I cannot count how many times myself and others have gotten 'format partition failed' errors when trying it that way, on drives that boot to the console, and have partitions on them from a previous install. If you have a workaround or fix for that- I think it would be very helpful. There's many who don't know what to do in that situation.
And so because of that error, I always blank the drives first- to save time and headaches. Some of us are just too busy and don't have time. Plus, we don't know how old his drives are or if they were mishandled. It's possible (however unlikely) the data area where the firmware is stored could have bad sectors. I always find it a good idea to blank drives and sector check them first before installing from sratch, because these devices don't have very good utilities for testing, managing, and maintaining drive health.
Anyway, hopefully he gets it going.
I'll bouw out of this and leave it to you- you're the expert...