After a few years use can't access the nwsp2 via network

Re: After a few years use can't access the nwsp2 via network

Postby Jocko » Fri Oct 07, 2016 5:07 pm

So that means at least sda1 is corrupted by bad blocks.

If you just need to backup your data, we can try to boot from sda2 instead of sda1

So still with the telnet access, do:
(I assume sda7 is still mounted)
Code: Select all
mv /sda7/lacie-boot/sda1boot /sda7/lacie-boot/sda2boot


Then restart the NAS
Code: Select all
reboot -f


And look at if fvdw-sl assistant detects your NAS (after ~1min)
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: After a few years use can't access the nwsp2 via network

Postby brinka123 » Fri Oct 07, 2016 6:03 pm

using mount -t ext3 -o ro /dev/sda8 /share/1000 I see my data!!!!!!!

Now how do I retrieve it from the disk??
brinka123
Donator VIP
Donator VIP
 
Posts: 126
Joined: Sat Nov 17, 2012 3:06 pm

Re: After a few years use can't access the nwsp2 via network

Postby Jocko » Fri Oct 07, 2016 6:12 pm

Yes I know that

And do what I wrote in my previous post!
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: After a few years use can't access the nwsp2 via network

Postby brinka123 » Fri Oct 07, 2016 6:27 pm

Assistent doesnt find it. Addres is the same as in the console.
brinka123
Donator VIP
Donator VIP
 
Posts: 126
Joined: Sat Nov 17, 2012 3:06 pm

Re: After a few years use can't access the nwsp2 via network

Postby Jocko » Fri Oct 07, 2016 6:37 pm

So
a last try (with sda7)

- get a telnet access on your nas and post
Code: Select all
mkdir /sda2
mount /dev/sda2 /sda2
mount
cat /sda2/boot.log

mkdir /sda7
mount /dev/sda7 /sda7
mount
cat /sda7/etc/fvdwversion
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: After a few years use can't access the nwsp2 via network

Postby brinka123 » Fri Oct 07, 2016 7:04 pm

Thanks for you patience and help.
This is what I see:
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:/ # mount
rootfs on / type rootfs (rw,size=124976k,nr_inodes=31244)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sda2 on /sda2 type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
root@fvdw-sta-kirkwood:/ # cat /sda2/boot.log
start boot log
detect and set platform
nwsp2
UIMAGE-395-199
nwsp2
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 = nwsp2
source = buttons-nwsp2
buttons-nwsp2 daemon started
Sat Mar 29 23:01:52 GMT+1 2014
create temporary passwd file
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'ehci_hcd' not found
modprobe: module 'usb_storage' not found
modprobe: module 'usblp' not found
modprobe: module 'iscsi_trgt' not found
modprobe: module 'iscsi_tcp' not found
configure loopback netwerk interface
setting reboot and standby
nwsp2
rebootd-nwsp2
nwsp2
standbyd-nwsp2
starting php based setup routines step 1

 * Found XML database configuration file...      [ OK ]
 * Starting udevd...                                     [ 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 ]
 * Configuring Disks...                                  [ OK ]
 * Configuring Samba...                                  [ OK ]
 * Configuring System Users...
        Root password: use default password
        Set users, linux and samba accounts      [ OK ]
 * Starting syncawayd...                                 [ 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 Disk Temperature Guard...    [ OK ]
 * Starting NTP client...                                [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 15.1 patched
    built on: Januari 26 2013

    LAN IP address: 192.168.2.91 (DHCP)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
else loop1 finished
rcS finished
root@fvdw-sta-kirkwood:/ # mkdir /sda7
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # mount
rootfs on / type rootfs (rw,size=124976k,nr_inodes=31244)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sda2 on /sda2 type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
/dev/sda7 on /sda7 type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
root@fvdw-sta-kirkwood:/ # cat /sda7/etc/fvdwversion
fvdw-sl 11.0
root@fvdw-sta-kirkwood:/ #
brinka123
Donator VIP
Donator VIP
 
Posts: 126
Joined: Sat Nov 17, 2012 3:06 pm

Re: After a few years use can't access the nwsp2 via network

Postby Jocko » Fri Oct 07, 2016 7:22 pm

Well,

It won't be a good idea to load fvdw-sl from sda7 : it is a very old version and surely there is now some unsupported settings in the nas database.

But I think you made an error with the previous try as in boot.log stored in sda2 I found the same time:
Code: Select all
Sat Mar 29 23:01:52 GMT+1 2014


So post
Code: Select all
ls -l /sda7/lacie-boot
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: After a few years use can't access the nwsp2 via network

Postby brinka123 » Fri Oct 07, 2016 8:41 pm

Code: Select all
root@fvdw-sta-kirkwood:/ # ls -l /sda7/lacie-boot
total 0
-rw-r--r--    1 root     root             0 Apr 18  2014 sda2boot
root@fvdw-sta-kirkwood:/ #
brinka123
Donator VIP
Donator VIP
 
Posts: 126
Joined: Sat Nov 17, 2012 3:06 pm

Re: After a few years use can't access the nwsp2 via network

Postby Jocko » Fri Oct 07, 2016 8:44 pm

So reboot the NAS by unplugging the power supply
Do not use the fvdw-sl console and see if the NAS is detected by fvdw-sl assistant (after rebooting the NAS, when 1 minute and repeat several times "autoscan" )
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: After a few years use can't access the nwsp2 via network

Postby brinka123 » Sat Oct 08, 2016 7:14 am

Hi
According to me the nwsp2 boots. But the network assistant doenst find it. I also tried when firewalls and virus software was stopped. The assistent doesnt find it. What I think is after the disk boots a prosses is starting e.g.g. nzbget or transmission which consumes all proceszing power. Can I access parameters to disable these applications?
What I also going to do is mount the disk on my rasberry bi to retreive the data.

Do you have other options to check what the is gonging on?
brinka123
Donator VIP
Donator VIP
 
Posts: 126
Joined: Sat Nov 17, 2012 3:06 pm

PreviousNext

Return to Lacie Network Space vs2 and max version

Who is online

Users browsing this forum: No registered users and 5 guests