Results 1 to 3 of 3

Thread: Kernel image corruption

  1. #1
    Join Date
    Jul 2008
    Posts
    268

    Default Kernel image corruption

    When upgrading to version 2.1.x, if you get the following error "ERROR: Image data failed checksum verification, image is corrupt. Aborting boot" when booting "Image Type: PowerPC Linux Kernel Image". The full output is shown below.

    NAND read: device 0 offset 0x0, size 0x180000

    Bad block at 0x120000 in erase block from 0x120000 will be skipped
    Reading data from 0x19f800 -- 100% complete.
    1572864 bytes read: OK

    NAND read: device 0 offset 0x200000, size 0x3000000

    Reading data from 0x31ff800 -- 100% complete.
    50331648 bytes read: OK
    ## Booting image at 02000000 ...
    Image Name: Linux-2.6.31.7-pika
    Image Type: PowerPC Linux Kernel Image (gzip compressed)
    Data Size: 1801751 Bytes = 1.7 MB
    Load Address: 00400000
    Entry Point: 00400450
    Verifying Checksum ... ERROR: Image data failed checksum verification, image is corrupt. Aborting boot


    The key here is the 'size 0x180000' in the top line. this represents the old loaded size for the kernel. If you do not have the latest uboot then you will need to recover the box via serial cable. To do so attach a serial cable to the Warp, enter uboot by pressing a key immediately after rebooting and then type the following commands:

    > setenv load_nand_kernel nand read.jffs2 0x02000000 0x00000000 0x00200000
    > saveenv
    > reset

  2. #2
    gwyncm Guest

    Default That works.... but now

    Thankyou that works fine kernel is booting. Now the ramdisk fails.
    Is there a similar fix for that?

    Basically it gets to about here and ....


    [ 46.970629] VFS: Mounted root (ext2 filesystem) on device 1:0.
    [ 46.976639] Freeing unused kernel memory: 140k init
    init started: BusyBox v1.10.3 (2010-02-26 07:26:10 EST)
    starting pid 822, tty '': '/sbin/syslogd'
    starting pid 824, tty '': '/sbin/klogd'
    starting pid 826, tty '': '/etc/rc.S'
    [ 47.101356] uncorrectable error :
    [ 47.104687] uncorrectable error :
    [ 47.108125] uncorrectable error :
    [ 47.111566] uncorrectable error :
    [ 47.115007] uncorrectable error :
    [ 47.118450] uncorrectable error :
    [ 47.121891] uncorrectable error :
    [ 47.125328] uncorrectable error :
    [ 47.128781] mtd->read(0x400 bytes from 0x0) returned ECC error
    [ 47.138722] uncorrectable error :
    [ 47.142006] uncorrectable error :

    And so on forever.

    Just a few observations about the upgrade process that may be of interest to you:

    1) Both the pads link and the images link in the download area point to images.

    2) Either the vfat module is not present or doesn't get loaded so the usb stick mounts without long filename support making all the .wrp files appear missing.

    3) There is an error in the flashecc script (that got me in this mess in the first place.

    [ -z "" ] actually yields a zero returncode and the script continues happily with no files.

    Hope the suggestions/observations are useful.

    Thankyou in advance for any suggestions.

    G

  3. #3
    Join Date
    Jul 2008
    Posts
    268

    Default

    This type of error is from a mismatch between uboot and ramdisk where the ramdisk image was written one method but being read using a different method. This usually occurs with a failure during the 2.0->2.1 upgrade procedure.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •