Switch not booting

[almadar]

Hello,
I have a 6360 switch stuck in a boot loop. The Console output when booting is as follows:

Code: Select all

General initialization - Version: 1.0.0
Serdes initialization - Version: 1.0.2
mvHwsSerdesTopologyGet:  ac3s topology
PEX: pexIdx 0, detected no link
DDR3 Training Sequence - Ver TIP-1.55.0
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
DDR3 Training Sequence - Ended Successfully
BootROM: Image checksum verification PASSED

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_
        | | | |___|  _ \ / _ \ / _ \| __|
        | |_| |___| |_) | (_) | (_) | |_
         \___/    |____/ \___/ \___/ \__|
 ** LOADER **


U-Boot 2013.01 8.7.R02.149 |armv7_ac3| (Jan 27 2021 - 21:28:06) Marvell version: 2015_T1.0p18

Board: RD-XC3-BHX-24G-4XG
SoC:   Alleycat3S Rev A1
       running 3 CPUs
CPU:   Marvell PJ4B (584) v7 (Rev 2) LE
       CPU 0
       CPU    @ 667 [MHz]
       L2     @ 200 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 667 [MHz]
       DDR 16Bit Width, FastPath Memory Access, DLB Enabled
       DDR ECC Disabled
DRAM:  1 GiB
U-Boot at: 3fe29000
Board ID d:3
CPLD REV: 11
OS6360_P24 out of reset
NAND:  1024 MiB
MMC:   MRVL_MMC: 0
SF: Detected MX25L6405D with page size 64 KiB, total 8 MiB
PCI-e 0: Detected No Link.
FPU initialized to Run Fast Mode.
USB2.0 0: Host Mode

Map:   Code:                    0x3fe29000:0x3feebc40
       BSS:                     0x3ffefe0c
       Stack:                   0x3f918ee0
       Heap:                    0x3f919000:0x3fe29000
       U-Boot Environment:      0x00100000:0x00110000 (SPI)

Net:
|  port  | Interface | PHY address  |
|--------|-----------|--------------|
| egiga0 |   SGMII   |   In-Band    |
| egiga1 |   SGMII   |   In-Band    |

Reading Nvram:.. Done
Loading from NAND
incorrect device type in spi0=spi_flash
Creating 1 MTD partitions on "nand0":
0x000000000000-0x000040000000 : "mtd=0"
UBI: attaching mtd1 to ubi0
UBI: Force attach in read-only mode
UBI: physical eraseblock size:   262144 bytes (256 KiB)
UBI: logical eraseblock size:    253952 bytes
UBI: smallest flash I/O unit:    4096
UBI: VID header offset:          4096 (aligned 4096)
UBI: data offset:                8192
UBI: 18 bad PEB, 4078 good PEB
UBI: scan took 10700ms
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=0"
UBI: MTD device size:            1024 MiB
UBI: number of good PEBs:        4078
UBI: number of bad PEBs:         18
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             23
UBI: total number of reserved PEBs: 4055
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 4/1
UBIFS: read-only UBI device
LEB 0 mapped to PEB 1050
LEB 1 mapped to PEB 2372
LEB 2 mapped to PEB 2375
UBIFS error (pid 0): ubifs_scan: LEB 1445 scanning failed
UBIFS error (pid 0): ubifs_mount: Error reading superblock on volume 'ubi:flash' errno=-12!

Unable to mount UBI partition!
NVRAM:
        Booting from certified/Nosa.img
Checking Nvram:  No change!
Hit any key to stop autoboot:  0
UBIFS not mounted, use ubifs mount to mount volume first!
ubifsload_nosym - load file from an UBIFS filesystem, skipping symtbl entries

Usage:
ubifsload_nosym <addr> <filename> [bytes]
    - load file 'filename' to address 'addr'
Wrong Image Format for bootm command
ERROR: can't get kernel image!


To use the switch rescue procedure first make sure of the following:

  - The Narescue.img file is located in the root directory of the
    USB flash device
  - The 6360 directory contains all the system files required to
    revive the switch.
    i.e. 6360/certified/<*.img boot.cfg>
         on the USB flash device
  - USB flash device is inserted

Once the above requirements are met, issue the following command
at the prompt to start the rescue process:

=> run rescue

***** Using the rescue process WILL destroy all switch data *****
*****              USE WITH EXTREME CAUTION                 *****

Marvell>>

The switch is unresponsive to keyboard input. I Thought the com settings are incorrect so I tryed with baud speed 115200 and the only change is that the switch outputs this instead (in a loop).

Code: Select all

BootROM 1.41
Booting from SPI flash

I created a rescue USB and iserteed it before and during rebooting and nothing happens. I also tryed to different USB drives, an old 1GB and a newer 32GB and none worked. I formated both in fat32 and put the rescue image file Narescue.img, 6360/certified/Nosa.img and 6360/certified/boot.cfg on them.

Is there a step I missed or something else I need to try? Could this be hardware problem that can't be fixed?
Thanks.

[Cristek]

I was going to say to try Rescue mode but then right afterwards I read that you already tried it.
While this never happened to me, I'm wondering if you have all the files in the USB stick (vcboot.cfg, vcsetup.cfg, the image etc)

[almadar]

In the rescue disk I put the certified folder of a similar normal working switch. The thing is I don't see any sign of the switch seeing the USB sticks and the switch is unresponsive to keyboard entries so I can't use any commands to check.