cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4090
Views
10
Helpful
2
Replies

1832i Can't boot. Is it a hardware problem?

AlexChan21895
Spotlight
Spotlight

Console output:

------------------------------------------------------------

 

U-Boot 2012.07 (btldr release 30) (Mar 03 2017 - 19:13:24)

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:  1 GiB
NAND (ONFI): Detected MICRON MT29F2G08ABBEAH4 [524544 MiB]
SF: Detected Macronix MX25U3235F [4 MiB]
MFG data loaded
Scanning shenv data blocks
Total valid parts=4
Active shenv part[0:0], write_counter=21
PCI0 Link Intialized
PCI1 Link Intialized
Net:
PHY ID = 0x4dd074, eth0 found AR8033 PHY
PHY ID = 0x4dd074, eth1 found AR8033 PHY
Valid I2C chip addresses: 51 52
AP 1832 . detected...
Power Type: Power Brick detected...
Signature returns 0
BL signing verification success, continue to run...
Auto boot mode, use bootipq directly
Hit ESC key to stop autoboot:  0
Specified BOOT: part2
nand0: partition (fs) size alignment incorrect
Error initializing mtdparts!

Booting from part2

nand0: partition (fs) size alignment incorrect
Error initializing mtdparts!

Booting failed, try boot on part1

nand0: partition (fs) size alignment incorrect
Error initializing mtdparts!
(RNAQ-C7) #

------------------------------------------------------

 

 

 

I notice the error is:

--------------------------------------------

Specified BOOT: part2
nand0: partition (fs) size alignment incorrect
Error initializing mtdparts!

Booting from part2

nand0: partition (fs) size alignment incorrect
Error initializing mtdparts!

Booting failed, try boot on part1

nand0: partition (fs) size alignment incorrect
Error initializing mtdparts!

---------------------------------------------

 

 

I try to 20sec reset and tftp a firmware.Not work. But it can boot form TFTP when use command "bootipq tftp".  Then it can work normally with WLC. It will appear the same problem when restart it.

Is it a software or hardware problem?

Thanks.

2 Replies 2

Rich R
VIP
VIP
I'd guess faulty flash but not sure if COS AP's have an option to do fsck to make sure it's not just flash corruption.
Otherwise TAC case and probably RMA - TAC will tell you if it's something that can be fixed without replacing the hardware.

>>> But it can boot form TFTP when use command "bootipq tftp".  Then it can work normally with WLC. It will appear the same problem when restart it. <<<

looks like it cannot find a valid image in flash, but can if you manually boot from tftp server

then the image is run from RAM instead of flash.

you can try from the WLC to perform a preload of the primary or backup image on flash (as if this is an upgrade).

if this fails than I suspect  the flash is faulty and you need to RMA.

 

I guess this went wrong:

  • To reset the AP to its default factory-shipped configuration, keep the mode button pressed for less than 20 seconds. The AP's configuration files are cleared.

This resets all configuration settings to factory defaults, including passwords, WEP keys, the IP address, and the SSID. However, the regulatory domain provisioning is not reset.

  • To clear the AP’s internal storage, including all configuration files and the regulatory domain configuration, keep the mode button pressed for more than 20 seconds, but less than 60 seconds.

you held the button too long and "cleared the AP's internal storage" wich could read as "erased the  flash"!

source: Cisco Aironet 1830 Series Access Points Getting Started Guide

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card