web interface goes on and of

[wietje]

led stays blinking (first both leds one at the time,then 1 led ,the most on the side)
i could not make the directory public with lxterminal
i used file manager to make it

could that be the problem?

Command (m for help): p

Disk /dev/sdf: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6d24e09b

Device Boot Start End Blocks Id System
/dev/sdf1 1 32 256016 83 Linux
/dev/sdf2 * 33 64 257040 83 Linux
/dev/sdf3 65 96 257040 82 Linux swap
/dev/sdf4 97 60801 487612912+ 5 Extended
/dev/sdf5 97 144 384536 83 Linux
/dev/sdf6 145 60801 487226328+ 83 Linux

Command (m for help):

[fvdw]

The partition table looks good as well as the boot flag.
If the public folder is not there it is not a problem that will prevent the NAs from booting.
If it can not read the nas configuration file on sdf5 it will not boot.

But first
what command did you use tho write the firmware image to sdf1 and sdf2 ? and what twas the file name of the fime you have written to disk (should not have been the "bin" file but the unpacked "img" file xfvdw-sl-12-1-phn-4jun2012.img of 200 MB)

To see if the firmware is written properly you could connect the disk again to you PC running knoppix and mount the partitions.
For example to look in sdf2 (the one used for boot)
Open root shell, make a folder with name sdf1-test

Code: Select all

mkdir sdf2-test

and then mount the partition

Code: Select all

mount /dev/sdf2 sdf2-test

If this gives no error you can change to this direcorty

Code: Select all

cd sdf2-test

and do a directory listing

Code: Select all

ls

)

for example on my system it looks like this

Code: Select all

root@SPD8020:/ # mkdir /mnt/sda2
root@SPD8020:/ # mount /dev/sda2 /mnt/sda2
root@SPD8020:/ # cd /mnt/sda2
root@SPD8020:/mnt/sda2 # ls
bin       dev          lib         mnt      proc   sbin   tmp
boot      etc          linuxrc     nowhere  root   share  usr
boot.log  lost+found  opt      rw_fs  sys    var
root@SPD8020:/mnt/sda2 #

or detailed output
root@SPD8020:/mnt/sda2 # ls -l
total 104
drwxr-xr-x   2 root root  4096 2012-02-18 23:30 bin
drwxr-xr-x   2 root root  4096 2011-10-29 21:51 boot
-rw-r--r--   1 root root  4875 2012-03-06 23:50 boot.log
drwxrwxr-x   5 root root 12288 2012-03-07 00:49 dev
drwxrwxrwx  12 root root  4096 2012-03-22 19:24 etc
drwxr-xr-x   3 root root  4096 2011-11-19 22:52 lib
lrwxrwxrwx   1 root root    11 2011-10-29 21:51 linuxrc -> bin/busybox
drwx------   2 root root 16384 2008-01-03 22:21 lost+found
lrwxrwxrwx   1 root root    14 2012-03-07 00:48 mnt -> /rw_fs/tmp/mnt
drwxr-xr-x   2 root root  4096 2008-08-27 22:46 nowhere
drwxr-xr-x  10 root root  4096 2012-01-01 23:17 opt
drwxrwxrwx   2 root root  4096 2011-03-05 11:08 proc
drwxr-xr-x   2 root root  4096 2008-01-03 21:06 root
drwxr-xr-x   2 root root  4096 2012-03-07 00:48 rw_fs
drwxr-xr-x   2 root root  4096 2012-01-15 17:30 sbin
drwxrwxrwx   3 root root  4096 2012-01-08 20:24 share
drwxrwxrwx   2 root root  4096 2011-03-05 11:08 sys
lrwxrwxrwx   1 root root    10 2012-03-07 00:48 tmp -> /rw_fs/tmp
drwxrwxr-x  22 root root  4096 2012-03-07 00:48 usr
drwxr-xr-x   2 root root  4096 2012-03-07 00:48 var
root@SPD8020:/mnt/sda2 #



Same with sdf5
This should have a folder /etc containing the nas database

Code: Select all

root@SPD8020:/mnt/sda5/etc # ls
nas_conf_db.xml     ntp.conf
nas_ext_hdd_db.xml 
root@SPD8020:/mnt/sda5/etc #

[wietje]

i used the dd command as in the manual (dd if=/......)

root@Microknoppix:~# mkdir sda2-test
root@Microknoppix:~# mount /dev/sda2 sda2-test
mount: you must specify the filesystem type
root@Microknoppix:~#

[fvdw]

should not be necessary to specify filesystem but you should replace "sda" by the actually device id as detected by fdisk (in you previous post it was sdf)
If it insist to have filesystem type you could try
mount -t ext3 /dev/sdf2 sdf2-test

[wietje]

if i see with gparted sda1 ,sda2 and sda3 are unknown file system
can i write the sda1 and 2 back with the dd command?

[wietje]

yes,it starts
can get a connection via webbrowser
a lot more things to set
thats gonna take some time
first trying to make a drive letter for the drive
that i used to do with the program from philips
thanks for the help

the file a copied with the dd-command was not the right one
i needed to unpack it one time more

[fvdw]

the file a copied with the dd-command was not the right one
i needed to unpack it one time more

:doh :laughat :disapprove :pound :snicker

finally you got it working :punk :bananadance

I was just preparing an upload for you containing the right image. I already expected that maybe the unpacking of the bin file was not done properly. Its a bz2 compressed archive. If you use for instance 7-zip to extract it it is indeed necessary to do it twice. If you unpack it in Linux then you would need the tar -xjvf... command. Beside the disk image you will get several other files. Those are needed for the firmware upgrade routine.

Anyhow I can delete that post now as your problem is solved now

[wietje]

with dd command i have only i file that i putted in sda1
is that ok ?

[fvdw]

with dd command i have only i file that i putted in sda1
is that ok ?

please explain little more ?
you mean you still have the wrong file is in sda1 ? and only put the correct one in sda2 ? and you now have booted from sda2 (the one with the boot flag set) ?
If so and the spd8020 is booting then it is no problem. You could use the firmware upgrade menu of the webinterface to get a good image also on sda1, just install fvdw-sl-12-1 once more (use the bin file !). That then will overwrite sda1 with the correct image and let it boot from sda1

[wietje]

i unpacked the firmware file
first i get a*.bin
second i get a file without extention
third i get a file with *.img an some other files
its the *img that i did with the dd command
hope its ok
i do not want to start al over