Invalid Filename error in Tftp client while installing FW

[Deadbeef]

I've just bought 45 lacie Network space 2 (classic) bricks. They had no HD and no PSU.
Placed an unpartitioned HDD into one and tried to install firmware fvdw-sl-16-0
Used fvdw-sl-console.exe and selected "action" and "Install fvdw-sl firmware". Then after the U-Boot window I powered on the Lacie and the script continues.

Install fails.

U-Boot reports that it's a Lacie 1.5.11 256MB
Then it opens the TFTP window. There it fails (screenshot included) with an Invalid filename error.

Invalid Filename.jpg

After that it continues and Telnet cannot establish a connection.

Please tell me what I'm doing wrong. Is the file in the wrong place? Do I need to start with a lower FW version. Tried "fvdw-sl-11-0-nwsp2-6jan2012.img" with the same result.


Update:
I've found out that I was trying to upload the FW fvdw-sl-11-0 image instead of uploading the U-Boat image.
Changed all that to the correct files.

Still getting an invalid filename.

How do I need to do a first install (AND on a blank HDD)? Do I need to manually prepare the HDD on a linux machine?
or is it possible to do all with the console app?
Could someone please give me the guide to do this? I need to write an instruction, because all 45 nsp2 classic and lite need to be restocked with a new HDD.

And, yes, I've just also found out that the batch I've got is a mix of classic and lite NS2.

[fvdw]

:disapprove you did not read the instructions very well
Below the help file for the action install firmware.
It mentions which file to select first, the standalone kernel....(so not a firmware image or compressed firmware image, but this one UIMAGE-3142-NWSP2CL-KIRKWOOD-24-standalone if you use the fvdw-sl console 5.5)

Furthermore the file with that name must be present in the tftp folder of the fvdw-sl console. This tftp folder is a sub folder of the folder were you installed the fvdw-sl console). You must have selected the file via the popup window that appears when you start this action it ask you to select the standalone kernel. Do not not change the default settings for th tftp folder and just select the file with name UIMAGE-3142-NWSP2CL-KIRKWOOD-24-standalone and then the magic should happen. It still could fail if your firewall is blocking access to the tftp server.

instructions:

Switch off your NAS and follow the instructions that will appear in the main fvdw-sl console window, below some extra information:

(1) Answer the question in the dialog boxes that will popup.
First question will be if you are sure to do this
If you answer "no" the process will be aborted.

(2) Select the standalone kernel file to be loaded
The file must be present in the directory used by the tftp server, a window will popup to let you choose a file.
It will have name like this "UIMAGE-nnnnn-abcdef-STANDALONE-xx". In future release this name may change.
(nnnnn is kernel version abcdef is for which device , for example NWSP2CL means it is for lacie V2 family, KIRKWOOD for lacie devices with kirkwood processor, STANDALONE means it is a kernel that will run from RAM, xx is a version number)

(3) Start your NAS as soon as a window pops up with the remark that it waits for u-boot.
When the NAS is starting it will be detected by the program and it will interrupt the boot, you will see the interrupt in the u-boot window
and after that it will transfer the kernel to the NAS and tries to load and start it.
You can see the progress of the uploading of kernel and starting of the kernel

(4) Wait until this u-boot command windows closes automatically.

(5) Wait for telnet client to start up
After closing the u-boot window the script will wait for 12 seconds to start a telnet client enabling you to log in to the NAS.
The telnet window will pop up automatically after 12 seconds.

(6) Log in using the telnet client
username: root
password: giveit2me

(7) Upload the fvdw-sl-installer script to the NAS by entering in telnet client window:

tftp -r fvdw-sl-installer.sh -l fvdw-sl-installer -g ip-of-your-pc

Replace ip-of-your-pc by the actual ip address of your PC, it is mentioned in the main fvdw-sl-console window.
The reason why the script is not included in the kernel is that is subject to change (optimization)
and can be changed in future without need to recompile the standalone kernel.

(9) Make the installer script executable
After the script is transferred to the nas make it executable by entering in the telnet client:

chmod 755 fvdw-sl-installer

(10) Start the installer by entering in the telnet client:

/fvdw-sl-installer ip-pc

