All Shares Gone - Lacie 5Big Network 2

[fvdw]

and did you actually see that the standalone kernel was uploaded, in the command window it should be visible , it will show tftp command and progress of the upload and before it closes automatically it will mentions "starting kernel"

[Jocko]

In addition with fvdw's post : you must use only the lan1 network port.

[cwherbert]

I started over again and after selecting the kirkwood folder for the kernel I'm not getting beyond the "waiting for u-boot" msg

I must be doing something wrong …. did I select the correct folder/kernel??? :oops:

[cwherbert]

oh, sorry, and yes, I am using the lan1 port on the NAS now, but nothing changed :sob

[fvdw]

Because the console doesn't detect your nas while booting something must be wrong in your network setup

Do you use a router

which ip pool does it allow to use ?

do not use wireless connection on the pc running the fvdw-sl console

be sure your firewall is not blocking nc and tftp32 server

Only switch on the 5big2 after you have the message waiting for u-boot

ps. what is the ip address you PC running the fvdw-sl console and the default ip addres used for the nas (you can see it in the fvdw-sl console) This is noyt the cuase of the problem because that is only relvant when you get to the stage the telnet client must connect

[cwherbert]

i got a message of bad magic number …… before getting to a TELNET timeout error ??? what does that mean?

[cwherbert]

hi guys,

i couldn't recreate the bad magic number message, but I seem to load the kernel, however I still get a TELENT timeout error ….? :sob :sob :sob

help please :please :please :please :please

[fvdw]

@cwherbert, please described exactly what you see happening in the command window after it mentions "waiting for u-boot" and when you then starts your nas.

Your remark "I think kernel has loaded" is not sufficient to offer any help.
You should see the uploading in that window, many xxxxx and finally the remark "starting kernel". Did yo see that?

[cwherbert]

Hi fvdw,

I finally got it to work!!! :applause :applause :hail :hail :hail

Howlong should this take? The mount has been running for over a day now. This NAS had about 3-4TB of data, could that be the reason?

This was what I did:

root@fvdw-sta-kirkwood:/ # tftp -l /sbin/mdadm -r mdadm -g xxx.xxx.xxx.xx
mdadm 100% |****************************************************************| 1100k 0:00:00 ETA
root@fvdw-sta-kirkwood:/ # chmod 755 /sbin/mdadm
root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md4 /dev/sd[abcde]2
mdadm: /dev/md4 has been started with 5 drives.
root@fvdw-sta-kirkwood:/ # mkdir /mountpoint
root@fvdw-sta-kirkwood:/ # mount -o ro /dev/md4 /mountpoint

[fvdw]

:-D nice that you did get it working, what did you change to make it work ?

about mount.
A mount command should finish in a second or so. Its independent for device size

Why do you think the mount command is still running ?
Didn't you get a new command prompt ?

ps you can use a second telnet window to connect to the nas as well to see what is going on.