Help with recovering a 6465T-12

[AUautodc]

I was configuring a 6465T-12 out of the box and then I did a write memory flash-synchro after. I let the switch fully reboot before I disconnected the power cable. I did not pay attention to the detail of what was on my CLI before I disconnected the power cable. When I arrived at the site, the switch is not booting normally anymore. Does someone know how to do a recovery? I have another 6465T-12 if it helps. I do not know how to copy nos.img from the working switch. Thank you

U-Boot 2013.01 8.7.R02.2 |armv7_ac3| (Oct 08 2020 - 21:32:05) Marvell version: 2 015_T1.0p18

Board: ALLEYCAT3-Customer-Board-0
SoC: Alleycat3 Rev A1
running 2 CPUs
CPU: Marvell PJ4B (584) v7 (Rev 2) LE
CPU 0
CPU @ 800 [MHz]
L2 @ 200 [MHz]
TClock @ 200 [MHz]
DDR @ 800 [MHz]
DDR 16Bit Width, FastPath Memory Access, DLB Enabled
DDR ECC Disabled
DRAM: 1 GiB
U-Boot at: 3fe29000
Board ID 8:4
CPLD REV: 04
OS6465T_12 out of reset
NAND: 1024 MiB
MMC: MRVL_MMC: 0
SF: Detected MX25L6405D with page size 64 KiB, total 8 MiB
Using default environment

PCI-e 0: Detected No Link.
FPU initialized to Run Fast Mode.
USB2.0 0: Host Mode

Map: Code: 0x3fe29000:0x3feebb30
BSS: 0x3ffefa0c
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: 15 bad PEB, 4081 good PEB
UBI: scan took 10129ms
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=0"
UBI: MTD device size: 1024 MiB
UBI: number of good PEBs: 4081
UBI: number of bad PEBs: 15
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: 26
UBI: total number of reserved PEBs: 4055
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 2/0
UBIFS: read-only UBI device
LEB 0 mapped to PEB 1062
LEB 1 mapped to PEB 1020
LEB 2 mapped to PEB 1021
UBIFS error (pid 0): ubifs_scan: LEB 1001 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/Nos.img
Checking Nvram: No change!
ethernet addresses do not match
00:50:43:06:06:06 -> 94:24:E1:D6:52:E4
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 Nrescue.img file is located in the root directory of the
USB flash device
- The 6465 directory contains all the system files required to
revive the switch.
i.e. 6465/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 *****

[silvio]

Like written you need to rescue the switch.

- The Nrescue.img file is located in the root directory of the USB flash device (=> Nrescue you can download in myportal)
- The 6465 directory contains all the system files required to revive the switch. (=> at least you need "6465/certified/Nos.img" 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

[AUautodc]

Thank you Silvio! I was able to recover my 6465T

I downloaded the nrescue.img from your post of 2 years ago
https://www.alcatelunleashed.com/viewtopic.php?t=31171

I formatted a 4GB flash drive into FAT (not sure if FAT32 will not have worked)
I created the following folders/files in the flash drive:
/nrescue.img
/6465/certified/
/6465/working/

I boot another working 6465, logged in as admin, typed USB enable, inserted the flash drive,
typed cd working (or maybe cd /flash/working) and copied all the files (cp -R *.* /uflash/6465/working)
also copied certified folder from the working switch into the flash drive's certified folder

back to the broken switch. It already starts on miniboot. Insert flash drive, typed "run rescue" and followed the prompts. Process took around 10 minutes but my anxiety took 100.

All good now. I can configure again.