(replace ip-pc by the actual ip address of your pc

(11) Answer the questions in the dialog boxes that popup in the telnet client window

It will ask several questions which speak for themselves.

It will also ask if the boot loader of the NAS supports GPT partition tables.
If the boot loader don't support GPT then you cannot use a hard disk bigger then 2 TB or GPT partition tables
If you make a GPT formatted disk and put it a nas that hasn't support for it in the boot loader then it won't boot

Remarks.
The installer will erase all data on the disk by deleting the existing partition table and creating a new one.

(12) When scirpt is finished

When install script is completed successful:
The nas is not yet completely ready for use if it is not a nwsp2-classic or lite.
For all devices except the nwsp2 classic and lite you need to install the latest firmware upgrade package for your specific device.
If you do not perform this last step than your nas will not be fully functional !.

How to proceed:
a. reboot the NAS by entering in the tenet window::
reboot -f
b. Open web interface of the NAS by entering the ip address of your NAS in browser (you can use the fvdw-sl assistant to find the ip of your NAS)
username : admin-nas
password: admin
c. In case your NAS is not a nwsp2 classic or lite, perform a firmware upgrade using the firmware upgrade menu of the web interface.
You can download the upgrade package for your device from our web site (plugout.net)
After this upgrade and reboot of your NAS your are done.
enjoy

When install is not successful and the script is aborted.
The script produces a log file: installer.log
When the sript has aborted you can view the content by using command:
cat installer.log
The info can be used to see if there is a message inside why the installation failed.

(13) Close all windows related to fvdw-sl-console

thats all

fvdw

[Deadbeef]

Sorry for the long wait (had to work) but here are my results.
Installed a new pc with windows 10 and it worked (almost..)
The new PC was connected through Wifi and although the fimware worked, the telnet console started while there were still files being uploaded through the tftp server.
Switched to ethernet and it worked perfectly.

There were two points in the setup procedure where I had doubts what to do:
1: There was a question about using GPT> I had a virgin nwsp2 classic, with a 120Gb test HDD. I selected the NO option
2: Having nwsp2 classic do I have to do some fimware updates in the WEB interface?

There are questions I would like to ask now:

1)
After I prepared 1 nwsp2 with a drive, I've put the drive in an other virgin nwsp2 classic and that booted?!!?!
Because there's talk of Firmware, I thought a rom on the PCB was being updated and not the disk.
Am I wrong in that assumption?

2) Because I have 43 nwsp2 Classics and Lite (mixed bunch), could I make a disk image with pc cloning software to quickly prep a disk for the other nwsp2's, or do I need to go through this procedure every time?

Sorry for all the questions, thank you for your time answering and the excellent piece of programming the NAS software.

[fvdw]

Sorry for the long wait (had to work) but here are my results.
Installed a new pc with windows 10 and it worked (almost..)
The new PC was connected through Wifi and although the fimware worked, the telnet console started while there were still files being uploaded through the tftp server.
Switched to ethernet and it worked perfectly.

yes you should use wired connection, a wireless connection doesn't seems to work ok with the tftp file stransfers

There were two points in the setup procedure where I had doubts what to do:
1: There was a question about using GPT> I had a virgin nwsp2 classic, with a 120Gb test HDD. I selected the NO option

as long as you use disk smaller then 2 TB using GPT has no advantage.
If you wan to use disks > 2 TB on a nwsp2 classic then you need yo upgrade the boot loader (read the help)

2: Having nwsp2 classic do I have to do some fimware updates in the WEB interface?

No

There are questions I would like to ask now:

1)
After I prepared 1 nwsp2 with a drive, I've put the drive in an other virgin nwsp2 classic and that booted?!!?!
Because there's talk of Firmware, I thought a rom on the PCB was being updated and not the disk.
Am I wrong in that assumption?

yes you are wrong. The kernel and firmware are loaded from the hard disk, the program that does this is the boot loader, that is in flash memory but not touched by installing the firmware

2) Because I have 43 nwsp2 Classics and Lite (mixed bunch), could I make a disk image with pc cloning software to quickly prep a disk for the other nwsp2's, or do I need to go through this procedure every time?

yes you could do that, a disk for nwsp2 classic will also run in lite, the kernel that we use supports both types and also the firmware is the same for both

Sorry for all the questions, thank you for your time answering and the excellent piece of programming the NAS software.

thank you , you are welcome, as I think you are going to sell these lacie's (or are you going to use more then 40 by yourself ;) ) maybe you should consider to use the donation button to support the development of our firmware :whistle