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

[Jocko]

What I think is after the disk boots a prosses is starting e.g.g. nzbget or transmission which consumes all proceszing power.

No I don't think so. If the fvdw-sl assistant does not detect the NAS, that would mean the boot script fails at some level and the iface is not set.

Maybe sda2 is also corrupted:

Code: Select all

root@fvdw-sta-kirkwood:/ # mount /dev/sda2 /sda2
mount: mounting /dev/sda2 on /sda2 failed: Input/output error

Now as you can get a telnet access and you only want to recover data, you may install vsftpd server and by using a ftp client copy the data on another host (the host where you use the ftp client)

So read the fvdw's post to install it: http://plugout.net/viewtopic.php?f=26&t=2508&start=20#p22816
mount sda8 partition

Code: Select all

mkdir /sda8
mount /dev/sda8 /sda8

on your laptop, use a ftpclient like filezilla and connect to the ftp server with the credential giving by fvdw.

Caution: you absolutely must use the binary transfer mode

Otherwise, for my knowledge, can you post again your boot.log on sda2

Code: Select all

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

[fvdw]

Suggestion. If as well sda1 and sda2 are corrupt why not use the fvdw-sl console action "write firmware image" to install the latest version on both partitions.

Remark having two corrupt partitions is peculiar and abnormal. It might indicate that the hdd has more problems and close to end of life. Anyhow if after writing the image still you have a not working nas, I would advice to proceed as Jocko suggest in his last post to get the data secured as soon as possible before the fails completely.
There are error messages in dmesg like erno -16 and chs that could be signs of a failing disk

[brinka123]

Before I am going to write on the disk. First I am going to retrieve the data. I pulled out the disk already it is recognized. Now i have to mount it on a linux alike machine. Maybe umbuntu or the rasberry. I bought new disk already. Want to place this in the lacie. Than put the data on it.
Keep you informed.

[Jocko]

@fvdw

Just because there are bad blocks on the disk:

Code: Select all

[   93.735075] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[   93.742145] ata1.00: failed command: READ FPDMA QUEUED
[   93.747347] ata1.00: cmd 60/20:00:00:00:00/00:00:00:00:00/40 tag 0 ncq 16384 in
[   93.747347]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   93.762022] ata1.00: status: { DRDY }
[   93.765731] ata1: hard resetting link
[   99.315006] ata1: link is slow to respond, please be patient (ready=0)
[  103.815006] ata1: SRST failed (errno=-16)
[  103.819029] ata1: hard resetting link
[  109.365006] ata1: link is slow to respond, please be patient (ready=0)
[  113.865007] ata1: SRST failed (errno=-16)
[  113.869036] ata1: hard resetting link
[  119.415008] ata1: link is slow to respond, please be patient (ready=0)
[  123.195026] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[  123.415074] ata1.00: configured for UDMA/133
[  123.419391] ata1.00: device reported invalid CHS sector 0  <--- here
[  123.424877] ata1: EH complete

So rewrite the file image should not change the state without repairing the disk (if it can)

[brinka123]

What I want to know is: So ther are 2 partions with boot data. How are these used during bootup? When sda1 fails sda2 is tried? Or is it a static backup?
How can I see ( in the future )that the disc is degrading?
What is the simples solution in my situation to in stall a new clean disk ?

[Jocko]

Sda1/2 partitions are used to upgrade the firmware with a rotate process (e.g. you have version 15.1 on sda2 and 15.2 on sda1)

If you want to check the disk, the best way is:
- download seagate tools http://www.seagate.com/nl/nl/support/downloads/seatools/ on your laptop
- extract the disk from the Lacie box and plug it in your laptop

then use the tools to investigate if the disk can be repaired

[brinka123]

What is on sda7? This is the application data and direction to sda1 or sda2?
When I mount sda7 it takes about 2 minutes using telnet. Could there be a mount time out during boot?

[Jocko]

When I mount sda7 it takes about 2 minutes using telnet. Could there be a mount time out during boot?

I do not think so

As before rename sda1boot, the bootloader load the root script from sda7 and then chroot the fs on sda1 (we have this trace with boot.log file on sda7 and sda1). So if the bootloader had failed to detect sda7, we would not have these traces.

So currently the settings are : the bootloader load the root script sda7 and then chroot the fs on sda2 (but you did not post the boot.log on sda2 after your 2d reboot try)

About sda7, the bootloader on these lacie NAS searches the init script on sda7 (no way to change that). So sda7 is fully used after a first install but as soon as you have upgraded the firmware it is used only to load the fs from sda1 or sda2.
The issue to use it for a full boot from it, is you have a too old firmware version on it (version 11.0)

But maybe it is worth to try to write the firmware on sda7 (version 16.1) with fvdw-sl console and see what happens :?

[brinka123]

So the log of sda2. I powered up the disk several times.

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:/ #


What does this date mean: ?
Sat Mar 29 23:01:52 GMT+1 2014
Should this be the startup time?

[Jocko]

Yes that is and it is strange to have the same date as the previous tries.

So on the telnet access, do

Code: Select all

mkdir /sda2 (if you have reboot the nas)
mount /dev/sda2 /sda2  (if you have reboot the nas)
mv /sda2/boot.log /sda2/boot.log.org

Then try to reboot the nas and as surely you still do not get an access on the nas, open again the telnet access and see if you find a new boot.log file.

if not that would mean init script failed to chroot the fs on sda2.

Then you should try to write fvdw-sl vers 16.1 on sda7