Firmware upgrade of WS-26-400-IDC then power outage

[frog]

Hi,
You have a great product in regards to your Netonix switches but I was looking for some assistance with an issue that I have created.
While completing a firmware upgrade of a WS-26-400-IDC to the latest version the power went out.
We have tried your Netonix Serial Recovery tool from your forum page multiple times with a few different outcomes. However, the Recovery Tool never appears to indicate it is done. I have even left the recovery tool running for about 4 hours and still it did not indicate it was done.

I have captured a putty log of the Netonix switch when booting up. These are the things we have currently tired: -
Left power off for a few hours then reboot
Pressed and held physical reset button for 5 seconds (the Ethernet ports did not turn on green as they should nor did it reboot)
Pressed and held physical reset button for 10 seconds (the Ethernet ports did not turn on red as they should nor did it reboot)
Pressed and held physical reset button for 20 seconds, nothing happened at all.
Connected via putty and pressed Ctrl C to get to RedBoot then run Netonix Serial Recovery tool as per Forum “If 1.5.15 bricked your switch PLEASE READ” Recovery
Method 1 Removed the top cover of the switch as per Recovery
Method 2 but there is no cable plugged into the i2C so did not proceed any further
NOTE: - All Ethernet Ports have no link-state on any ports.
I really hope there is a solution that I can complete from the office to get the switch running again.
We have a backup of the configurations so I do not care if the system is totally restored to default.

Note: - We can setup a screen share if required as well.

Any feedback on this matter will be greatly appreciated.

Thanks Jason

[frog]

Hi, We have managed to get the Netonix Serial Recovery tool to reach the done state.
Once we unplugged the three Fans it allowed your tool to work.
Tried the latest firmware version - still no luck Tried firmware 1.5.14 - still no luck
It appears to fail in two different locations

admin@xxxxxxxx:/# rebootmini_fo_lookup: ERROR, meta data corruption detected.mini_fo_d_delete: negative dentry passed.mini_fo_d_release: no private data.admin@xxxxxxxx:/# Restarting system.

i2c /dev entries driveri2c_vcoreiii i2c_vcoreiii: i2c bus driver on IRQ 19mini_fo_lookup: ERROR, meta data corruption detected.

Any help with this matter will be greatly appreciated.

Thanks Jason

[Stephen]

You could try a factory reset:

1. Power off the switch
2. Use something thin and firm to press and hold the button in the reset pinhole (typically I use paperclip)
3. Power on the switch and monitor the serial console.
4. Once the reset has started, you can release the button.

If the switch does not respond to your pressing this button it means that a failure is taking place before userland loads, meaning there is an issue with hardware and the switch will have to be RMA'd to fix.

However if the switch is able to perform the factory reset and you are still seeing trouble, please capture the putty output and paste it here so we can try to further assist. But if the error's we're seeing are the same as the one's you've already reported, it still likely means there is a problem in the hardware unfortunately.

But let's see how this goes first.

[frog]

Hi Stephen,

Thanks for the quick response.
I have already tried to press and hold the reset button with the paper clip.
Pressed and held physical reset button for 5 seconds (the Ethernet ports did not turn on green as they should nor did it reboot) therefore nothing was captured when monitoring via the serial cable.
Pressed and held physical reset button for 10 seconds (the Ethernet ports did not turn on red as they should nor did it reboot) therefore nothing was captured when monitoring via the serial cable.
Pressed and held physical reset button for 20 seconds, nothing happened at all. Therefore nothing was captured when monitoring via the serial cable.

Two (2) Putty logs attached.
We completed some further research on the web and entered this command when booted to Redboot

RedBoot> fis init -f

This then cleared all the partitions.
I was now hoping you could assist with reinstalling the 13 partitions to see if the switch will then boot correctly.
Creating 13 MTD partitions on "m25p80":
0x00000000-0x00040000 : "RedBoot"
0x00040000-0x00080000 : "config"
0x00080000-0x001c0000 : "linux_recovery"
0x001c0000-0x003c0000 : "rootfs_recovery"
mtd: partition "rootfs_recovery" set to be root filesystem
0x003c0000-0x00500000 : "linux"
0x00500000-0x00b00000 : "rootfs"
0x00b00000-0x00f40000 : "rootfs_data"
0x00f40000-0x00f80000 : "FIS directory"
0x00f80000-0x00f81000 : "RedBoot config"
0x00fc0000-0x01000000 : "Redundant FIS"
0x03f40000-0x03f80000 : "FIS directory 512"
0x03f80000-0x03f81000 : "RedBoot config 512"
0x03fc0000-0x04000000 : "Redundant FIS 512"

Thanks Jason

[frog]

Hi Stephen,

We have another working WS-26-400-IDC, can we export partitions via RedBoot to another device,
Here's what we have found on the web:
To move a backed partition to a Windows computer using XMODEM in RedBoot, follow these steps:
Access RedBoot: Connect to your device using a terminal emulator like PuTTY or Tera Term and access the RedBoot prompt. Prepare for Transfer: Ensure your terminal emulator is set to use the XMODEM protocol. Transfer File: Use the load command to send the partition file via XMODEM. For example:

RedBoot> load -r -v -b 0x600000 -m xmodem
Replace 0x600000 with the memory address where you want to load the file.
Start the Transfer: Initiate the XMODEM transfer from your terminal emulator. In PuTTY or Tera Term, go to File -> Transfer -> XMODEM -> Send and select the partition file you want to transfer. Save the File on Windows: Once the transfer is complete, save the file on your Windows computer.




To transfer a partition file from a Windows computer back to your device using XMODEM in RedBoot, follow these steps:
Access RedBoot: Connect to your device using a terminal emulator like PuTTY or Tera Term and access the RedBoot prompt. Prepare for Transfer: Ensure your terminal emulator is set to use the XMODEM protocol. Initiate Transfer on Device: Use the load command to receive the file via XMODEM. For example:

RedBoot> load -r -v -b 0x600000 -m xmodem
Replace 0x600000 with the memory address where you want to load the file.
Start the Transfer: Initiate the XMODEM transfer from your terminal emulator. In PuTTY or Tera Term, go to File -> Transfer -> XMODEM -> Send and select the partition file you want to transfer from your Windows computer. Complete the Transfer: Once the transfer is complete, you can verify the data has been loaded correctly.

Any ideas regarding this would be great.

Thanks Jason