Page 2 of 4

Re: firmware loaded but IP address not found.

PostPosted: Sat Nov 11, 2023 9:29 pm
by lacee2u
trying rapidly again without setting telnet to fullscreen

Re: firmware loaded but IP address not found.

PostPosted: Sat Nov 11, 2023 9:55 pm
by lacee2u
This is all the log shows. When I copied it to text it made a space. I then opened the log again and everything on telnet is below.

Nothing else shows in the log. I think i did all correctly.


HERE IS WHAT TELNET SHOWS:


fvdw-sta-kirkwood login: root
Password:
root@fvdw-sta-kirkwood:/ #













root@fvdw-sta-kirkwood:/ # mkdir /sda7
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # cat /sda7/boot.log
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 ]
root@fvdw-sta-kirkwood:/ # cat /sda7/boot.log
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:/ #

:idea: ?

Re: firmware loaded but IP address not found.

PostPosted: Sat Nov 11, 2023 10:26 pm
by lacee2u
maybe I should try a windows 7 computer instead of 10.

Re: firmware loaded but IP address not found.

PostPosted: Sat Nov 11, 2023 10:53 pm
by lacee2u
I tried on windows 7 and got same log results, it ends when trying to assign IP address.

Is it possible the files to load program are corrupt?

I also did note that there was something i read on this forum about a 2big NAS with 1.1.4 uboot not having enough memory or NAND?

The 5big 2 I am trying to load says it has uboot 1.1.4.

Re: firmware loaded but IP address not found.

PostPosted: Sat Nov 11, 2023 10:54 pm
by fvdw
Windiws 10 is just fine. If the line configuring lan interface is really the last line it means that loading firmware failed either because you cut power before boot was finished or installation was incomplete or the package you used is corrupt. Be sure to use a wired connection between pc and router and if you have a wireless interface as well disable it. Installation by using wireless interface is known to corrupt data transfer.
I suggest you install the firmware again using wired connection.

Re: firmware loaded but IP address not found.

PostPosted: Sat Nov 11, 2023 10:58 pm
by fvdw
Your device is a 5big network 2. You used the right package.
If installation on windows 7 failed also I think the installation package is corrupt, that might happen if you downloaded the package with unstable internet connection. Maybe downloading t console package again may solve this

Re: firmware loaded but IP address not found.

PostPosted: Sat Nov 11, 2023 11:28 pm
by lacee2u
I have tried that when I originally loaded and could not find the IP address.

Will try that again or maybe there is another location for download/alternate repository?

Re: firmware loaded but IP address not found.

PostPosted: Sat Nov 11, 2023 11:29 pm
by lacee2u
is there SHA1 or MD5 hashes or the files?

Re: firmware loaded but IP address not found.

PostPosted: Sun Nov 12, 2023 1:16 am
by lacee2u
I found the MD5 hashes in the below thread. All the 5 files I downloaded match these MD5s. I wonder if I am running into a similar problem as I was also getting errors with 7 zip when unpacking them. I then tried WINRAR but the problem presents the same, no IP.

viewtopic.php?f=11&t=3496

When I check the main folder of the console program after unzipping it in 3 separate folders as a test I get 3 different sizes (only 100-150 bits different). Possibly I should unzip on a linux machine?

Thanks very much.

Re: firmware loaded but IP address not found.

PostPosted: Sun Nov 12, 2023 8:55 am
by fvdw
Using winrar or 7z should be ok. When you winrar how do you unpack the archive? You schould just unpack nr 1, winrara will automatic unpack them all. And what is the size of the firmware archive, the big file in the unpacked files, you find it in the folder firmware.
When installing via fvdw-sl console does the installation finish succesfully?
When you finished install do not reboot directly but look to content of the installer.log
In the telnet terminal type
Code: Select all
cat /installer.log

And post output