New WS-26-400-IDC Bricked?

[troy]

Have a WS-26-400-IDC that's been acting up, so figured today is the day to replace it.

Updated the firmware without a problem, then when I attempted to restore the backup from the old switch, it became completely unresponsive.

Serial console got me to an OpenWRT prompt. Was able to run the recovery tool. Tried firmware 1.5.6 and 1.5.0. Both results in Segmentation faults.

What's next?

[Stephen]

Well, to recover it from where it is, you need to perform a hard config reset.
To do that, there should be a small hole right next to the serial port that you can stick a pin in. Press that for a few seconds when it's powered and it should reset the config.

If that doesn't work, try using the recovery tool (click to go to the post and download the software and needed files)

Once the process completes, the switch should be operational again.

Finally, when upgrading going from 1.5.0 to 1.5.6. So many changes have occurred that the config file is likely no longer compatible.
This is why we typically recommend you upgrade and then backup the config. Or, keep up to date on each software version so changes between config restores are minimal.

That being said, what might work is this:
once the switch is restored,
you can downgrade it back to the original version of firmware,
then apply the config,
upgrade to the latest.

If that doesn't work, then you will need to restore the switch again and upgrade it back to the latest and simply manually re-enter the configurations.

However, by far the the safest way would be to recover the switch with one method above, make sure you're on the latest firmware, and then simply manually enter configurations.

Hope that helps.

[troy]

Stephen,

Thanks for the reply.

The firmware upgrade I did was from 1.5.5 to 1.5.6. The switch was fine and responsive after that upgrade. I think it had previously been upgraded from 1.5.3 to 1.5.5.

If you re-read my post, you'll see that I did use the recovery tool. Twice. The first time with 1.5.6, the second time with 1.5.0.

The configuration restore I attempted was from an identical switch running the same firmware version (1.5.6).

Pressing the reset button doesn't do anything. I've used it on other switches in the past without issue (other than the hole being too small for a paperclip or even a micro screwdriver). I can feel the button depressing, but there is no light dance. Period.

Is there a way to check or clear the config from the OpenWRT prompt? Before the attempted configuration restoration, it should have been 100% default except for the management IP being set to 192.168.1.30.

Again, this is a brand new switch that has not been used for anything other than being put on the bench and having it's firmware upgraded.

[Stephen]

Hi troy,

Sorry it looks like I did mis-read part of your post.

Well, that's a pretty tough spot.

In the console, see if you can run these commands and PM me the results:

Code: Select all

cmd
strings /dev/mtd1


However, if this fails, then something must have gone wrong with the flash or some other components on the switch and it will have to be RMA'd.

[troy]

Stephen,

Doesn't appear to be anything special in /dev/mtd1, so here it is (along with the last of the boot messages, etc...

Code: Select all

 switch: 'Luton26' board detected
nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
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.
^C
Please press Enter to activate this console.


BusyBox v1.19.4 (2018-06-07 14:48:31 EDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
^C
@OpenWrt:/# strings /dev/mtd1
MAC=EC:13:B2:11:D8:20
MODEL=WS-26-400-IDC
BOARDREV=B
SERIAL=0
DC_MULTIPLIER=1.000

 

[Stephen]

Ah OK, so that start up output at the beginning:

Code: Select all

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.


Along with the other symptom's you've described, is a strong indicator something is wrong with the flash.
At this point I would say you need to RMA the switch. Please go to rma.netonix.com to create a ticket.