Help Needed! Can't acces data on Lacie

[senzas]

Hello all,

I'm using a Lacie network space vs 2 (Firmware version 12-1)
to automatically backup camera-uploads form dropbox thru a programm called Syncbackfree.
It worked like a charm untill now. I can't acces mij data anymore.
It startsup and i can feel and hear the harddisk running fine.
I can acces the web-admin and there it says there are no partitions or users available, free and used space are 0?

I've installed FVDW-SL console v. 5.5 and run some commands i've red in an other post on this forum.
Since i'me a total noob, the outcomes of these command-lines tell me nothing.
Can somebody help? Could it be that the partition(s) are somehow unmounted?

Thanks in advance!

Edit:
There has been a powerout a couple of weeks ago

Code: Select all

root@fvdw-sta-kirkwood:/ # cat /proc/partitions

major minor  #blocks  name

  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0  976762584 sda
   8        1     513056 sda1
   8        2     514080 sda2
   8        3     514080 sda3
   8        4          1 sda4
   8        5     802226 sda5
   8        6       7008 sda6
   8        7     513056 sda7
   8        8  973891406 sda8

root@fvdw-sta-kirkwood:/ # cat /proc/mounts

rootfs / rootfs rw,size=125060k,nr_inodes=31265 0 0
none /proc proc rw,relatime 0 0
none /sys sysfs rw,relatime 0 0
none /dev/pts devpts rw,relatime,mode=600 0 0

root@fvdw-sta-kirkwood:/ # cat /proc/mdstat

Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
unused devices: <none>
root@fvdw-sta-kirkwood:/ # fdisk -l

Disk /dev/mtdblock0: 0 MB, 512000 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 4096 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1          64      513056  83 Linux
/dev/sda2              65         128      514080  83 Linux
/dev/sda3             129         192      514080  82 Linux swap
/dev/sda4             193      121601   975217792+  5 Extended
/dev/sda5             193         292      802226  83 Linux
/dev/sda6             293         293        7008+ 83 Linux
/dev/sda7             294         357      513056  83 Linux
/dev/sda8             358      121601   973891406  83 Linux
root@fvdw-sta-kirkwood:/ #

[fvdw]

you should boot your nas a connect via server with a client like Putty. (username: root and password: giveit2me)
Then we can investigate what is wrong, it seem your main data base may have a problem because that contains all users and shared folders.
This might be caused besides by a corrupt database also by a failure to mount partition 5
Anyhow connect via ssh and give us the output of the command

Code: Select all

mount

If mount gives as output that sda5 and sda8 are mounted then have a look in folders
/share/1000

Code: Select all

cd /share/1000
ls


It should contain all your shared folders
and in the folder /rw_fs/etc you should find the the nas database
A file with name: nas_conf_db.xml

You can list conetnt bu using a command like

Code: Select all

cat nas_conf_db.xml

post the content
(ps the database content will show the passwords you have set, you might want to take these out before posting)

If sda5 or sda8 is not mounted we have a different problem

[senzas]

Hello fdvw,

Thanks for your quick response.

So I downloaded Putty, connected via SSH en typed in the command lines.
Hope i did it the right way...

Code: Select all

root@:/ # mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/sda1 on / type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=200k)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/root on /lacie-boot type ext3 (rw,relatime,errors=continue,barrier=0,data=o                                                                                        rdered)


Code: Select all

root@:/ # cd /share/1000
root@:/share/1000 # ls
tr-daemon


Code: Select all

root@:/rw_fs/etc # cat nas_conf_db.xml
<?xml version="1.0"?>
<nas_conf_db>
        <system>
                <platform>TG</platform>
                <drives>SingleDrive</drives>
        </system>
        <samba>
                <windmediadisable>yes</windmediadisable>
        </samba>
        <interfaces>
                <lan>
                        <rand_ip>169.xxx.xxx.xx</rand_ip>
                        <hwaddr>00:D0:xx:xx:xx:xx</hwaddr>
                </lan>
        </interfaces>
</nas_conf_db>


[fvdw]

