AP230 failed to restart and is now stuck on red light, reset will not work, next steps?

jorr1 — Wed, 13 Feb 2019 05:45:10 GMT

Here's the CLI: It hangs before the system actual boots:

Using default environment

In: serial

Out: serial

Err: serial

Unlocking L2 Cache ...Done

arm_clk=1000MHz, axi_clk=500MHz, apb_clk=250MHz, arm_periph_clk=500MHz

Net: Registering eth

Broadcom BCM IPROC Ethernet driver 0.1

Using GMAC1 (0x18025000)

et0: ethHw_chipAttach: Chip ID: 0xcf12; phyaddr: 0x1e

bcm_robo_attach: devid: 0x53012

bcmiproc_eth-0

MAC address is d854:a2f3:f480

Reset TPM chip...

Hit any key to stop autoboot: 0

Loading kernel from device 0: nand0 (offset 0xa80000) ... done

Loading rootfs from device 0: nand0 (offset 0x3780000) ... done

## Booting kernel from Legacy Image at 01005000 ...

Image Name: Linux-3.16.36

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 2573781 Bytes = 2.5 MiB

Load Address: 80008000

Entry Point: 80008000

Verifying Checksum ... OK

## Loading init Ramdisk from Legacy Image at 02005000 ...

Image Name: uboot initramfs rootfs

Image Type: ARM Linux RAMDisk Image (uncompressed)

Data Size: 27791360 Bytes = 26.5 MiB

Load Address: 00000000

Entry Point: 00000000

Verifying Checksum ... OK

Power off two PHY...

Loading Kernel Image ... OK

boot_prep_linux commandline: root=/dev/ram console=ttyS0,9600 ramdisk_size=70000 cache-sram-size=0x10000

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

L2C: platform provided aux values match the hardware, so have no effect. Please remove them.

L2C: platform provided aux values permit register corruption.

Mounting local file systems...

jffs2: notice: (55) check_node_data: wrong data CRC in data node at 0x18bf1330: read 0x92c19e8f, calculated 0xf41c8161.

jffs2: notice: (70) check_node_data: wrong data CRC in data node at 0x13cabec0: read 0x811d9572, calculated 0x75320a8f.

jffs2: notice: (119) check_node_data: wrong data CRC in data node at 0x0b157d2c: read 0x4108ea23, calculated 0xe552a59d.

jffs2: notice: (55) check_node_data: wrong data CRC in data node at 0x01de23ec: read 0x8772f29f, calculated 0xe4f73da5.

kmpi: module license 'Aerohive Networks,Inc.' taints kernel.

Disabling lock debugging due to kernel taint

Updating system config database...

System POE Input Detection -> confDC

ig update complete.

eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 10.10.80.505_e5.1.2.3 (r659762)

eth1: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 10.10.80.505_e5.1.2.3 (r659762)

Aerohive Wireless Extension 2.0.0 ... INIT!

Aerohive Forwarding Engine module ... INIT!

Image L7 repository version 5, checking existing L7 repository... ...

Existing L7 repository version 5

Nothing to be done or verified with L7 repository version 5

Re: AP230 failed to restart and is now stuck on red light, reset will not work, next steps?

samantha_lynn — Wed, 13 Feb 2019 21:32:45 GMT

Thanks very much for that output. At this point you would need a TFTP flash, which requires an Aerohive engineer on a screen sharing session with you. I've linked your user record to your account and enabled full access for you, could you please open a technical support case and request to set up a time for a TFTP flash?

Re: AP230 failed to restart and is now stuck on red light, reset will not work, next steps?

jorr1 — Thu, 14 Feb 2019 03:28:55 GMT

Thanks for getting back to me, Sam.

After several reboots yesterday, I finally got to the login point. I was able to log in, and run: load config default

reboot backup

I came back in today, and the AP is up. It is back in our HiveManager as it should be, and I was able to install an OS update, so I think we are back in business.

topic Re: AP230 failed to restart and is now stuck on red light, reset will not work, next steps? in Aerohive Migrated Content

AP230 failed to restart and is now stuck on red light, reset will not work, next steps?

Re: AP230 failed to restart and is now stuck on red light, reset will not work, next steps?

Re: AP230 failed to restart and is now stuck on red light, reset will not work, next steps?