Problem finding Nas after upgrading to new firmware version

[Jocko]

fvdw-sl console can not be used to upgrade the firmware.

You should be able to install version 18.2 if the patch11 for version 17.0 is installed: https://plugout.net/viewtopic.php?f=7&t=2695&start=10#p29940 (which should be the case)

[leone101]

Finally i installed 18.2 firmware without any problem!
Thanks….really thaks for your patience and assistance!
wish u merry Christmas and happy new year!
:woohoo

[Jocko]

So the issue is solved :thumbup
Thank you for you feedback and wishing you a Merry Christmas

[leone101]

Thanks to u!
:hail :hail :hail

[leone101]

Hi Joko ì.m sorry to disturb u again but my nas has the same problem of the biginning of post, that is why i didn t open new one but decided to answer on that one.
It happened after 3 weeks i was out from home and i disconnected nas from DC.
I noticed the nas can't be seen in network.....i remember i already upgraded to 18 firmware and before asking your help i tried already using FVDW 6 console using UIMAGE kirkwood .... i prevently disabled eset internet security and started standlone kernel ......all procedure was ok till telnet opening....at this point telnet ends without giving me possibility to enter with user and password.
the nas is under router and not connected directly to pc.
I already tried to use FVDW assistant to check my nas address but is says kirkwood is on ip 192.168.1.252.
what i should do to have telnet permission to enter and show u problem from my nas firmware that fault?
Thanks
Regards

[fvdw]

Hi you must use the kirkwood standalone kernel when you use option standalone kernel in fvdw-sl console

If you did that and when fvdw-sl assistant says kirkwood is on 192.168.1.252 then use this ip in the telnet client to connect. It can happen that in case the nas takes long to boit due to disk issues that the telnet client times out. In the menu har of the telnet client there is a button that can be used to connect manually after telnet has timed out

[leone101]

Hi fwdw thanks so much for your replay!
I thanks you because i missed last step and i reached to enter in telnet with user and password
i tried commands and this was result:

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-45
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
nwsp2
 mount dev/pts
update dev nodes
booting using sda1 root file system...
enable IP forwarding...
run udevstart to update dev nodes when necessary
depmod: can't change directory to '4.14.133': No such file or directory
inserting kernel modules:
depmod: can't change directory to '4.14.133': No such file or directory
modprobe: can't change directory to '4.14.133': No such file or directory
modprobe: can't change directory to '4.14.133': No such file or directory
modprobe: can't change directory to '4.14.133': No such file or directory
modprobe: can't change directory to '4.14.133': No such file or directory
modprobe: can't change directory to '4.14.133': No such file or directory
start buttons control daemon
device = nwsp2
source = buttons-nwsp2
buttons-nwsp2 daemon started
initializing date
Mon Jan  1 12:00:00 CET 2018
create temporary passwd file
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 Vol-A:  [ 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 patched
    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
start boot log
is a physical machine
detect and set platform
nwsp2
kirkwood
 mount dev/pts
update dev nodes
root@fvdw-sta-kirkwood:/ #

[fvdw]

According this in boot.log of sda7

Code: Select all

booting using sda2 file system...

the nas tries to boot from sda2 but fails

When running standalone kernel please mount sda7 and give a command to list content of folder /lacie-boot

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
ls -al /lacie-boot

Lets try following
check why it takes so long to boot standalone kernel
Post output when running standalone kernel of this command

Code: Select all

dmesg

And lets see if the file system on sda2 must be repaired
When running standalone kernel give command

Code: Select all

fvdw-sl-programs

Choose option load mini glibc and tools.
After that give this command

Code: Select all

e2fsck -fy /dev/sda2

When being in

[leone101]

so according to u i have to enter again in telnet and try all commands you write in sequence u gave me or i need to use different sequence?

[fvdw]

so according to u i have to enter again in telnet and try all commands you write in sequence u gave me or i need to use different sequence?

yes start standalone kernel connect via telnet and give the commands