topic Re: Boot Error wit AP 1815t in Wireless

Boot Error wit AP 1815t

MarkusGrasl82364 — Mon, 23 Aug 2021 07:34:48 GMT

Hello,

we recently bought a few Cisco AP 1815t so most of them wont start and cannot be config with the LAN Port 3 so we decieded to buy the Console Adatper und have a look at it. So here is our Problem.

Board type: AP1815T
smem ram ptable found: ver: 1 len: 3

U-Boot 2012.07 (btldr release 36) (Oct 13 2017 - 10:35:07)

This product contains some software licensed under the
"GNU General Public License, version 2" provided with
ABSOLUTELY NO WARRANTY under the terms of
"GNU General Public License, version 2", available here:
http://www.gnu.org/licenses/old-licenses/gpl-2.0.html

DRAM: 510 MiB
Nand: Detected ONFI Micron AND 128MiB 3,3V 8-bit
NAND ECC=4 ECC_THRESHOLD(NAND ECC-1)=3
SF: Detected MX25L3205D with page size 4 KiB, total 4 MiB
MFG data loaded
Scanning shenv data blocks
Total valid parts=4
Active shenv part[0:0], write_counter=13
machid: 8010001
Net: MAC0 addr:2c:4f:52:1a:8f:d8
PHY ID1: 0x4d
PHY ID2: 0xd0b1
ipq40xx_ess_sw_init done
Auto boot mode, use bootipq directly
Hit ESC key to stop autoboot: 0
Specified BOOT: part1
UBI error: init_volumes: not enough PEBs, required 1590, available 1024
UBI error: ubi_eba_init_scan: no enough physical eraseblocks (-566, need 1)

I looked into it but i can not find a solution. I hope someone here can help me.

Best regards

Markus Grasl

Re: Boot Error wit AP 1815t

Mark Elsen — Mon, 23 Aug 2021 09:40:36 GMT

- Could be related to them running a bad software version but since they are new I would engage on that with TAC and or ask Cisco for an explanation.

Re: Boot Error wit AP 1815t

MarkusGrasl82364 — Mon, 23 Aug 2021 11:43:02 GMT

As far as i know my Chef has buyed them used so there is a possibility that they are running a bad Version. But i cant really figure out how i can upload a new or better version to them. With the Command "dhcp" in "btldr" i have no clue what the AP tries to attemp. And "tftpboot" downloads the image only to the address-offset 8800000. But i dont know how to go further from there.

So at the moment i dont know what to do, rather then send them back to the seller.

Re: Boot Error wit AP 1815t

patoberli — Mon, 23 Aug 2021 13:11:35 GMT

If there is still a working image on the AP, this here should help:

https://lihaifeng.net/?p=222

You can try to boot the part2 instead of part1. If there is also no image, then I don't have a ready solution for you.

Re: Boot Error wit AP 1815t

MarkusGrasl82364 — Tue, 24 Aug 2021 07:57:12 GMT

Finally i made it Start an Image but now im left with these Messages:

Starting image ...

[01/01/1970 00:00:59.1199] Linux version 3.14.43 (aut@wnbu-tools-lnx3) (gcc version 4.7.1 (OpenWrt GCC 4.7.1 r48430) ) #1 SMP PREEMPT Thu Mar 4 09:41:04 GMT 2021
[01/01/1970 00:00:59.2799] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
[01/01/1970 00:00:59.3699] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[01/01/1970 00:00:59.4799] Machine model: Cisco 11ac Wave2 Wifi Access Point
[01/01/1970 00:00:59.5599] Memory policy: Data cache writealloc
[01/01/1970 00:00:59.6299] Kernel command line: console=ttyMSM0,9600n8 ubi.mtd=0 root=/dev/ram activepart=tftp activeboot=0 wdgtriggered=0 board_sku=2 clk_ignore_unused
[01/01/1970 00:00:59.7999] CPU1: Booted secondary processor
[01/01/1970 00:00:59.8699] CPU2: Booted secondary processor
[01/01/1970 00:00:59.9299] CPU3: Booted secondary processor
[01/01/1970 00:00:59.9899] buginf tty flushing thread started, ttyport=9b0b0000
[01/01/1970 00:01:02.6499] UBI error: init_volumes: not enough PEBs, required 1590, available 1024
[01/01/1970 00:01:02.7399] UBI error: ubi_wl_init: no enough physical eraseblocks (-566, need 1)
[01/01/1970 00:01:02.8499] UBI error: ubi_attach_mtd_dev: failed to attach mtd0, error -12
[01/01/1970 00:01:02.9399] UBI error: ubi_init: cannot attach mtd0
[*01/01/1970 00:01:03.0215] buginf() enabled.
[*01/01/1970 00:01:03.0467] Made it into bootsh: Mar 4 2021 10:01:45 T-0b7bc0faa97ae8a26ea605c7622aac357397184c-g0b7bc0fa-aut
[01/01/1970 00:01:04.0499] UBIFS error (pid 1): ubifs_mount: cannot open "/dev/ubivol/storage", error -22
[*01/01/1970 00:01:04.1541] mount_ubifs: mounting ubifs storage: Invalid argument
[*01/01/1970 00:01:04.1618] /bin/sh: /usr/sbin/load_policy: No space left on device

Factory full reset detected...
Full Factory Reset triggered: clear all files from storage..
[*01/01/1970 00:01:04.6527] /init: ioctl(SIOCGIFHWADDR): wired0: No such device
[*01/01/1970 00:01:04.6617] /init: ioctl(SIOCGIFHWADDR): wired0: No such device
[*01/01/1970 00:01:04.7662] /usr/sbin/create_platform_files: writing to fd 4 failed!: No space left on device
[*01/01/1970 00:01:04.7665] /usr/sbin/create_platform_files: writing to fd 4 failed!: No space left on device
[*01/01/1970 00:01:04.7668] /usr/sbin/create_platform_files: writing to fd 4 failed!: No space left on device
error: open /dev/board-config
error: open /dev/board-config
error: open /dev/board-config
error: open /dev/board-config
[*01/01/1970 00:01:04.8754] try_ramfs_boot: execl of new init: No space left on device..............................................

Does somebody know what i have to do now?

Re: Boot Error wit AP 1815t

Mark Elsen — Tue, 24 Aug 2021 09:21:30 GMT

- The situation does not seem that different from your initial post , answers from me and patoberti still apply, did the seller sold you something brand-new or used-already, you need to look at the integrity of both vendor and what was sold to you.

Re: Boot Error wit AP 1815t

Rich R — Tue, 24 Aug 2021 17:03:35 GMT

Sounds like somebody sold you faulty APs - return for a refund unless they can get them fixed for you.

Re: Boot Error wit AP 1815t

tidope90 — Mon, 16 May 2022 10:08:15 GMT

I am going to find out if I should buy a provider contract as I spent too much money and time on the lab and absolutely don't want to throw it away to get air rifle.

Just out of curiosity, does TAC use the flash power that came with APIC to repair the APIC signature? If not, what is the motive of that flash power?

Re: Boot Error wit AP 1815t

patoberli — Mon, 16 May 2022 12:29:54 GMT

This is probably unknown what TAC exactly does. I assume they have a way to
reimage those devices if they have corrupt signatures, but for us customers
it's typically RMA.