no ip address, unable to access the NAS

Re: no ip address, unable to access the NAS

Postby danilomag » Mon Jun 26, 2023 8:53 am

[ img ]

I did exactly as you say, but it remains in this screen
danilomag
Donator VIP
Donator VIP
 
Posts: 52
Joined: Fri Jun 23, 2023 8:38 am

Re: no ip address, unable to access the NAS

Postby fvdw » Mon Jun 26, 2023 8:56 am

Seems you did not select option install firmware but instead choose option uboot console in tvdw-sl console :scratch
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: no ip address, unable to access the NAS

Postby fvdw » Mon Jun 26, 2023 9:03 am

You replaced the puicture the first one you posted clearly showed message starting uboot netconsole.
That can only happen if you choose as option uboot console in fvdw-sl console.

If you then manually start telnet of course you will get connection refused message as no telnet server is running on the nas.
Now switch off you nas, select install firmware choose kirkwood standalone kernel, wait for window mentioning waiting for uboot and then power on your nas and report what happens in the window. If kernel loads and starts the window will close automatic after message starting kernel and after some time the telnet client will start automatic prompting you to login. Do not start anything manually just wait.
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: no ip address, unable to access the NAS

Postby danilomag » Mon Jun 26, 2023 9:21 am

yes, sorry you're right, I put the wrong screenshot. I have updated the previous post.
I wanted to try what happened with u-boot console.

[ img ]

and immediately after, this window closes and another one appears and the popup saying telnet refused
danilomag
Donator VIP
Donator VIP
 
Posts: 52
Joined: Fri Jun 23, 2023 8:38 am

Re: no ip address, unable to access the NAS

Postby fvdw » Mon Jun 26, 2023 9:44 am

Thats odd it seems there is no kernel uploaded.
Lets see if we can do it manually

Switch off the nas and close fvdw-sl console if you have that running
Start fvdw-sl console
choose as action start tftp server then choose action u-boot console
Wait for window waiting for uboot and then switch on your nas
Wait for the message with remark to click on the window and press enter
click on the window and press enter.
You should get a prompt: marvel>>
At this prompt type exactly these commands
Code: Select all
setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7

use the commands exactly as they are given so do not replace the parameters ipaddr and serverip leave them as they are in this command
PS the u-boot console window has a paste option (right click on title bar)
check if now bootargs parameter is set to this string
Code: Select all
printenv bootargs

proceed
Code: Select all
ide reset
tftpboot 0x800000 UIMAGE-3142-KIRKWOOD-171-standalone

You should see in the u-boot window that the kernel is uploaded looking something like this (example output your kernel name and size will be different
tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59
Using egiga0 device
TFTP from server 192.168.1.147; our IP address is 192.168.1.197
Filename 'UIMAGE-26394-NWSP2CL-59'.
Load address: 0x800000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
##########################
done
Bytes transferred = 3123520 (2fa940 hex)


If that is finished enter
Code: Select all
bootm

You should see in the u-boot window that the kernel is starte

If the kernel starts you should get detailed output of kernel laoding in the u-boot console window. If the kernel fails before netconsole is activated in the kernel then there will be no output
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: no ip address, unable to access the NAS

Postby fvdw » Mon Jun 26, 2023 9:50 am

I edited my previous post
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: no ip address, unable to access the NAS

Postby danilomag » Mon Jun 26, 2023 10:07 am

[ img ]
I feel stupid, I can not go further
danilomag
Donator VIP
Donator VIP
 
Posts: 52
Joined: Fri Jun 23, 2023 8:38 am

Re: no ip address, unable to access the NAS

Postby fvdw » Mon Jun 26, 2023 10:10 am

put your mouse on the window and click on it to select it then press enter.

If that doesn't work your firewall is blocking outbound traffic
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: no ip address, unable to access the NAS

Postby fvdw » Mon Jun 26, 2023 10:17 am

your firewall should be set to allow to pass firewall for clunc-open, nc, tftp-server, tftpd

Easier is to disable the firewall temporarily
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: no ip address, unable to access the NAS

Postby danilomag » Mon Jun 26, 2023 10:20 am

I have completely disabled the firewall. I don't use antivirus.
The modem has never assigned an IP address to the NAS.
danilomag
Donator VIP
Donator VIP
 
Posts: 52
Joined: Fri Jun 23, 2023 8:38 am

PreviousNext

Return to Lacie 5big Network vs2

Who is online

Users browsing this forum: Bing Bot and 5 guests