fvdw-sl doesnt work for me :(

[FoCMB]

i did these steps. forgot to copy ;)
here is the terminal output (in german)

root@fLaptop:/xxx/fvdw# mke2fs -j -m 1 /dev/sdb5
mke2fs 1.41.14 (22-Dec-2010)
Dateisystem-Label=
OS-Typ: Linux
Blockgröße=4096 (log=2)
Fragmentgröße=4096 (log=2)
Stride=0 Blöcke, Stripebreite=0 Blöcke
50176 Inodes, 200556 Blöcke
2005 Blöcke (1.00%) reserviert für den Superuser
Erster Datenblock=0
Maximale Dateisystem-Blöcke=205520896
7 Blockgruppen
32768 Blöcke pro Gruppe, 32768 Fragmente pro Gruppe
7168 Inodes pro Gruppe
Superblock-Sicherungskopien gespeichert in den Blöcken:
32768, 98304, 163840

Schreibe Inode-Tabellen: erledigt
Erstelle Journal (4096 Blöcke): erledigt
Schreibe Superblöcke und Dateisystem-Accountinginformationen: erledigt

Das Dateisystem wird automatisch nach jeweils 37 Einhäng-Vorgängen bzw.
alle 180 Tage überprüft, je nachdem, was zuerst eintritt. Dies kann durch
tune2fs -c oder -i geändert werden.
root@Laptop:/xxx/fvdw# mke2fs -j -m 1 /dev/sdb8
mke2fs 1.41.14 (22-Dec-2010)
Dateisystem-Label=
OS-Typ: Linux
Blockgröße=4096 (log=2)
Fragmentgröße=4096 (log=2)
Stride=0 Blöcke, Stripebreite=0 Blöcke
60874752 Inodes, 243472851 Blöcke
2434728 Blöcke (1.00%) reserviert für den Superuser
Erster Datenblock=0
Maximale Dateisystem-Blöcke=4294967296
7431 Blockgruppen
32768 Blöcke pro Gruppe, 32768 Fragmente pro Gruppe
8192 Inodes pro Gruppe
Superblock-Sicherungskopien gespeichert in den Blöcken:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848

Schreibe Inode-Tabellen: erledigt
Erstelle Journal (32768 Blöcke): erledigt
Schreibe Superblöcke und Dateisystem-Accountinginformationen: erledigt

[FoCMB]

root@Laptop:/# dd if=/xxx/fvdw/uImage-26331-2-nwsp2 of=/dev/sdb6
3595+1 Datensätze ein
3595+1 Datensätze aus
1840836 Bytes (1,8 MB) kopiert, 0,1343 s, 13,7 MB/s

[Jocko]

Um, it's strange all the steps have been made ...

Can you confirm that the LED never blinks at boot : the startup script does not run.

Please, send the output of these commands (after mounting devices /dev/sdb7 and /dev/sdb5) :

Code: Select all

mkdir /mnt-sdb5
mount /dev/sdb5 /mnt-sdb5

ls -al /mnt-sdb5
ls -al /mnt-sdb5/etc

mkdir /mnt-sdb7
mount /dev/sdb7 /mnt-sdb7

ls -al /mnt-sdb7



[fvdw]

@FoCMB
which program did you use to make the partitions ?
There is something odd in your partiton table, the number of blocks is for some partitions not correct
When you follow the how to guide and use fdisk then you should get exactly the table as mentioned in the how to guide.

[FoCMB]

the amber led blink 2 or 3 times at boot, then never.

here the outputs:

root@Laptop:/# mount /dev/sdb5 /mnt-sdb5
root@Laptop:/# ls -al /mnt-sdb5
insgesamt 44
drwxr-xr-x 7 root root 4096 2011-10-05 20:28 .
drwxr-xr-x 27 root root 4096 2011-10-04 20:42 ..
drwxr-xr-x 2 root root 4096 2011-08-12 17:26 etc
drwx------ 2 root root 16384 2000-01-01 21:40 lost+found
-rw-r--r-- 1 root root 2094 2011-10-05 20:28 sda5-lacie-nwsp.tar.gz
drwxr-xr-x 2 root root 4096 2011-08-12 17:51 tmp
drwxr-xr-x 3 root root 4096 2011-08-12 17:26 usr
drwxr-xr-x 3 root root 4096 2011-08-12 17:26 var

root@Laptop:/# ls -al /mnt-sdb5/etc
insgesamt 20
drwxr-xr-x 2 root root 4096 2011-08-12 17:26 .
drwxr-xr-x 7 root root 4096 2011-10-05 20:28 ..
-rwxrwxrwx 1 root root 3420 2011-08-12 17:47 nas_conf_db.xml
-rw-r--r-- 1 root root 104 2009-03-15 18:16 nas_ext_hdd_db.xml
-rw-r--r-- 1 root root 40 2009-10-03 22:21 ntp.conf

