Lacie 2Big Network vs1

[fvdw]

Hi Matzi

There are some help menus included in the console. :whistle
The sequnce is connect to nas to the network but keep it swictched off. Now start the fvdw-sl console.
If you want to install firmware then choose as action "install fvdw-sl firmware".
It then will ask you to if you have a nwsp2, answer yes. Then select the 2big1 standalone kernel in the window that pops up. It must be in the tftp directory of the console and unzipped. (the name must contain "nwsp2" otherwise it won't load. Thats the reason why the file is called the UIMAGE-26394-NWSP2-2BIG1-22-standalone. After selecting the standalone kernel it cmd window will popo up saying it waits for u-boot. Now start the 2big1. The console should detect that it boots and iterupt the boot, and upload the standalone kernel and start it. After that you get a telnet window enabling you to log in. etc etc (read the instruction)

After writing the firmware you will need to replace the kernel in sda6 as the installer will write a nwsp2 kernel to sda6. Do not reboot. First upload the normal 2big1 kernel via tftp and write it to sda6.

In the telnet client give the commands

Code: Select all

tftp -r UIMAGE-26394-2BIG1-21 -l UIMAGE-26394-2BIG1-21 -g ip-pc

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

Write it to sda6

Code: Select all

dd if=UIMAGE-26394-2BIG1-21 of=/dev/sda6

now reboot

[matzi]

That's what i thought to do, but see my last post: Choosing "Install fvdw-sl firmware" I get a message box saying "standalone function returned false" and the sequnece aborts.

Edit: Before this message box there is another one saying "This kernel is probably not for nwsp2,5big2, 2big2 or cloudbox, abort"

[fvdw]

change the name to

Code: Select all

UIMAGE-26394-NWSP2CL-2BIG1-22-standalone

and try again

[matzi]

That works now. It then tries starting the telenet session but cannot establish connection. Telent uses the correct IP that can see in my router. I tried with both disks installed and with just one disk (right one seen from the rear side).

[fvdw]

sometimes it takes longer then 12 seconds for the kernel to finish boot, the telnet serve ris not up and running when the client tries and tthe client times out.
Just try to connect again with the telnet client, use the connect button in the telnet window and choose the right IP

The kernel will work regardless of the number of disk (even without any disk in the nas)

[matzi]

Sorry also after waiting and several attempts, no connection. :dontknow

[fvdw]

which ip do you use in the telnet client ?

[matzi]

192.168.178.32

[fvdw]

the standalone kernel assigns itself two static ip's 192.168.1.252 and 192.168.0.252
Of course you can not reach those in a lan with ip's starting with 192.168.178 (assuming you router uses netmask 255.255.255.0)
It also tries to assign itself a dynamic ip address from dhcp server. Probably that is the one you are using.
I always use the static ones but that will mean in your case you need to change setup of your LAN

Question if you open a command window in windows and sent a ping to the ip you mentions, does it respond ?

[matzi]

ping from 192.168.178.30 (PC) to 192.168.178.32 Host not reachable
ping from 192.168.178.30 (PC) to 192.168.0.252 Timeout

Edit:
ping from 192.168.0.250 (PC) to 192.168.0.252 Timeout