not booting after power failure

[fvdw]

seems you have written the new u-boot to flash, if uou get the u-boot prompt then that has gone ok but it could have bricked your nwsp2 if was not a classic (as Jocko indicate).
No for the standalone kernel there is no need for a partition table on the disk. You can even run it without having a disk inside.

Why the telnet client cannot connect is strange, you mentions you see the kernel upload and it mentions starting kernel.
Which standalone kernel did you load (full name of the file) ?

[kuzanagi88]

UIMAGE-395-NWSP2CL-179-standalone

I indeed flashed the new u-boot. I figured i might as well try it, since i have the classic. That doesn't seem to be the problem.

Directly over lan with static ip's doesn't change a thing btw. The kernel get uploaded and then the time out.

[fvdw]

I have seen some issues with the standalone kernel on system where the dhcp server refused to give an ip. The standalone kernel then might hang on requesting an ip from the dhcp server and does not continue to assign itself two static ones one of them being 192.168.1.252

You could try to use the attached experimental standalone kernel. This one does not try to get an ip from the dhcp server but only assigns itself ip 192.168.1.252 and 192.168.0.252

[kuzanagi88]

still no luck..

is there any way to check if the kernel is loaded correctly? i feel like i'm running out of options.

[fvdw]

you could try to load the standalone kernel with enabling netconsole output mening you will get output in the u-boot console window after starting kernel.

To this do not use the option load standalone kernel but use the options "start tft server" and then "u-boot console"
When you can talk to u-boot set the environment variables, you should have a prompt like this Marvell>>
(copy the commands exactly as shown here, do not make any change):

Code: Select all

Marvell>> setenv ipaddr ${ipaddr}

(response will be an echo of this command)

Code: Select all

Marvell>> setenv serverip ${serverip}

Code: Select all

Marvell>> setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/

Code: Select all

Marvell>> tftpboot 0x800000 UIMAGE-395-NWSP2CL-179-standalone

It should give some output that it uploads the kernel, after that

boot the kernel

Code: Select all

Marvell>> bootm

now you should get also starting kernel but hopefeully also output of the netconsole to see what happens while loading.

When the kernel has loaded completely open the telnet client (action in fvdw-sl console) and choose connect with the ip 192.168.1.252

[kuzanagi88]

Thanks for the info. I tried this, but never get it past: Starting Kernel ...
There is some hdd activity for about 30 seconds after that but no output in the uboot screen.
After 30 seconds the light starts flashing red/blue.

At this moment I am able to start a new uboot screen and this find the uboot without a reboot of my nas. So it instantly finds the nas at opening of uboot. This seems like proof that the kernel isn't starting at all.

I added a screenshot of my uboot output.

Any other suggestions? I'm willing to flash the device if that might bring a solution

edit: i also tried the 179 kernel..

[fvdw]

I just checked the 237 kernel on my 5big2 and it loads just fine and is accessible at two ip's 192.168.1.252 and 192.168.0.252

I am pretty sure the kernel is loaded and running on your nwsp2.

Are you sure clunc-open and nc are granted access through your firewall ? clunc-open and tftp server certainly otherwise you could not upload the kernel.

Last trial although should not make a difference
take the disk out and try it again, the kernel doesn't need the disk
On my device the standalone kernel runs just fine also with a disk with no partition table (and red/blue flash).

[kuzanagi88]

my firewall is turned off and i've searched for every possible piece of software but nothing that will block network access on my computer.

Without the disk, the flashing light starts a little bit earlier, but still the telnet time out.

[fvdw]

It might be possible that your pc is not setup to use telnet client and so it doesn't allow using port 23

here a howto to enable telnet in windows 7
http://social.technet.microsoft.com/wik ... lient.aspx

ps do not use the windows telnet client, please use the telnet client provided in the fvdw-sl console after you have enable telnet in windows 7 (maybe you need to reboot your windows pc)

[kuzanagi88]

great suggestion, i'm going to try this right away. At the moment i'm booted into linux and putting the original firmware back on the disk as instructed here:

http://lacie.nas-central.org/wiki/Insta ... space_2%29

Just to check if it boots, i don't want this firmware after i know what it CAN do :)

Be right be with feedback on your suggestion