Problem finding Nas after upgrading to new firmware version

Re: Problem finding Nas after upgrading to new firmware vers

Postby fvdw » Wed Sep 14, 2022 6:36 pm

That means file system on sda2 is corrupt
We can try to boot from sda1
To do that connect with standalone kernel.
Give these commands
Code: Select all
mkdir /sda7
mount /dev/sda7 /sda7
cd /sda7/lacie-boot
ls

It should give as output sda2boot
If so then change the filename
Code: Select all
mv sda2boot sda1boot

Now give again the command
Code: Select all
ls

To see if name of file has changed to sda1boot

If ok reboot the nad
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Problem finding Nas after upgrading to new firmware vers

Postby leone101 » Wed Sep 14, 2022 7:03 pm

i did it:
fvdw-sta-kirkwood login: root
Password:
root@fvdw-sta-kirkwood:/ # mkdir /sda7
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # cd /sda7/lacie-boot
root@fvdw-sta-kirkwood:/sda7/lacie-boot # ls
sda2boot
root@fvdw-sta-kirkwood:/sda7/lacie-boot # mv sda2boot sda1boot
root@fvdw-sta-kirkwood:/sda7/lacie-boot # ls
sda1boot
root@fvdw-sta-kirkwood:/sda7/lacie-boot # reboot -f

.....still the same at reboot...... :cry:
leone101
Donator VIP
Donator VIP
 
Posts: 88
Joined: Sun Apr 02, 2017 7:21 am

Re: Problem finding Nas after upgrading to new firmware vers

Postby fvdw » Thu Sep 15, 2022 7:52 am

Unlikely but possible that also sda1 is corrupt. That might indicate that your disk has a hardware problem.
Now before jumping to conclusions lets try to boot from sda7
Following commands
Code: Select all
mkdir /sda7
mount /dev/sda7 /sda7
cd /sda7/lacie-boot
unlink sda1boot
ls

Now the ls command should not list any files
If thats the case reboot and see what happens.
If boot fails load again the standalone kernel and do the commands to list content of the boot.log on sda7

Note as sda7 will contain an older version of the fvdw-sl version, the version you used for first install. So upgrading will be required.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Problem finding Nas after upgrading to new firmware vers

Postby leone101 » Thu Sep 15, 2022 11:14 am

hi fvdw i tried what u asked me to do and these are result....hope i didn't anything wrong...

root@fvdw-sta-kirkwood:/ # mkdir /sda7
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # cd /sda7/lacie-boot
root@fvdw-sta-kirkwood:/sda7/lacie-boot # unlink sda1boot
-sh: unlink: not found
root@fvdw-sta-kirkwood:/sda7/lacie-boot # ls
sda1boot

and after that i reboot but nothing so i tried boot.log as requested:

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 sda1 file system...
else loop1 finished
rcS finished
leone101
Donator VIP
Donator VIP
 
Posts: 88
Joined: Sun Apr 02, 2017 7:21 am

Re: Problem finding Nas after upgrading to new firmware vers

Postby fvdw » Thu Sep 15, 2022 2:09 pm

You didn' t check if sda1boot was deleted. It wasn't because unlink failed
Try this command after mounting sda7 and cd /sda7/lacie-boot
Code: Select all
busybox unlink sda1boot

If this command also fails try
Code: Select all
rm sda1boot

Or
Code: Select all
busybox rm sda1boot

Check with ls if sda1boot is gone.
If still not gone rename it
Code: Select all
mv sda1boot sda3boot
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Problem finding Nas after upgrading to new firmware vers

Postby leone101 » Thu Sep 15, 2022 5:46 pm

here it is....

root@fvdw-sta-kirkwood:/ # mkdir /sda7
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # cd /sda7/lacie-boot
root@fvdw-sta-kirkwood:/sda7/lacie-boot # busybox unlink sda1boot
unlink: applet not found
root@fvdw-sta-kirkwood:/sda7/lacie-boot # rm sda1boot
root@fvdw-sta-kirkwood:/sda7/lacie-boot # ls
root@fvdw-sta-kirkwood:/sda7/lacie-boot #

i rebooted.....but still the same.... i start feeling with no chance to recover datas :cry:
leone101
Donator VIP
Donator VIP
 
Posts: 88
Joined: Sun Apr 02, 2017 7:21 am

Re: Problem finding Nas after upgrading to new firmware vers

