Error bad magic number

[fvdw]

why did you flash u-boot, is your nwsp2 a "classic" ?

If not and you have a Lite version, then you have bricked it.... (if so why did you ignore the help text and warnings)

[fvdw]

if it is a classic then the flashing didn't brick it, it then means it does not recognize the hdd you have put in, which is logical if this is an empty disk

[wredin]

I changed network and got the same result with these commands

[wredin]

why did you flash u-boot, is your nwsp2 a "classic" ?

Yes, my nwsp2 is classic

[fvdw]

ok now start the telnet client in the fvdw-sl console and use as IP to connect 192.168.1.252
(In telnet client choose dropdown connect->remote system and fill in this ip in field host and click ok

[wredin]

telnet can't connect.
And starting kernel is hanging all the time.

[wredin]

I rebooted it and now it blinks twice with red and blue and then the blue light is on.

[wredin]

Now I have three ip addresses at my network adapter: 192.168.0.240, 192.168.1.240 and 192.168.20.74. But I still connect to ns2 via telnet.

[fvdw]

when the standalone kernel is loaded then you mkust wait 12-15 seconds to try to access it.

The kernel is not hanging only u-boot is no longer in control and therefor u-boot windows is not responsive anymore.

if you reboot then the standalone kernel is not there anymore. Its loaded in RAM and gone at reboot. Then you need to repeat it.
But what do you want to do when having loaded the standalone kernel ?

[wredin]

I want to install fvdw -sl frimware and prepare this disk for work. But I cant because I cant connect to my device by telnet. And I just tried the different variants to connect to device to see if it works.