FIRMWARE RECOVERY VIA CONSOLE PORT

[ptera]

Trying a power down/power up now.

Power was shut off to the device out in the field and when power was restored it did not load.

[ptera]

Nope - same error message.

[Stephen]

It really does look like there is an issue with the flash chip. All the messages we are getting from either method stops when it's accessing it for writing. At this point I would suggest you RMA the unit.

This is just a guess but I'm wondering if maybe a surge occurred during the original power cycle.

[ptera]

Ok well we will do that.

I am guessing the same thing now also.

Thanks

[Stephen]

You're welcome

[csanger]

Hello --- attempting to recover a WS-12-250DC that field techs reported "may" have gotten the power cut to it during F/W update.

Started to attempt recovery via console, got this initial result:

Code: Select all

i2c /dev entries driver
i2c_vcoreiii i2c_vcoreiii: i2c bus driver on IRQ 19
mini_fo_lookup: ERROR, meta data corruption detected.
mini_fo_d_delete: negative dentry passed.
mini_fo_d_release: no private data.
mini_fo_lookup: ERROR, meta data corruption detected.
mini_fo_d_delete: negative dentry passed.
mini_fo_d_release: no private data.
mini_fo_lookup: ERROR, meta data corruption detected.
mini_fo_d_delete: negative dentry passed.
mini_fo_d_release: no private data.
mini_fo_lookup: ERROR, meta data corruption detected.
mini_fo_d_delete: negative dentry passed.
mini_fo_d_release: no private data.
 
BusyBox v1.11.2 (2014-09-17 17:18:08 EDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.
admin@Netonix_Switch:/# fis load -d linux_recovery go
/bin/ash: fis: not found
admin@Netonix_Switch:/#


Read through the forum thread on this topic and saw the following post that seemed to be related to a user reporting a similar symptom:

Leave the console port plugged in, and remove power and reapply. Press control+C when prompted to break boot sequence, and then follow the instructions above, you should be fine.

Gave that a try, but ^C doesn't seem to have any effect on breaking the boot sequence (when prompted) and the boot process continues. After a couple of reboots and attempts, boot process now appears to hang here:

Code: Select all

vtss_ethdrv: Unknown symbol vtss_fdma_init
vtss_ethdrv: Unknown symbol vtss_packet_rx_conf_get
i2c /dev entries driver
i2c_vcoreiii i2c_vcoreiii: i2c bus driver on IRQ 19
mini_fo_lookup: ERROR, meta data corruption detected.
mini_fo_d_delete: negative dentry passed.
mini_fo_d_release: no private data.
mini_fo_lookup: ERROR, meta data corruption detected.
mini_fo_d_delete: negative dentry passed.
mini_fo_d_release: no private data.
mini_fo_lookup: ERROR, meta data corruption detected.
mini_fo_d_delete: negative dentry passed.
mini_fo_d_release: no private data.
mini_fo_lookup: ERROR, meta data corruption detected.
mini_fo_d_delete: negative dentry passed.
mini_fo_d_release: no private data.


And no longer ends on the 'admin@Netonix_Switch:/#' prompt.

In fact, the terminal is now hanging and non-responsive at 'mini_fo_d_release: no private data.'

Tried it both in Hyperterminal and PuTTY for the sake of doing so --- same result.

Thoughts? Time to RMA or am I missing something?

Thanks!

[Stephen]

Hello csanger,

So if you can get it back to this prompt:

Code: Select all

admin@Netonix_Switch:/#


Then it means that it has made it past the bootloader and you can try following these instructions to recover:

OK, everything looks right (except that it's not working of course).

Try this:

1) cd /tmp
2) rx wispswitch-1.5.0.bin
3) touch upgrade_in_progress
4) firmware_upgrade wispswitch-1.5.0.bin

Let me know what this does. Depending on what the original issue was, this has worked for me under various circumstance's.

However, if corruption has gotten worse and you are completely blocked from any interaction in the prompt then it has to be re-flashed which require's an RMA.

[csanger]

Thanks for the reply, Stephen. I'll give it a whirl. Failing that, we'll RMA it.

Much appreciated!

[Stephen]

No problem,

Good luck!

[dragonwifi]

hiya Guys.

Got a switch here. It stopped passing VLANs yesterday, so I rebooted it and it never came back on. 2 Green Solid Lights inside and the fan running at max. Any advice?