firmware loaded but IP address not found.

[lacee2u]

I just loaded the firmware (kirkwood standalone) on a 5big 2 using 29 July 2019 release fvdw-sl console 6-0 with 18-1 firmware installer and image writer.

I have just one disk installed (I received the unit with no drives as a used machine). The lacie firmware is note as 1.4.4 i think.

But the kirkwood seemed to load fully on telnet ( I could see the LAN ports flashing and drive slot flashing responding per the console and went through all actions including the reboot at the end. Everything looked sucessful in terms of loading the firmware.

The problem is I cant find the IP address and connect to the NAS. The assistant program does not find it either.

Any clues what is wrong? I have tried all manner of things on the network side (I am using a small network switch only not a router).

[fvdw]

In which slot dud you put the disk? It should be in the most lefthand slot seen from the back.

If you did that correctly then use the fvdw-sl console and load the standalone kernel at the telnet terminal give command

Code: Select all

cat /boot.log

en post output here

[lacee2u]

Hello and thanks for answering! (sorry, I was away for a couple days).

I loaded the kirkwood standalone using the the console and logged in on telnet but the boot.log could not be found.

Oddly, while the standalone was loaded I was able to ping the 5big2 using the IP 172.23.95.252 (pc is 172.23.95.213). The assistant also found the NAS when in this state. After rebooting the assistant could not find the IP.

But here is what the telnet said:

fvdw-sta-kirkwood login: root
Password:
root@fvdw-sta-kirkwood:/ # cat /boot.log
cat: can't open '/boot.log': No such file or directory
root@fvdw-sta-kirkwood:/ #


MORE INFO:

I am using windows 10 on the PC. Firewall is off.

The Uboot on the machine is version 1.1.4.

When I earlier installed the firmware I had to manually upload the installer script. All steps completed successfully per the script and after reboot the drive does appear to be doing something and the network port is active but no IP address found (172.23.95. 252 could no longer be pinged). I did note that the formatting steps only took about 5 seconds (2TB drive) even though the script said the process would take some time.


Let me know if there is more data you need.

[lacee2u]

Oh yes I did have only one drive in the left slot (#1). Also using lan 1.

[fvdw]

O sorry my mistake.
When standalone kernel has been loaded give these commands in telnet terminal

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
cat /sda7/boot.log

And post output.

Ps. I assume you have the disk installed

[lacee2u]

OK so here id the output. Yes disk is installed.


start boot log
is a physical machine
detect and set platform
5big2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
5big2
kirkwood
mount dev/pts
update dev nodes

start boot log
is a physical machine
detect and set platform
5big2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
5big2
kirkwood
mount dev/pts
update dev nodes
booting using root file system...
enable IP forwarding...
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
start buttons control daemon
device = 5big2
source = buttons-nwsp2
buttons-nwsp2 daemon started
initializing date
Mon Jan 1 12:00:00 UTC 2018
create temporary passwd file
create temporary group file
set samba environment for version 3.0.37
configure loopback network interface
setting reboot and standby
5big2
root@fvdw-sta-kirkwood:/ #

Hope this helps.

[fvdw]

This boot.log is incomplete, did you copy all the output?
To see if firmware is loaded correctly we nee all output.
Ps at the end of the boot.log the ip is mentioned assigned to the nas

[lacee2u]

trying that now

[lacee2u]

Here is the output. What was odd in the log sent earlier is I set the telnet to full screen to copy but when i did that the bottom entries disappeared> so i opened the log a second time and the below is what came up.


start boot log
is a physical machine
detect and set platform
5big2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
5big2
kirkwood
mount dev/pts
update dev nodes
booting using root file system...
enable IP forwarding...
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
start buttons control daemon
device = 5big2
source = buttons-nwsp2
buttons-nwsp2 daemon started
initializing date
Mon Jan 1 12:00:00 UTC 2018
create temporary passwd file
create temporary group file
set samba environment for version 3.0.37
configure loopback network interface
setting reboot and standby
5big2
rebootd-nwsp2
5big2
standbyd-nwsp2
start fan
starting php based setup routines step 1
* Initialize the volatile db file... [ OK ]
* Starting udevd... [ OK ]
* Finishing restore RAID devices... [ OK ]
* Found database configuration file... [ OK ]
* Updating Disks database... [ OK ]
* Starting mount of volumes...
- Mounting volume Vol-A: [ OK ]
* Finishing mount of volumes... [ OK ]
* Generating Hosts File... [ OK ]
* Configuring System Hostname... [ OK ]
* Configuring LAN interface... root@fvdw-sta-kirkwood:/ #

when it was loading i did see the line saying "our ip address is 172.23.95.252"

[fvdw]

The output is still incomplete....

when it was loading i did see the line saying "our ip address is 172.23.95.252

Thats an ip used by the standalone kernel. When firmware is running the ip will be different.

Ps the part of the boot.log output you posted looks normal, but there must be more