[SOLVE] 2BIG2 hide after installation reset.

[maxdo]

Hello,
i'm trying to install your Firmware on my nas 2BIG v2.
so following your procedure i have:
- run the installation.
- install the kernel
- enter in the telnet
- run the installation menu
- the procedure download via tftp the firmware, formatting the three partition ,and install everything withou any error.
- then reset the NAS via command telnet.
- but when the NAS Reboot, doesn't answer at the ip address configured (used from telent before)............

so, why? how can i check what happens and fix the issue?

many thanks

[Jocko]

Hi maxdo,

You need to use fvdw-sl assistant to discover the IP of your NAS.

Please to note it is a temporary IP used by the NAS when you install the firmware by using fvdw-sl console

Note: you may also try to use the url

Code: Select all

http://fvdwsl-base

BUT
I saw you also posted some messages on the forum "2big1". So if you install the firmware for 2big2 whereas it is a 2big1, boot script will abort

[maxdo]

HEllo Jocko,
thanks for your answer.
don't worry....it was a my mistake, where i write my request in a wrong post....sorry i had close the request to on the wrong post.

MEAN here the problem it is different.
I've the 2BIGv2 and install the kirkwood firmware. so it is correct.
i had supposed that the ip address was a temporary ip, and after reboot, i image: or search a a dhcp server , or need to use some else.

fvdw-sl assistant it was my solution of course....but doesn't find anything.

so i have put under trace the network and i have seen that the NAS sent out AoE request information (!!!) and ask a ip adress 169.xx.xxx.xx and want the answer at the address 0.0.0.0 :O

there is something of strange here.

how can i debug the issue? there is a way for leave a ip address on the system in static way?

thanks.

[Jocko]

As it was not clear how your nas is on your lan and your laptop? (according with your previous posts on 2big1 forum)
The right configuration is:
- nas and laptop on the same subnet (set by by your router).
- you must have a dhcp server available on your subnet (so basically provided by your router)

so i have put under trace the network and i have seen that the NAS sent out AoE request information (!!!) and ask a ip adress 169.xx.xxx.xx and want the answer at the address 0.0.0.0

That means your nas fails to get a lease from dhcp server.

[maxdo]

Hello jacko,
you had right.... my configration NEtwork it is:
nas connect to a swith
my laptop connect to the same switch
on my laptop i have the DHCP server tool, but nothing request a ip address via DHCP

i have my head so hard :) then i have run my wireshark and read the packkect sent on this mini network (other nas and my pc there is not any other device connect on it)
and i have see that the NAS doesn't present a request DHPC, but try only to see an address 169.245.64.175 that register on network his name ......aaaaah then you assign the default ip when normally doesn't find a DHCP server.... well i have changed my laptop on the same ip subnet....et voilà i'm enter in it :)
so, i have check immediately the network status..... in effect it configured how DHCP, but the request doesn't send out on broadcast.... i don't know why....

however, i'm finally in the NAS with the right IP address again.
now i proceed to install the second disk (via your procedure)

please, we can close that thread :)

i will change the subject add the [solve] note ...
thanks

[Jocko]

Hi maxdo

and i have see that the NAS doesn't present a request DHPC, but try only to see an address 169.245.64.175 that register on network his name ......aaaaah then you assign the default ip when normally doesn't find a DHCP server....

It is not fully right
Default behaviour with the default settings is :
- set a random default static IP 169.245.xx
- run a dhcp client and wait to get a lease
- keep this static IP as long as the nas does not receive a lease from a DCHP server
- set a next IP when it receive it

Your issue means the nas and your DCHP server failed to exchange requests

[maxdo]

t is not fully right
Default behaviour with the default settings is :
- set a random default static IP 169.245.xx
- run a dhcp client and wait to get a lease
- keep this static IP as long as the nas does not receive a lease from a DCHP server
- set a next IP when it receive it

Yes, it is all right.
but the NAS doesn't send in broadcast a request of DHCP ip address lease.
So my DHCP server , does not release any ip, until it sees a request coming from a client (in this case the NAS).
the issue still in that.

;)