plugout.net

I was pretty impressed by this forum so I tried to manually flash my nwsp2 uboot. I just went to the loading bar on the clunc console and my electricity went out. Now, my device is not detected by the computer as I try to re-flash it but all the LEDs and LAN port lights seem to work correctly. Did I brick my device ??

It depends, if power cut happened while the flash was erased or while the new uboot image was written to flash, then yes your device is bricked as flash is empty or the image in flash is incomplete, not fully written, and as such corrupt.

But what exactly do you mean with loading bar?
When flashing uboot first flash is erased and then the new version is written to flash. This erasing and writing is mentioned in the uboot windows. Where exactly did you get the power cut?

fvdw wrote:It depends, if power cut happened while the flash was erased or while the new uboot image was written to flash, then yes your device is bricked as flash is empty or the image in flash is incomplete, not fully written, and as such corrupt.

But what exactly do you mean with loading bar?
When flashing uboot first flash is erased and then the new version is written to flash. This erasing and writing is mentioned in the uboot windows. Where exactly did you get the power cut?

It stopped before the blue line on the picture attached. I got the picture from the fvdw console manual.

Hi

fvdw is not yet here (it is the expert about the bootloader) but if you got a power-off at this step fvdw-sl console did not yet overwrite (and delete) the original bootloader (so it would be nice)

Can you perform this to valid the current bootlaoder on the nas:
- close all windows and stop the nas.
- From fvdw-sl console, try to use the action "U-boot console"
- start the nas when you get the message "waiting for u-boot" (please to report if you got it or not)
- on prompt "MARVEL>>", run

Code: Select all

version
printenv

(please to post these output)

This will help fvdw

What Jocko describe is correct. If power was cut at the moment you mentioned then the original uboot in flash is untouched. And indeed follow the suggestion from Jocko to try to connect using the uboot console as present in fvdw-sl console

I followed the steps as described by Jocko but the clunc is stuck on waiting for u-boot. I tried changing the HDD to the older one and then an empty one but still stuck there. Now every time I boot up, the front led first flashes blue and then flashes red and blue twice after becoming blue so I think that has something to do with firmware I guess. I am using direct LAN cable or patch-cord to connect my device to my computer.

What happens if you do a trial without a disk installed?
Especially the behavior of the leds is of interest.
Is your current set up equal to the one when you had the power failure?
Last question are you able to set up a connection using the serial port of the nwsp2? To make that work you will an usb-serial TTL cable to connect your nwsp2 serial port to a serial com port of your PC