root@Laptop:/# ls -al /mnt-sdb7
insgesamt 80
drwxr-xr-x 16 root root 4096 2011-03-05 14:38 .
drwxr-xr-x 28 root root 4096 2011-10-05 21:40 ..
drwxr-xr-x 2 root root 4096 2011-08-13 00:18 bin
drwxr-xr-x 2 root root 4096 2011-08-13 00:44 boot
drwxrwxr-x 4 root root 8192 2011-02-07 22:17 dev
drwxrwxrwx 11 root root 4096 2011-08-13 00:10 etc
drwxr-xr-x 3 root root 4096 2011-02-28 21:19 lib
lrwxrwxrwx 1 root root 11 2009-02-09 22:55 linuxrc -> bin/busybox
drwx------ 2 root root 16384 2008-01-03 22:21 lost+found
drwxr-xr-x 2 root root 4096 2008-08-27 23:46 nowhere
drwxr-xr-x 10 root root 4096 2009-02-12 21:22 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 2011-08-13 00:48 sbin
drwxrwxrwx 2 root root 4096 2011-03-05 14:38 share
drwxrwxrwx 2 root root 4096 2011-03-05 11:08 sys
drwxrwxr-x 19 root root 4096 2010-11-01 23:44 usr

for making the partitions i used fdisk (util-linux 2.19.1)
under ubuntu 11.10

fdisk /dev/sdb
then option u for working with cylinders (without u fdisk works with blocks)
then p
shows:
Gerät boot. Anfang Ende Blöcke Id System
/dev/sdb1 1 64 513056 83 Linux
/dev/sdb2 65 128 514080 83 Linux
/dev/sdb3 129 192 514080 82 Linux Swap / Solaris
/dev/sdb4 193 121601 975217792+ 5 Erweiterte
/dev/sdb5 193 292 802226 83 Linux
/dev/sdb6 293 293 7008+ 83 Linux
/dev/sdb7 294 357 513056 83 Linux
/dev/sdb8 358 121601 973891406 83 Linux

[fvdw]

the amber led blink 2 or 3 times at boot, then never.

with amber led do you mean the red one at the front side near the blue one ?
Or do you mean the orange led at the LAN connector on the back side ?

The red one at front side should not light up at all, if that light ups you may have a hardware failure.
if it is the led of the LAN connector then it doesn't mean anything.

Normally the sequence to get this device booting is that you connect the power. Then blue led comes up for a short moment and goes out again. Then you have to press and hold the button on the back for 2 seconds to let it start booting.
Only the blue led should light up and start flashing, you will also hear the disk spin up.
After the fvdw-sl firmware has been booted and you se the shutdown command in the webinetrface then the startup will be different. As soon as you connect the power it will start booting without the need to press and hold the button on the back side, but also in this case the red led should always remain off

[FoCMB]

with amber i mean the led at the network connector on the backside. there are a green one and the amber one.

the front led is only blue and blinks on start up.

"Normally the sequence to get this device booting is that you connect the power. Then blue led comes up for a short moment and goes out again"

i conncet power, then the blue led is shortly blinking and i hear the disk spin up and then the blue led is always on.
if i press the power button for 2seconds nothing happens and my router shows me no lan-device (only the laptop)

[fvdw]

with amber i mean the led at the network connector on the backside. there are a green one and the amber one.

the front led is only blue and blinks on start up.

"Normally the sequence to get this device booting is that you connect the power. Then blue led comes up for a short moment and goes out again"

i conncet power, then the blue led is shortly blinking and i hear the disk spin up and then the blue led is always on.
if i press the power button for 2seconds nothing happens and my router shows me no lan-device (only the laptop)

This looks like a disk problem.
As said and assuming you never have run our firmware or changed something in flash memory of the nwsp 2 then after connecting the power the blue led should light only short moment and go out again and the disk should not spin up.
Only after pressing and holding the button on the back for 2 seconds should light up the blue led again and makes the disk spin up.
If this is not happening on your system and it directly starts with starting the disk and try booting then you must have modified the flash memory ???

[FoCMB]

oh no, i only put the disk out of the box and changed only the things written in your howto. i never touched the flash

[Jocko]

@FoCMB
which program did you use to make the partitions ?
There is something odd in your partiton table, the number of blocks is for some partitions not correct
When you follow the how to guide and use fdisk then you should get exactly the table as mentioned in the how to guide.

Like sdb6, the number of blocks is not correct (and sda6 is the kernel...)

It may better to repeat the entire procedure and before destroying the partition table.

It is not normal that the Langerak script fails (at the step format sdb5)