Error bad magic number

Error bad magic number

Postby wredin » Sun Jun 09, 2013 6:32 pm

Hi, all.
First of all sorry for my English. I am Russian so I don't know English very well.

My old hard disk in ns2 died and I have bought the new one with 2TB.
Yeaserday, when I used fvdw-sl-5-0-3june2013 I got the error described here viewtopic.php?f=11&t=1273&start=10.
My telnet couldn't connect to ns 2.
I got the same message "bad magic number", trying to write this:
Code: Select all
setenv ipaddr ${ipaddr}
setenv serverip ${serverip}
tftpboot 0x800000 kernel-file-name-as-present in-tftp-folder
bootm 0x800000


When the new version of sl-console was released I tried to use it but when I run "Write fvdw-sl frimware image to disk" and choose UIMAGE, nothing happens, just after some time telnet runs and it can't connect to Lacie NS2.

Please help me with this problem.
wredin
 
Posts: 14
Joined: Sat Jun 08, 2013 6:51 pm

Re: Error bad magic number

Postby fvdw » Sun Jun 09, 2013 7:36 pm

kernel-file-name-as-present in-tftp-folder

:disapprove
this part in your command you must replaced by the actual file name of the kernel you want to load

Furthermore I just checked the writing to fvdw-sl firmware to disk feature on the fvdw-sl-console and it works fine
Be aware that if the telnet client con not connect that you try to use as ip 192.168.0.252 instead of 192.168.1.252 or the ip assigned by your dhcp server. Needles to say that the ip must be accessible in your LAN setup. If it uses another range then 192.168.1.x or 192.168.0.x then you need to use the ip assigned by the dhcp server

and I uploaded a new version of the console (5.1) but no change regarding writing firmware action in this new version
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Error bad magic number

Postby wredin » Sun Jun 09, 2013 8:17 pm

Thank you for your reply.
I ran this command and got this
You do not have the required permissions to view the files attached to this post.
wredin
 
Posts: 14
Joined: Sat Jun 08, 2013 6:51 pm

Re: Error bad magic number

Postby fvdw » Sun Jun 09, 2013 8:27 pm

if you use u-boot console to upload a kernel, like you try, then you must also first start the tftp server in the fvdw-sl console (choose action start tftp server)
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Error bad magic number

Postby wredin » Sun Jun 09, 2013 8:39 pm

Thank you again for your reply.

I started tftp server and now got the sign "Starting kernel..."

And this sign is still hanging and nothing happens again. I cant ping 192.168.20.20.
You do not have the required permissions to view the files attached to this post.
wredin
 
Posts: 14
Joined: Sat Jun 08, 2013 6:51 pm

Re: Error bad magic number

Postby wredin » Sun Jun 09, 2013 8:39 pm

The sign
You do not have the required permissions to view the files attached to this post.
wredin
 
Posts: 14
Joined: Sat Jun 08, 2013 6:51 pm

Re: Error bad magic number

Postby wredin » Sun Jun 09, 2013 8:44 pm

Also I switched off DHCP in my network
wredin
 
Posts: 14
Joined: Sat Jun 08, 2013 6:51 pm

Re: Error bad magic number

Postby wredin » Sun Jun 09, 2013 8:51 pm

If I flash U-boot I Get such result. After rebooting it blinks red and blue all the time
You do not have the required permissions to view the files attached to this post.
wredin
 
Posts: 14
Joined: Sat Jun 08, 2013 6:51 pm

Re: Error bad magic number

Postby wredin » Sun Jun 09, 2013 8:52 pm

What do I do wrong? Where is my mistake?
wredin
 
Posts: 14
Joined: Sat Jun 08, 2013 6:51 pm

Re: Error bad magic number

Postby fvdw » Sun Jun 09, 2013 8:52 pm

you are using ip range 192.168.20.x on your router then telnet can not reach 192.168.1.252 or 192.168.0.252
Also you switched off your DHCP server so the nws2 will not have a IP assigned by dhcp.
This means you cannot connect to the telenet server of the standalone kernel because you router will only allow access to ip's with 192.168.20.x
The standalone kernel can only be contacted with telnet by using 192.168.1.252 and 192.168.0.252 or then IP address assigned by DHCP server

You can do two things, switch on dhcp server on you router and let it assign an ip address to the nwsp2 and use that to connect with telnet after starting the standalone kernel
or change setting of you router to use 192.168.1.x or 192.168.0.x range for ip adresses
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Next

Return to Lacie Network Space vs2 and max version

Who is online

Users browsing this forum: No registered users and 3 guests