Problem finding Nas after upgrading to new firmware version

[fvdw]

Yes that looks ok

[leone101]

i connected the new power supply and booting the nas normally the assistant for now recognize the nas on 192.168.1.13....i can't go in web interface but hd looks working lot for now.....led blinks but not fixed.
I tried Putty

This is result:

login as: root
root@192.168.1.13's password:
root@NetworkSpace2:/ # cat boot.log
start boot log
is a physical machine
detect and set platform
nwsp2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
nwsp2
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 = nwsp2
source = buttons-nwsp2
buttons-nwsp2 daemon started
Fri Sep 23 22:45:49 CEST 2022
create temporary passwd file
create temporary group file
set samba environment for version 3.0.37
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... [ FAIL ]
* Starting Twonky Server... [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
This is fvdw-sl version: fvdw-sl 18.1
built on: July 29 2019

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@NetworkSpace2:/ # login as: root
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 = nwsp2
source = buttons-nwsp2
buttons-nwsp2 daemon started
Fri Sep 23 22:45:49 CEST 2022
create temporary passwd file
create temporary group file
set samba environment for version 3.0.37
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... [ FAIL ]
* Starting Twonky Server... [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
This is fvdw-sl version: fvdw-sl 18.1
built on: July 29 2019

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

Hope to receive feedback from u soon.

[fvdw]

Well this looks much better. Web server seems to be loaded.
Lets check if it is running.
Connect with putty and give command

Code: Select all

ps -ef

And post output

[leone101]

i'm really disappointed....all was ok ...like i show u till this afternoon and now doesn't connect anymore to putty.....and doesn't show on assistant..... :hairpull :elec)
i rebooted router....i unplugged nas and reconnected but nothing.......

[fvdw]

:dontknow difficult to say whats wrong but it seems a hardware issue

[leone101]

so....according to u ..... should i try any other way to recover system failure or could i just try to save data from partition on pc?

[fvdw]

so....according to u ..... should i try any other way to recover system failure or could i just try to save data from partition on pc?

There is still one possibility and that is the utp cable between nas and your router. Exchange that and try again to connect, also try using the standalone kernel.
You could also try to install fvdw-sl firmware on another disk. If that works the old disk is the problem. If that also doesn't work the mainboard is the problem.
Other ten that I don't see other options left.

If system gets corrupt everytime after repairing it it becomes useless to attempt to repair again. The question is now is the harddisk the problem or the mainboard of the nas?. If it is the first then data on partition 8 may be impossible to recover. If it is the second the recover data via pc might be possible assuming it was not damaged by faulty maiboard.
You could try to copy data from partition 8 using a pc but you will need a pc that runs on linux or install a driver under windows to be able to read ext3 and ext4 formatted partitions

[leone101]

ok.....no change with new eth cable...
i think last chance is to recover data from sda8...
Is there a way to do that from console to PC HD using NAS usb plug....or i phisically need to unmount it from nas and plug into pc?
I have Vmware as virtualizing machine
and i have router NetGear R7800 with usb 3.0

[fvdw]

If you jave linux running in your virtual machine I advise to plug it into the pc

[leone101]

so i can't do it without unmountin hd from nas?