i.MX53 kernel panic "invalid blocks count"

[fcs]

I have successfully done a minimal build with the i.MX53 ltib and deployed it to a microSD card by doing

sudo cp -r ltib/rootfs/* /media/sdcard/

Is this the best way to deploy the built image?

However the "FSL gnome release packages" build has a kernel panic during the boot:

mke2fs 1.41.4 (27-Jan-2009)

init: invalid blocks count - setenv

Kernel panic - not syncing: Attempted to kill init!

[<800384c0>] (unwind_backtrace+0x0/0xf0) from [<80408b18>] (panic+0x6c/0xe0)

[<80408b18>] (panic+0x6c/0xe0) from [<80065a2c>] (do_exit+0x68/0x654)

[<80065a2c>] (do_exit+0x68/0x654) from [<800660c8>] (do_group_exit+0xb0/0xe0)

[<800660c8>] (do_group_exit+0xb0/0xe0) from [<80066108>] (sys_exit_group+0x10/0x18)

[<80066108>] (sys_exit_group+0x10/0x18) from [<80033f80>] (ret_fast_syscall+0x0/0x30)

I have attached the complete kernel boot output. What does "invalid blocks count" mean?

It has something to do with mke2fs:

http://comments.gmane.org/gmane.linux.installation.system-imager.general/1897

[fcs]

Somehow I had a very small busybox binary installed on the microSD which didn't do mke2fs properly. The correct busybox binary is over 600kb and works correctly when executed by the kernel init as an alias for /sbin/init

[HuiShao]

Hi fcs,

Did your panic got resolved? I got a similar kernel panic after enabling MTD package to my rootfs. SD card had  been working fine before I added MTD to rootfs. Any idea on it? My boot log is as followings:

VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2

input: mxc_ts as /devices/virtual/input/input2

mxc input touchscreen loaded (modified for CSSU's ADC)

mxc_rtc mxc_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)

Waiting for root device /dev/mmcblk0p1...

mmc0: new high speed SD card at address 1234

mmcblk0: mmc0:1234 SA02G 1.83 GiB

mmcblk0: p1

EXT3-fs: barriers not enabled

EXT3-fs (mmcblk0p1): warning: maximal mount count reached, running e2fsck is recommended

kjournald starting.  Commit interval 5 seconds

EXT3-fs (mmcblk0p1): using internal journal

EXT3-fs (mmcblk0p1): mounted filesystem with writeback data mode

VFS: Mounted root (ext3 filesystem) on device 179:1.

Freeing init memory: 168K

Usage: init [-c|-l filename] [-b block-size] [-f fragment-size]

        [-i bytes-per-inode] [-I inode-size] [-J journal-options]

        [-G meta group size] [-N number-of-inodes]

        [-m reserved-blocks-percentage] [-o creator-os]

        [-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]

        [-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]

        [-T fs-type] [-U UUID] [-jnqvFSV] device [blocks-count]

Kernel panic - not syncing: Attempted to kill init!

[<800374c0>] (unwind_backtrace+0x0/0xf0) from [<803e5a5c>] (panic+0x6c/0xe0)

[<803e5a5c>] (panic+0x6c/0xe0) from [<80064a80>] (do_exit+0x68/0x654)

[<80064a80>] (do_exit+0x68/0x654) from [<8006511c>] (do_group_exit+0xb0/0xe0)

[<8006511c>] (do_group_exit+0xb0/0xe0) from [<8006515c>] (sys_exit_group+0x10/0x18)

[<8006515c>] (sys_exit_group+0x10/0x18) from [<80032f80>] (ret_fast_syscall+0x0/0x30)

[fcs]

At a glance it seems to be executing an init binary, on the i.MX53 QSB image I am using /sbin/init is just a symbolic link to /bin/busybox:

ls -la /sbin/init

lrwxrwxrwx    1 root     root            14 Oct 22  2012 /sbin/init -> ../bin/busybox