topic Cisco AP 9105 stuck in boot loop in Wireless

Cisco AP 9105 stuck in boot loop

anuj02 — Mon, 12 Aug 2024 18:01:17 GMT

Console Logs for 1st AP-

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: 2109/374, WL threshold: 4096, image sequence number: 1761887563
ubi0: available PEBs: 0, total reserved PEBs: 4069, PEBs reserved for bad PEB handling: 80
Load Addr 0x10000000
Mount UBIFS PARTITION part1 ...
Error reading superblock on volume 'ubi0:part1' errno=-30!
ubifsmount - mount UBIFS volume

Usage:
ubifsmount <volume-name>
- mount 'volume-name' volume
Unable to mount UBIFS PARTITION part1, read UBI PARTITION ...
Read 0 bytes from volume part1 to 10000000
No size specified -> Using max size (427401216)
undefined instruction
pc : [<0000164c>] lr : [<ffffffff>]
reloc pc : [<0000164d>] lr : [<00000000>]
sp : 1fef6268 ip : 00000020 fp : 1ff06000
r10: 00000000 r9 : 1fef7ed0 r8 : ffffffff
r7 : 00000000 r6 : 00000000 r5 : 00000000 r4 : 00000000
r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : 00000000
Flags: nZcv IRQs off FIQs off Mode SVC_32
Resetting CPU ...

Console Logs for 2nd AP-

Mounting UBI device 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: 2109/374, WL threshold: 4096, image sequence number: 1761887563
ubi0: available PEBs: 33, total reserved PEBs: 4036, PEBs reserved for bad PEB handling: 80
Load Addr 0x10000000
Mount UBIFS PARTITION part1 ...
Error reading superblock on volume 'ubi0:part1' errno=-117!
ubifsmount - mount UBIFS volume

Usage:
ubifsmount <volume-name>
- mount 'volume-name' volume
Unable to mount UBIFS PARTITION part1, read UBI PARTITION ...
Read 0 bytes from volume part1 to 10000000
No size specified -> Using max size (419020800)
prefetch abort
pc : [<ebc35d70>] lr : [<00000000>]
sp : 1fef6358 ip : 00000020 fp : 1ff06000
r10: 00000000 r9 : 1fef7ed0 r8 : 51e6d68b
r7 : fb7c4a57 r6 : 3508663d r5 : e7bf26c7 r4 : b17fd61e
r3 : 00000000 r2 : 00000000 r1 : 20137c00 r0 : 4a96472b
Flags: nZcv IRQs off FIQs off Mode SVC_32
Resetting CPU ...

Re: Cisco AP 9105 stuck in boot loop

Mark Elsen — Mon, 12 Aug 2024 18:13:29 GMT

- Review hints from this thread ;
https://community.cisco.com/t5/wireless/c9117axi-e-btldr-ubi-volumes-both-removed-how-to-restore-the-ap/td-p/5000295
Personally I would be tended to create partitions again because it point to file systems corriuption
, as it is mentioned somewhere

Strange that it happens on 2APs , because it could be a hardware problem , then it it is RMA...

Re: Cisco AP 9105 stuck in boot loop

anuj02 — Mon, 12 Aug 2024 18:16:21 GMT

I did try that, but it didn't help. APs are still stuck in the same loop.

Re: Cisco AP 9105 stuck in boot loop

Mark Elsen — Mon, 12 Aug 2024 18:28:48 GMT

- As stated , it can not be guaranteed that such problems can be recovered ; if desired ask advice to Cisco's TAC ,

Re: Cisco AP 9105 stuck in boot loop

Leo Laohoo — Mon, 12 Aug 2024 23:06:25 GMT

RMA the APs.

Re: Cisco AP 9105 stuck in boot loop

Rich R — Tue, 27 Aug 2024 00:27:44 GMT

If you haven't already RMA the APs then see https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9120axi-access-point/217537-repairing-c9120-c9115-access-points-from.html for re-flashing the APs.

What version of software were the APs running?
Did this happen after you tried to upgrade the software (and to what version)?

Also see:
Field Notice: FN74109 - Access Point Image Corruption During CAPWAP Upgrade May Result in Boot Failure
Recover from a Boot Loop Caused by Image Corruption on Wave 2 and 11ax Access Points (CSCvx32806)
Safely Upgrade Access Points, Avoiding Image Corruption That Causes Boot Loop