I can't find the nas after a first time install

[jeanlouispy]

Hi,

I have just made the first install of the fvdw-sl-10-1 firmware on my nwsp1.

When I start the nas the led blinking non-stop.

I can' t find the nas on my network.

I've looked for on this forum but I haven't found the answer.

This is my partition's table :

Commande (m pour l'aide): p

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 têtes, 63 secteurs/piste, 121601 cylindres, total 1953525168 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Identifiant de disque : 0x5cadbb20

Périphérique Amorce Début Fin Blocs Id Système
/dev/sda1 2048 514079 256016 83 Linux
/dev/sda2 514080 1028159 257040 83 Linux
/dev/sda3 1028160 1542239 257040 82 partition d'échange Linux / Solaris
/dev/sda4 1542240 1953520064 975988912+ 5 Étendue
/dev/sda5 1544288 2313359 384536 83 Linux
/dev/sda6 2315408 2329424 7008+ 83 Linux
/dev/sda7 2331473 2859569 264048+ 83 Linux
/dev/sda8 2861618 1953520064 975329223+ 83 Linux

I tried to look into the boot.log on sda7 but I never found this file :dontknow .

Thanks for your help.

:please

[fvdw]

your partition table is displayed in sectors instead of cylinders, it seems to be right although in extended part there are some strange numbers for starting sectors. Can you post it also in cylinders ?

if it constantly blinking it means booting is not completed. if you did not find the file boot.log in sda7 it means it halts very early in the booting process.
This can be ailure to load the kernel (did you write it to sda6 ? (I assume you did), then next logical problem is an error in mounting of sda7.
Another possibility is that you used wrong package. This evening I have little time need to go for a party. Tomorow I have more time to find the reason of your problem, hope you have some patience

[jeanlouispy]

Many Thanks, your are my last change, it was around 2 month that I try to find the issue.

I'll be there tomorrow from 4 pm.

This is my partition table in cylinders :

Périphérique Amorce Début Fin Blocs Id Système
/dev/sda1 1 32 256016 83 Linux
/dev/sda2 33 64 257040 83 Linux
/dev/sda3 65 96 257040 82 partition d'échange Linux / Solaris
/dev/sda4 97 121601 975988912+ 5 Étendue
/dev/sda5 97 144 384536 83 Linux
/dev/sda6 145 145 7008+ 83 Linux
/dev/sda7 146 178 264048+ 83 Linux
/dev/sda8 179 121601 975329223+ 83 Linux

I have saved a log of the commands, this is the copy of sda6 :

root@jlp-System-Product-Name:~# dd if=/home/jlp/lacie/uImage-26331-6-nwsp1 of=/dev/sda6
3603+1 enregistrements lus
3603+1 enregistrements écrits
1844988 octets (1,8 MB) copiés, 0,0895049 s, 20,6 MB/s

Thanks,

[fvdw]

that looks ok

do you also have the log of the commands to write image to sda1,2 and 7 and how to prepare sda5

[jeanlouispy]

Hello,

this for sda 1,2 and 7 :

root@jlp-System-Product-Name:~# dd if=/home/jlp/lacie/fvdw-sl-10-1-nwsp1-19nov2011.img of=/dev/sda1
409600+0 enregistrements lus
409600+0 enregistrements écrits
209715200 octets (210 MB) copiés, 12,4288 s, 16,9 MB/s
root@jlp-System-Product-Name:~# dd if=/home/jlp/lacie/fvdw-sl-10-1-nwsp1-19nov2011.img of=/dev/sda2
409600+0 enregistrements lus
409600+0 enregistrements écrits
209715200 octets (210 MB) copiés, 12,2136 s, 17,2 MB/s
root@jlp-System-Product-Name:~# dd if=/home/jlp/lacie/fvdw-sl-10-1-nwsp1-19nov2011.img of=/dev/sda7
409600+0 enregistrements lus
409600+0 enregistrements écrits
209715200 octets (210 MB) copiés, 2,35674 s, 89,0 MB/s

and for sda5 :

root@jlp-System-Product-Name:~# mke2fs -j -m 1 /dev/sda5
mke2fs 1.42.5 (29-Jul-2012)
Étiquette de système de fichiers=
Type de système d'exploitation : Linux
Taille de bloc=1024 (log=0)
Taille de fragment=1024 (log=0)
« Stride » = 0 blocs, « Stripe width » = 0 blocs
96256 i-noeuds, 384536 blocs
3845 blocs (1.00%) réservés pour le super utilisateur
Premier bloc de données=1
Nombre maximum de blocs du système de fichiers=67633152
47 groupes de blocs
8192 blocs par groupe, 8192 fragments par groupe
2048 i-noeuds par groupe
Superblocs de secours stockés sur les blocs :
8193, 24577, 40961, 57345, 73729, 204801, 221185

Allocation des tables de groupe : complété
Écriture des tables d'i-noeuds : complété
Création du journal (8192 blocs) : complété
Écriture des superblocs et de l'information de comptabilité du système de
fichiers : complété

root@jlp-System-Product-Name:~# mkdir /mnt-sda5
root@jlp-System-Product-Name:~# mount /dev/sda5 /mnt-sda5
root@jlp-System-Product-Name:/# cp /home/jlp/lacie/sda5-lacie-nwsp1.tar.gz /mnt-sda5/
root@jlp-System-Product-Name:/# cd mnt-sda5
root@jlp-System-Product-Name:/mnt-sda5# dir
lost+found sda5-lacie-nwsp1.tar.gz
root@jlp-System-Product-Name:/mnt-sda5# tar -xzvf sda5-lacie-nwsp1.tar.gz
etc/
etc/nas_conf_db.xml
etc/nas_ext_hdd_db.xml
etc/ntp.conf
lost+found/
tmp/
usr/
usr/private/
usr/private/secrets.tdb
var/
var/etc/
root@jlp-System-Product-Name:/mnt-sda5# ls
etc lost+found sda5-lacie-nwsp1.tar.gz tmp usr var

[fvdw]

:scratch looks ok

why is writing of sda7 so fast (only 2.6 sec-> 89 MB/s ?

[fvdw]

we need to check if sda7 is ok

to do this you could create a mountpoint like you did for sda5 (on the PC running linux)
when sda7 is mounted check what files system is on the partition

[jeanlouispy]

ok this the files on sda7 :

root@jlp-System-Product-Name:/mnt-sda7# ls
bin dev lib lost+found opt root share usr
boot etc linuxrc nowhere proc sbin sys

[fvdw]

so it is mountable and contains so to see the indeed a root file system

Can check if you can read the main boot script rcS

Code: Select all

cat /mount-point/etc/init.d/rcS

[jeanlouispy]

it's work :

root@jlp-System-Product-Name:/# cat /mnt-sda7/etc/init.d/rcS
#!/bin/sh

# mofified by fvdw for use with linux 2.6.33.1
# busybox 1.15 and ntfs-3g and fuse kernel module
# 8-jul-2011 few bug fixes , remove spaces in cammand line
# 16 jul modified to make booting posible using sda1 or sda2 on lacie nwsp
echo "start rcS"
echo "set global environment params"
...