Both sda5 and sda8 are not mounted, as a result you have a default database. We need to find why sda5 is not mounted.
Try to mount it manually

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5

If that succeeds and the command

Code: Select all

mount

now shows that it is mounted then something is wrong with the boot scripts.

I don't remember if we had already the boot.log.
Try this command to see if its there and what the content is

Code: Select all

cat /boot.log

[senzas]

It looks like I cant mount them manually..
Here's the code....

Code: Select all

root@:/ # mkdir /sda5
mkdir: cannot create directory `/sda5': File exists

root@:/ # mount /dev/sda5 /sda5
mount: mounting /dev/sda5 on /sda5 failed: Invalid argument

root@:/ # cat /boot.log
start boot log
Tue Oct  1 09:14:17 GMT+1 2013
booting using sda2 root file system...
run udevstart to update dev nodes when necessary
inserting kernel modules:
make dev node for buttons...
configure loopback netwerk interface
starting php based setup routines step 1


 * Initial Orion-Nas XML configuration file...           [ OK ]
 * Configuring Disks...                                  [ Fail ]
 * Configuring System Users...
Warning: fopen(/etc/rootpasswd): failed to open stream: No such file or director                                                                                        y in /etc/finc/userfunc_users_commit.finc on line 38
                                 [ OK ]
 * Starting mount of volumes...
 * Finishing mount of volumes...                         [ OK ]
 * Generating Hosts File...                              [ OK ]
 * Configuring System Hostname...                        [ OK ]
 * Configuring Samba...                                  [ OK ]
 * Configuring LAN interface...                          [ OK ]
 * Starting udevd...                                     [ OK ]
 * Starting web server...                                [ OK ]
 * Initializing Timezone...                              [ OK ]
 * Starting NTP client...                                [ Fail ]
 * Configuring Samba...                                  [ OK ]
 * Starting syncawayd...                                 [ OK ]
,QOSd...                         [ OK ]
starting php based setup routines step 2
 * Starting dropbear... cmd : dropbear -p 22 -r '/rw_fs/etc/dropbear/dropbear_rs                                                                                        a_host_key'                              [ OK ]


 * Starting daemon update Hosts File...                          [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 11.0
    built on: Januari 3 2012

    LAN IP address: 192.xxx.x.xx (static)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
start buttons control daemon
buttons-nwsp2 daemon started
web permission on resolv.conf
set device tuning for dms performance
move smbd en nmbd db files to ramdisk to enable disk spin down
rcS finished


[fvdw]

the fact that you cannot mount sda5 is not a good sign
can you try the same with sda8 ?

Code: Select all

mkdir /sda8
mount /dev/sda8 /sda8

If only sda5 failed it looks like sda5 partition is corrupt, it then uses a default database without reference to sda8 so that will not be mounted as well.

If sda88 mount you can check in /sda8 folder if still all your shared folders are present (that should be the case).

Never seen that we lost partition 5 but if it is the case then we need to reformat it , put a new database in it and restore users and shared folder names again

Maybe we can repair it by using e2fsck

Code: Select all

e2fsck /dev/sda5

after that try to mount it again
If it now mounts then reboot the nas and everything should be fine

[senzas]

I succeeded repairing SDA5 and SDA8...

Repairing SDA5 resulted in a bad cluster? Putty asked to rewrite and I chose yes.
After repairing I could mount SDA5 and SDA8...
I even could see my files again..via Putty

Now I have a different problem, after rebooting I cant connect anymore.
The networkspace doesnt show up on the network...

Any suggestions?

[fvdw]

reboot it again

did you use a static ip address in the past ?

[senzas]

Even after a reboot, several times, the networkspace doenst shows up on the network.
I'm using Fing to find the devices in my network.

In the past I used a static IP adress..

[fvdw]

:scratch

odd, then we need to use the fvdw-sl console and load the standalone kernel to see what is going on
viewtopic.php?f=7&t=2224#p7904
The fvdw-sl console runs under windows, are you familiar with that ?
It enbles you to run a standalone kernel, that kernel we can use to investigate the database on your nas