plugout.net

Hello,
i'm trying to install fresh install Fvdw-sl on my old NAS Lacier 2Big Network 2.

when i run the installer, i choose the install fwdw-sl firmware from menu, then choose then the image UMIMAGE.xxxx.2BIG-1-47-1-1-4-standalone and after power on the nas.
i see the u-boot menu connect to my pc
then i see assign the ip address, and download via tftp the image
after 15 second start the telnet.....but here after some seconds , fail the connect to the session.
if i try to ping the ip assign to nas from your procedure fail.....
why?
where i wrong?
the connection lan it is direct witn my laptop via cable.
the HD are completely empty (new)

thanks for your support.

Sorry i had write in wrong way the past messagge:
i DON't have chosen install fwdw-sl firmware from menu BUT i have choose first Install kernel standalone load and run.
then when run telnet, it can't access because doesn't see the ip address.

sorry my mistake

HEllo,
find my issue.
for help the other USER:
- run the installer
- Choose kernenel strandalone load and run
- choose the RIGHT version kernel :)
- wait the upload
- At the prompt of telnet digit user/passwrd how write on the console of the isntaller
- At the prompt digit the command for install the firmwarte on disk

DONE

Hi, I have a variation of this problem. I have a 2Big V2 and the Lacie firmware won't boot.
I have tried to download using FDDW-SL using the instructions from this site. Both the Windows 10 PC and the Lacie are on the same ethernet interface.
The window shows:

Using egiga0 device
TFTP from server 192.168.0.36; our IP address is 192.168.0.252
Filename 'UIMAGE-3142-KIRKWOOD-171-standalone'.
Load address: 0x800000
Loading: T T T T T T

then the window closed,Telnet starts but no connection is possible.
Telnet works to other devices on this network from this same PC.
I also noticed what I think is a problem. If I turn on the 2Big with NO hdds installed, the front light flashes blue, then goes solid blue...this doesn't seem right.
Appreciate any suggestions.

Seems there is no file transfered the T means timeout.
Meaning the tftd32 server started by the console doesn't respond.
Did you grant the tftp32 server access through your firewall?

Thanks for that, now instead of the timeouts I get a single flashing * for just a few seconds, then the window closes and I still can't telnet..

Hi,

Are you sure the IP 192.168.0.252 or 192.168.0.251 is not used by another host on your LAN ?

Yep, sure, I'm beginning to think the fault is with the 2Big, thanks for the suggestion.