Fail to get an IP from DHCP server after installing fvdw-sl

[Draftmancorp]

Load the standalone kernel and mount sda7 (on your new 5big2) and check contentent if boot.log

Also put file sda2boot in /lacie-boot folder of sda7 so that it will boot from sda2 just like your old 5big2
So after tenet access mountsda7 on /sda7 list boot.log and put sda2boot in the right folder

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
cat /sda7/boot.log
cd /sda7/lacie-boot
touch sda2boot
cd /
umount /sda7
reboot -f

ok, here the response:

Code: Select all

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
booting using sda2 file system...
rcS finished
root@fvdw-sta-kirkwood:/ #


Code: Select all

root@fvdw-sta-kirkwood:/ # cd /sda7/lacie-boot
root@fvdw-sta-kirkwood:/sda7/lacie-boot # touch sda2boot
root@fvdw-sta-kirkwood:/sda7/lacie-boot # cd /
root@fvdw-sta-kirkwood:/ # umount /sda7
root@fvdw-sta-kirkwood:/ # reboot -f


i notice the strange blu solid led in the back... i don't remember that stay ever ever solid.

[fvdw]

So it booted from sda2, of course as we cloned sda7 of your old 5big2 :doh

Load standalone kernel connect telelnet mount /dev/sda2 on a folder /sda2 and list boot.log of sda2

Code: Select all

mkdir /sda2
mount /dev/sda2 /sda2
cat /sda2/boot.log
umount /sda2

[Draftmancorp]

So it booted from sda2, of course as we cloned sda7 of your old 5big2 :doh

Load standalone kernel connect telelnet mount /dev/sda2 on a folder /sda2 and list boot.log of sda2

Code: Select all

mkdir /sda2
mount /dev/sda2 /sda2
cat /sda2/boot.log
umount /sda2

Here the response:

Code: Select all

fvdw-sta-kirkwood login: root
Password:
root@fvdw-sta-kirkwood:/ # mkdir /sda2
root@fvdw-sta-kirkwood:/ # mount /dev/sda2 /sda2
root@fvdw-sta-kirkwood:/ # cat /sda2/boot.log
start boot log
detect and set platform
5big2
kirkwood
UIMAGE-466-KIRKWOOD-7
Current kernel: 4.6.6 #7 PREEMPT Sun May 7 11:50:52 CEST 2017
5big2
 mount dev/pts
update dev nodes
booting using sda2 root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
start buttons control daemon
device = 5big2
source = buttons-nwsp2
buttons-nwsp2 daemon started
Tue Jan  1 18:49:27 UTC 2013
create temporary passwd file
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
create temporary group file
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 ]
   - Mounting volume Vol-B:  [ OK ]
   - Mounting volume Vol-C:  [ OK ]
   - Mounting volume Vol-D:  [ OK ]
   - Mounting volume Vol-E:  [ OK ]
 * Finishing mount of volumes...                 [ OK ]
 * Generating Hosts File...                      [ OK ]
 * Configuring System Hostname...                [ OK ] 
 * Configuring LAN interface...                  [ OK ]
 * Initializing Timezone...                      [ OK ]
 * Starting web server...                                [ OK ]
 * Starting mount of internal USB ...
 * Finishing mount internal USB ...      [ OK ]
 * Configuring Disks...                                  [ OK ]
 * Configuring Samba...                                  [ OK ]
 * Configuring System Users...
        Root password: use custom password
        Set users, linux and samba accounts      [ OK ]
 * Starting DDNS Service...                      [ FAIL ]
 * Starting Fvdw-sl Discovery Daemon...  [ OK ]
start rpcbind service
starting php based setup routines step 2
 * Starting dropbear...                                  [ OK ]
 * Kill temporary dropbear...                    [ OK ]
starting php based setup routines step 3
 * Starting daemon update Hosts File...  [ OK ]
 * Starting mount of remote shares...
 * Finishing mount shares...                     [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 17.0
    built on: May 28 2017

    LAN IP address: 192.168.0.189 (static)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
move smbd en nmbd db files away from ram disk to prevent hanging samba server
LED settings
else loop1 finished
rcS finished
root@fvdw-sta-kirkwood:/ # umount /sda2
root@fvdw-sta-kirkwood:/ #

The ip is the same ip of the other nas :-D (that is power off under my desk)

[fvdw]

So according this log it seems to be up and running using the ip of your old 5big2.
However this can be a boot.log from your old 5big2 so it is misleading.
So again load standalone kernel mount /dev/sda2 and remove the boot.log

Code: Select all

rm /sda2/boot.log

Check if it gone

Code: Select all

ls /sda2

If gone umount /sda2

And reboot, and after reboot failed again load standalone kernel and read boot.log on sda2

Ps as you have set a static ip on your old 5big2 and we cloned that it will use the same ip as your old 5big2
So Shutdown your old 5big2 and connect to your new one using the ip in mentioned in boot.log 192.168.0.189

[Draftmancorp]

So according this log it seems to be up and running using the ip of your old 5big2.
However this can be a boot.log from your old 5big2 so it is misleading.
So again load standalone kernel mount /dev/sda2 and remove the boot.log

Code: Select all

rm /sda2/boot.log

Check if it gone

Code: Select all

ls /sda2

If gone umount /sda2

And reboot, and after reboot failed again load standalone kernel and read boot.log on sda2

Ps as you have set a static ip on your old 5big2 and we cloned that it will use the same ip as your old 5big2
So Shutdown your old 5big2 and connect to your new one using the ip in mentioned in boot.log 192.168.0.189

Wait, i'm here:

Code: Select all

root@fvdw-sta-kirkwood:/ # mount /dev/sda2 /sda2
root@fvdw-sta-kirkwood:/ # rm /sda2/boot.log
root@fvdw-sta-kirkwood:/ # ls /sda2
bin              dev              lib              mnt              proc             sda7-tmp         usr
bin_cab          direct-usb       linuxrc          nowhere          root             share            var
boot             etc              lost+found       opt              rw_fs            sys
clunc            lacie-boot       mail             postupgrade.log  sbin             tmp
root@fvdw-sta-kirkwood:/ #

How i know if "it gone?"
(yes is ever powered off the old nas)

[fvdw]

Its gone as it not listed anymore in the ls command so reboot again, if failed load standalone kernel and read boot.log on sda2 which should be recreated at the last boot

[Draftmancorp]

Its gone as it not listed anymore in the ls command so reboot again, if failed load standalone kernel and read boot.log on sda2 which should be recreated at the last boot

...can't open?

Code: Select all

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


[fvdw]

That means it didn't boot can only happen if it failed to load a kernel.
So lets try to use fvdw-sl console action load external kernel. In this case don't select the standalone kernel when it asks which kernel to load but select the kirkwood kernel without standalone in the name.

[fvdw]

The kernel can be found in tftp\firmware\kirkwood

[Draftmancorp]

That means it didn't boot can only happen if it failed to load a kernel.
So lets try to use fvdw-sl console action load external kernel. In this case don't select the standalone kernel when it asks which kernel to load but select the kirkwood kernel without standalone in the name.

ok, the only image without standalone is "UIMAGE-466-KIRKWOOD-7"
After perform console External kernel, load and start, the black transfer window appear and in the and (as other cases) appear load kernel ok etc...
The windows auto close as ever made, but then no telnet window open...