Linux throwing "uncompression error" on rootfs.ext2.gz ?
Curious if anyone has run into an issue where their ext2.gz image causes linux boot to say "uncompression error", like this:
...
RAMDISK: gzip image found at block 0 uncompression error
VFS: Mounted root (ext2 filesystem) on device 1:0.
...
I have two patches to my buildroot install, one that causes this, and one that doesn't. Both have the same config file.
I can't imagine this to be caused by the contents of the skeleton, unless it is a bug in either buildroot (or its zipper), or my Linux kernel (ARM). My kernel is 2.6.37.
I can't see any significant changes in the kernel to lib/decompress_inflate.c, lib/zlib_deflate, or lib/zlib_inflate since our version.
Also of interest, the suspect file passes a 7zip "Test archive".
Thanks for any help or ideas!
-Judson
Le Mon, 02 Jul 2012 17:57:08 -0700,
Judson Wilson <[email protected]> a ?crit :
Quoted 8 lines
Curious if anyone has run into an issue where their ext2.gz image causes linux boot to say "uncompression error", like this:
...
RAMDISK: gzip image found at block 0 uncompression error
VFS: Mounted root (ext2 filesystem) on device 1:0.
...
Are you using this file as an initrd, or as the real root filesystem? Could you share some details about your setup (where do you put the ext2.gz image, what is your kernel command line, kernel configuration, etc.).
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
Quoted 6 lines
Are you using this file as an initrd, or as the real root filesystem? Could you share some details about your setup (where do you put the ext2.gz image, what is your kernel command line, kernel configuration, etc.).
Thomas
You asked the right questions! Turns out I was not expanding my U-Boot serial flash read commands to match my new larger flash partitions and images - so only part of the image was getting copied to RAM.
Thank you for the help!
- Judson