WS3 Serial Recovery

[turbojack]

I see posts and a tool to recover a WS via serial. Is this possible with WS3? I tried the manual process for WS for grins but I obviously ran into issues since I am asking here.

Thanks

Brad

[Stephen]

While the Recovery Tool is only compatible with the WS series. Unlike the WS, the WS3 also has a backup partition of previous firmware that can be activated. It doesn't always guarantee recovery depending on what went wrong but it may help.

Can you provide some more details about what you see during bootup (aka boot logs from the console) and general condition when starting the system? Also, any idea what may have caused your WS3 to go into a non-working state?

[turbojack]

So here is what I get on Serial at boot. The switch does seem to finally recover itself and boot. Once booted, the switch seems to work fine, however, it will not remember any settings. You can configure the switch and on next boot it does this same thing and seems to factory reset itself. I believe the issue was caused from improper grounding during a storm. When I went to the site I found my installers grounded everything in the cabinet, but the electrician actually never attached the ground to the ground rod, although it was lying right beside it and looked attached from the correct angle. Anyway, the switch went through a storm. It's probably bad, but I thought if I could get the filesystem corrected or do a reinstall it would / could still be a good switch.


Serial log on boot:
+M25PXX : Init device with JEDEC ID 0x20BA20.
Jaguar2 CU48 board detected (VSC7468 Rev. D).
RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version 1_4-7bc5012 - built 15:57:31, Dec 14 2017
Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009
Free Software Foundation, Inc.
RedBoot is free software, covered by the eCos license, derived from the
GNU General Public License. You are welcome to change it and/or distribute
copies of it under certain conditions. Under the license terms, RedBoot's
source code and full license terms must have been made available to you.
Redboot comes with ABSOLUTELY NO WARRANTY.
Platform: VCore-III (MIPS32 24KEc) JAGUAR2_C
RAM: 0x80000000-0x90000000 [0x80036580-0x8ffd0ffc available]
FLASH: 0x40000000-0x43ffffff, 1024 x 0x10000 blocks
== Executing boot script in 3.000 seconds - enter ^C to abort
RedBoot> diag -p
RedBoot> fis load -x linux
MD5 signature validated
Stage1: 0x80100000, length 6807345 bytes
Initrd: 0x80800000, length 188416 bytes
Kernel command line: init=/usr/bin/stage2-loader loglevel=4 image=mfi
RedBoot> exec
Now booting linux kernel:
Base address 0x80080000 Entry 0x80100000
Cmdline : init=/usr/bin/stage2-loader loglevel=4 image=mfi
Active fis: linux
00:00:00 Stage 1 booted. Starting stage2 boot @ 821 ms
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!! ERROR at line: 930, errno: 2 error: No such file or directory
!!!! MSG: Mount of ubi0:switch failed
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Note: The preceding error message suggests that the UBIFS /dev/mtd4 partition
in the Flash has not been formatted. If you have just flashed a new binary
firmware image file you need to perform the bootstrap procedure with a suitable
MFI image to resolve this.
00:00:01 Loading stage2 from NOR flash partition 'linux'
00:00:10 Overall: 9432 ms, ubifs = 813 ms, squash mount: 16 ms, rootfs 16687009 bytes read in 8057 ms (2022 KiB/s)
00:00:19 Starting application...
Using existing mount point for /switch/
W conf 03:16:50 45/conf_sec_read#874: Warning: illegal cookie[0] 0x00000000
W conf 03:16:50 45/conf_sec_read#874: Warning: illegal cookie[1] 0x00000000
board type 1, target 29800, ports 14
[ 26.148000] i2c_designware 70100400.i2c: controller timed out
Wed Jan 1 00:00:00 UTC 2020
W icfg 00:00:00 51/vtss_icfg_running_config_save#2668: Warning: Exceed the maximum stored space for saving the configured file.
Generating RSA private key, 1024 bit long modulus (2 primes)
...+++++
.......................................................................+++++
e is 65537 (0x010001)
Generating 1024 bit rsa key, this may take a while...