12-19-2024 06:32 AM
Hello Everyone.
I have a corrupt image / boot loop problem on my Access Point - Model 9120 AXI
Error - verify signature failed for /bootpart/part2/ramfs_data_cisco.cpio.lzma
I recreated the part 2 using below command :
(u-boot)> ubi part fs
(u-boot)> ubi remove part2
(u-boot)> ubi create part2
(u-boot)> boot
however upon hitting boot I face below problem which I think where the problem. I have omitted normal logs output from below. Could someone explain how to solve it?
u-boot> ubi part fs
ubi0: attaching mtd3
ubi0: scanning is finished
ubi0: attached mtd3 (name "mtd=2", size 1017 MiB)
ubi0: PEB size: 262144 bytes (256 KiB), LEB size: 253952 bytes
ubi0: min./max. I/O unit sizes: 4096/4096, sub-page size 4096
ubi0: VID header offset: 4096 (aligned 4096), data offset: 8192
ubi0: good PEBs: 4069, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 37/20, WL threshold: 4096, image sequence number: 839138221
ubi0: available PEBs: 33, total reserved PEBs: 4036, PEBs reserved for bad PEB handling: 80
u-boot> ubi remove part2
Remove UBI volume part2 (id 1)
u-boot> ubi create part2
No size specified -> Using max size (592470016)
Creating dynamic volume part2 of size 592470016
u-boot> boot
Mounting UBI device fs
ubi0: detaching mtd3
ubi0: mtd3 is detached
ubi0: attaching mtd3
ubi0: scanning is finished
ubi0: attached mtd3 (name "mtd=2", size 1017 MiB)
ubi0: PEB size: 262144 bytes (256 KiB), LEB size: 253952 bytes
ubi0: min./max. I/O unit sizes: 4096/4096, sub-page size 4096
ubi0: VID header offset: 4096 (aligned 4096), data offset: 8192
ubi0: good PEBs: 4069, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 37/21, WL threshold: 4096, image sequence number: 839138221
ubi0: available PEBs: 0, total reserved PEBs: 4069, PEBs reserved for bad PEB handling: 80
Load Addr 0x10000000
Mount UBIFS PARTITION part2 ...
Error reading superblock on volume 'ubi0:part2' errno=-30!
ubifsmount - mount UBIFS volume
Now coming to the mail logs where It again goes into u-boot without pressing esc button automatically and got stuck with below logs :
Hit ESC key to stop autoboot: 3 2 1 MG link 1G
0
Mounting UBI device fs
ubi0: attaching mtd3
ubi0: scanning is finished
UBI init error 22
Error: Unable to ubi mount mtd device fs
u-boot>
12-19-2024 06:38 AM
Have you tried recovery procedure given in the following document?
Jagan Chowdam
/**Pls rate useful responses**/
12-19-2024 02:18 PM - edited 12-19-2024 02:30 PM
It is easier and a lot faster to RMA the AP.
12-25-2024 04:56 AM
Re-flashing the AP using the u-boot procedure Jagan shared takes a few minutes and definitely going to be a whole lot quicker than RMA Leo ... I've used it a few times.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide