Problem finding Nas after upgrading to new firmware version

[leone101]

Hi, i upgraded the nas to last version of fvdw-sl directly from firmware auto updater from 17 version to last one.
The upgrading and installation ended without any errors.
Just now i reboot and i can't find my nas anymore.
Probably is in default ip or another one not in the same subnet and i can t reach it.
i also tried fvdw-sl assistant but in auto mode can't reach it
Could u please help me to find out it again?
Thanks

[Jocko]

Hi,

So only fvdw-sl console will allow to understand what it happened

Then you have to run the action "Load standalone kernel" to get a telnet access on the nas. (https://plugout.net/viewtopic.php?f=7&t=3086)
Please to read this topic if you have some connect issues: https://plugout.net/viewtopic.php?f=7&t=2645

When you are connected do:

Code: Select all

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

mount /dev/sda1 /sda1
cat /sda1/boot.log

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


Note: it will be easy to go back before upgrading

[leone101]

Thanks Jocko i will try sooner as i can if that is the only way to restore ip and subnet and enter in webinterface again :hammerhead
i'm just littlebit worried.....do u think i will succeed to access Nas using your procedure or i risk to loose datas stored inside?? :sob :sob :sob
regards

[Jocko]

I do not think it is an issue about IP settings because you would had to get it before upgrading. I believe the issue is the boot script aborts at a step whereas the iface is not yet brought up.

[leone101]

But….. according to u....i will lost data with your procedure? :sob :sob :sob
is it possible to try sort of soft reset?

[Jocko]

Except for a disk damage, your data are still here.

But let's what will say the boot log files

[leone101]

Hi,

So only fvdw-sl console will allow to understand what it happened

Then you have to run the action "Load standalone kernel" to get a telnet access on the nas. (https://plugout.net/viewtopic.php?f=7&t=3086)
Please to read this topic if you have some connect issues: https://plugout.net/viewtopic.php?f=7&t=2645

When you are connected do:

Code: Select all

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

mount /dev/sda1 /sda1
cat /sda1/boot.log

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


Note: it will be easy to go back before upgrading

i finally reach to enter in telnet mode after some problems solved by link you gave to me.
i did all but arriving at this last point of guide:
mount /dev/sda2 /sda2
cat /sda2/boot.log
it says to me: cat:can't open '/sda2/boot.log' : No such file or directory
i'm not expert of linux…..what i did wrong?

[Jocko]

Hi leone101,

You made nothing wrong. Having no boot.log file on sda2 is an information.
Please to post the other outputs!

And also these new ones :

Code: Select all

ls -l /sda2
ls -l /sda7/lacie-boot

(I assume you did not reboot the nas or in the other case, you made again the previous commands)

[leone101]

Code: Select all

fvdw-sta-kirkwood login: root
Password:
root@fvdw-sta-kirkwood:/ # mkdir /sda7 /sda1 /sda2
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # cat /sda7/boot.log
start boot log
detect and set platform
nwsp2
kirkwood
UIMAGE-3142-NWSP2CL-14
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
nwsp2
 mount dev/pts
update dev nodes
booting using sda2 file system...
else loop1 finished
rcS finished
root@fvdw-sta-kirkwood:/ # mount dev/sda1 /sda1
root@fvdw-sta-kirkwood:/ # cat /sda1/boot.log
start boot log
detect and set platform
nwsp2
kirkwood
UIMAGE-466-KIRKWOOD-7
Current kernel: 4.6.6 #7 PREEMPT Sun May 7 11:50:52 CEST 2017
nwsp2
 mount dev/pts
update dev nodes
booting using sda1 root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
start buttons control daemon
device = nwsp2
source = buttons-nwsp2
buttons-nwsp2 daemon started
Tue Nov 12 15:03:21 CET 2019
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
nwsp2
rebootd-nwsp2
nwsp2
standbyd-nwsp2
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 Default:  [ 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 default password
        Set users, linux and samba accounts      [ OK ]
 * Starting DDNS Service...                      [ OK ]
 * 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 NFS Server...                                [ OK ]
 * Starting daemon update Hosts File...  [ OK ]
 * Starting NTP Server ...                               [ OK ]
 * Starting mount of remote shares...
 * Finishing mount shares...                     [ OK ]
 * Starting FTP Service...                               [ OK ]
 * Starting NTP client...                                [ OK ]
 * Starting Minidlna Server...                   [ OK ]
 * Starting Twonky Server...                     [ 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.1.13 (DHCP)

    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:/ # mount /dev/sda2 /sda2
root@fvdw-sta-kirkwood:/ # cat /sda2/boot.log
cat: can't open '/sda2/boot.log': No such file or directory

This is all the device rooting in telnet
What is your suggestion?
Yes i'm still on telnet i didn't close it
P.S. Thanks a lot to answer me so soon

[Jocko]

So the bootloader works nicely and the issue is on sda2.

Please to post

Code: Select all

mount
ls -l /sda2