Postby fvdw » Thu Sep 15, 2022 7:33 pm

As requested post now output of command cat boot.log on sda7
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Problem finding Nas after upgrading to new firmware vers

Postby leone101 » Thu Sep 15, 2022 7:46 pm

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 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
Sun Nov 13 04:45:51 CET 2016
create temporary passwd file
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
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

* Found XML database configuration file... [FAIL]
database corrupt !
Loading the bak copy of the database !
* Starting udevd... [ OK ]
* Finishing restore RAID devices... [ OK ]
* Updating Disks database... [ OK ]
* Starting mount of volumes...
- Mounting volume SD-Card: [ Fail ]
* Finishing mount of volumes... [ Fail ]

Warning: Invalid argument supplied for foreach() in /etc/finc/exthddfunc_wait_allmountExtHdd.finc on line 96
* Generating Hosts File... [ OK ]
* Configuring System Hostname... [ OK ]
* Configuring LAN interface... cannot start udhcpc process.
* Initializing Timezone... [ OK ]
* Starting web server...
Warning: Invalid argument supplied for foreach() in /etc/finc/sysfunc_password_configure.finc on line 18
[ OK ]
* Starting mount of internal USB ...
* Finishing mount internal USB ... [ OK ]
* Configuring Disks... [ Fail ]
* Configuring Samba... [ OK ]
* Configuring System Users...
Root password: use default password
Set users, linux and samba accounts [ OK ]
* Starting Fvdw-sl Discovery Daemon... [ OK ]
start rpcbind service
starting php based setup routines step 2
* Starting dropbear... [ OK ]
* Kill temporary dropbear... [ FAIL ]
starting php based setup routines step 3
* Starting daemon update Hosts File... [ OK ]
* Starting mount of remote shares...
* Finishing mount shares... [ OK ]
* Starting NTP client... [ FAIL ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
This is fvdw-sl version: fvdw-sl 16.1 patched
built on: Oct 01 2015

LAN IP address: 127.0.0.1 (static)

Port configuration:

LAN ->
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
move some smbd en nmbd db files from to prevent samba issue when copying large amounts of files (more then 50 thousand)
LED settings
else loop1 finished
rcS finished
root@fvdw-sta-kirkwood:/ #
leone101
Donator VIP
Donator VIP
 
Posts: 88
Joined: Sun Apr 02, 2017 7:21 am

Re: Problem finding Nas after upgrading to new firmware vers

Postby fvdw » Fri Sep 16, 2022 7:52 am

Mmm..lots if problems also with this file system.
It also indicate that database on sda5 was corrupt. This typically may happen at power failures. Did that happen?. Also the name of volume to be mounted "sd-card" is strange. Did you try something with an usb stick?
Furthermore the udhcp process cannot start. The reason for that is probably that the netwerk interface is not up yet. However your network interface is not broken otherwise standalone kernel could not be loaded. Then also here we may have a corrupt file.
The only possibility I see now is reinstalling firmware on sda7 using fvdw-sl console. There is on option you can choose from the fvdw-sl-programs to write firmware to partition sda1, sda2 and sda7.

But looking to the amount of issues I am afraid that your harddisk has a problem causing file corruptions.
To see if your data us still accessible connect with standalone kernel and mount sda8 and list its content
Code: Select all
mkdir /sda8
mount /dev/sda8 /sda8
cd /sda8
ls

You can check the sub directories by using cd command to go into sub directory and then use ls command again
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Problem finding Nas after upgrading to new firmware vers

Postby leone101 » Fri Sep 16, 2022 11:21 am

First of all i want to say... i'm really thankfull to your assistence and patience.

i checked what u asked me and i can "luckly still access" to subdirectories of movies and tv series and datas i have installed on sda8....(hope this is kind of good news from the little disaster on my nas prospected from u)

The problem i think started because i had to be in hospital many days and in this period i disconnected power from nas because i thought could be damaged because of weather.......but i think damage happened at opposite because i was too much carefull to my nas :hammerhead :hammerhead :hammerhead ....

So.....now only u know way to save from that :hail
leone101
Donator VIP
Donator VIP
 
Posts: 88
Joined: Sun Apr 02, 2017 7:21 am

PreviousNext

Return to Lacie Network Space vs2 and max version

Who is online

Users browsing this forum: No registered users and 2 guests