Help Needed! Can't acces data on Lacie

[senzas]

Yes.. I'm logged in right now
What command line do I use...

[fvdw]

ok, as it seesm you were booting form sda1, first mount sda1

Code: Select all

mkdir sda1
mount /dev/sda1 sda1

and look to /sda1/boot.log content to see where the boot fails

Code: Select all

cat /sda1/boot.log

[senzas]

Thanks 4 your help so far, Fvdw!

On that NAS are some important files

Code: Select all

start boot log
booting using sda1 root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
start buttons control daemon
buttons-nwsp2 daemon started
Tue Oct  1 07:23:14 GMT 2013
run udevstart to update dev nodes when necessary
inserting kernel modules:
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 directory 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 ]
start portmap service
starting php based setup routines step 2
 * Starting dropbear...                                  [ OK ]
 * Kill temporary dropbear...                    [ FAIL ]


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


*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 12.1
    built on: June 3 2012

    LAN IP address: 192.xxx.x.xx (static)http://plugout.net/posting.php?mode=edit&f=11&p=19135#

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
starting minidlna server...
Error reading configuration file /share/1000/minidlna/minidlna.conf
Usage:
        /usr/sbin/minidlna [-d] [-f config_file]
                [-a listening_ip] [-p port]
                [-s serial] [-m model_number]
                [-t notify_interval] [-P pid_filename]
                [-w url] [-R] [-V] [-h]

Notes:
        Notify interval is in seconds. Default is 895 seconds.
        Default pid file is /var/run/minidlna.pid.
        With -d minidlna will run in debug mode (not daemonize).
        -w sets the presentation url. Default is http address on port 80
        -h displays this text
        -R forces a full rescan
        -V print the version number
move smbd en nmbd db files to ramdisk to enable disk spin down
starting transmission daemon...
rcS finished


[fvdw]

we will get this working again

it still doesn't seems to be able to mount the disks

Please do the same for /sda7

Code: Select all

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

and have a look which fils/dir's are present in /sda7/lacie-boot
you should find a file with name sda1boot

[senzas]

It seems like there is no log file within SDA7

Code: Select all

root@fvdw-sta-kirkwood:/ # cat /sda7/boot/log
cat: can't open '/sda7/boot/log': No such file or directory

root@fvdw-sta-kirkwood:/ # ls
bin      etc      ip.txt   linuxrc  proc     sda1     sys      var
dev      init     lib      mnt      sbin     sda7     usr

root@fvdw-sta-kirkwood:/ # cd /sda7
root@fvdw-sta-kirkwood:/sda7 # ls
bin          etc          linuxrc      opt          sbin         usr
boot         fvdw-chroot  lost+found   proc         share        var
boot.log     lacie-boot   mnt          root         sys
dev          lib          nowhere      rw_fs        tmp

root@fvdw-sta-kirkwood:/sda7 # cd /sda7/boot

root@fvdw-sta-kirkwood:/sda7/boot # ls
UIMAGE-26394-NWSP2CL-9  config-26394-nwsp2cl-9

root@fvdw-sta-kirkwood:/sda7/boot # cat /sda7/boot/log
cat: can't open '/sda7/boot/log': No such file or directory

root@fvdw-sta-kirkwood:/sda7/boot # cd /sda7/lacie-boot
root@fvdw-sta-kirkwood:/sda7/lacie-boot # ls
sda2boot

[fvdw]

ok
you must have an old installation, anyhow from /lacie-boot we learn that it is booting from sda2...

lets then mount sda2 and look at boot.log on that partition

[Jocko]

@senzas
fvdw made a small typo error, he wants the output of

Code: Select all

cat /sda7/boot.log

@fvdw
Do you note that in the first boot.log output firmware version is 11.0 and in the last output firmware version is 12.1 => this would mean that senzas made a downgrade ?

[fvdw]

oops sorry about that error on boot.log

yes I thought he was booting from sda1 because his mount command gave this output.

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)

this means sda1 is used as system disk...
next he post output of boot.log

Code: Select all

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...


this mentions sda2 as system partition

:tapfoot whats going on here, how can sda1 be mounted...

[senzas]

Hello Both,

I think 12-1 and 11 is my own fault ...
In a attempt to fix my problem I came across another post on this forum where some donwgraded the firmware via putty.
So i did the same. Maybe this causing the mis-understanding.
I apologize for this.....

Outcome boot.log on SDA 7

Code: Select all

root@fvdw-sta-kirkwood:/sda7/lacie-boot # cat /sda7/boot.log
start boot log
Wed Oct  2 03:59:53 GMT+1 2013
booting using sda2 file system...
rcS finished


Outcome boot.log SDA 2

Code: Select all

root@fvdw-sta-kirkwood:/sda2 # cat /sda2/boot.log
start boot log
Wed Oct  2 02:59:57 GMT 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 ]
starting php based setup routines step 2
starting php based setup routines step banner
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]

:twak ok that makes it more clear

seems sda2 is not ok it misses important part of the boot script output.

You could rename sda2boot in /sda7/lacie-boot to sda1boot

Code: Select all

mv /sda7/lacie-boot/sda2boot /sda7/lacie-boot/sda1boot

check that the name has cahnegd accordingly, and again reboot the nas