[AP3610] ERROR: Cannot boot either kernel image, dropping to interactive shell.

  • 13 April 2016
  • 2 replies
  • 311 views

Userlevel 1
Hello,

I need for recovery a AP3610 with kernel error. Does anyone know how I can fix this error? Some steps for getting the firmware image on the access point would be nice to have

Regards
Chris

U-Boot 1.2.0.07-dirty (Sep 23 2015 - 14:24:57)

Primary Image

DRAM: 128 MB
Flash: 16 MB
In: serial
Out: serial
Err: serial
Net: eth0
Hit any key to stop autoboot: 0
### JFFS2 loading 'boot_kernel.img2' to 0x80400000
Scanning JFFS2 FS: . done.
### JFFS2 load complete: 2979 bytes loaded to 0x80400000

## Checking Image at 80400000 ...
Image Name: Boot ROM Script
Created: 2010-06-21 17:46:19 UTC
Image Type: PowerPC Linux Script (uncompressed)
Data Size: 2915 Bytes = 2.8 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Executing script at 80400000
check for watchdog, limit=3...
check for reset by watchdog...
no watchdog...
bSaveEnviron=0 image_order=primary secondary
### JFFS2 loading 'primary.gz.uImage' to 0x80500000
### JFFS2 load complete: 5352637 bytes loaded to 0x80500000
ready to boot kernel, starting watchdog...
## Booting image at 80500000 ...
Image Name: Linux Kernel Image (LZMA)
Created: 2015-12-02 17:31:56 UTC
Image Type: MIPS Linux Kernel Image (uncompressed)
Data Size: 5352573 Bytes = 5.1 MB
Load Address: 84000000
Entry Point: 8400239c
Verifying Checksum ... Bad Data CRC
boot failed - stopped watchdog
### JFFS2 loading 'secondary.gz.uImage' to 0x80500000
### JFFS2 load complete: 5352801 bytes loaded to 0x80500000
ready to boot kernel, starting watchdog...
## Booting image at 80500000 ...
Image Name: Linux Kernel Image (LZMA)
Created: 2015-09-23 18:24:46 UTC
Image Type: MIPS Linux Kernel Image (uncompressed)
Data Size: 5352737 Bytes = 5.1 MB
Load Address: 84000000
Entry Point: 8400239c
Verifying Checksum ... Bad Data CRC
boot failed - stopped watchdog
ERROR: Cannot boot either kernel image, dropping to interactive shell.

2 replies

Userlevel 7
You should contact GTAC for assistance, the unit will need to be replaced or repaired based on your contract agreement (if any) with Extreme.

https://gtacknowledge.extremenetworks.com/articles/How_To/Return-Material-Authorization-RMA-Process-...
We've got the same error on multiple AP3705 and managed to solve this issue.
When you get to the interactive shell (console), you can logon with admin, pwd= new2day
Here you can list the files present in you AP.
In our case we saw following list by using the command 'ls':
drwxr-xr-x 0 Thu Jan 01 00:00:41 1970 var
drwxr-xr-x 0 Thu Jan 01 00:00:25 1970 home
-rw-r--r-- 4142 Thu Jan 01 00:00:28 1970 confData.bin
-rw-r--r-- 2628118 Thu Jan 01 00:03:36 1970 diag.gz.uImage
-rwxr-xr-x 4442 Thu Jan 01 00:00:27 1970 v2_confData.bin
-rw-r--r-- 2992 Fri Nov 30 18:31:15 2012 boot_kernel.img2
-rw-r--r-- 2992 Fri Nov 30 18:31:15 2012 boot_kernel.bak2
-rw-r--r-- 5228994 Wed May 21 09:41:14 2014 primary.gz.uImage
-rw-r--r-- 4974535 Thu Jan 01 00:02:34 1970 secondary.gz.uImage

You can load the secondary image into memory:
fsload secondary.gz.uImage
And boot the image that is now loaded in memory:
bootm

After two bootcycles, the AP booted with the stock image and was up and running.
I recommend to upgrade your AP with your controller afterwards

Reply