XPost: uk.comp.os.linux   
   From: theom+news@chiark.greenend.org.uk   
      
   In uk.comp.os.linux Java Jive  wrote:   
   > mv fs.initrd initrd   
   > tar -zcf initrd.tar.gz initrd/   
   > mv initrd fs.initrd   
   >   
   > # Create ext2 image   
   > mkdir initrd   
   > dd if=/dev/zero of=initrd.img bs=1k count=8192   
   > /sbin/mkfs.ext2 -F -v -m0 initrd.img   
   > sudo mount -o loop initrd.img initrd/   
   > sudo tar -zvxf initrd.tar.gz initrd   
   > sudo umount initrd/   
   >   
   > echo -e " \033[1;32m<< Exit Critcal Section! >>\033[0m"   
   >   
   > sudo gzip -9 < initrd.img > initrd.img.gz   
   > sudo rm -rf initrd   
   > sudo rm -f initrd.tar.gz   
   > sudo rm -f initrd.img   
   >   
   > INITRDCHECKSUM=`./ram2bin -i initrd.img.gz -e "${MODELNAME}" -t 4 -q -f`   
   > sed -i -e "s/^INITRD_CHECKSUM.*/INITRD_CHECKSUM\tvalue\t`echo   
   > ${INITRDCHECKSUM}`/g" ${METADATA}   
      
   > RAMDISK: Compressed image found at block 0   
   >   
   > # Above is normal   
   > # Below is crash   
   >   
   > EXT3-fs: Magic mismatch, very weird !   
   > List of all partitions:   
   > 0800 3907018584 sda driver: sd   
   >    0801     498688 sda1   
   >    0802 3906518016 sda2   
   > 1f00        128 mtdblock0 (driver?)   
   > 1f01       1792 mtdblock1 (driver?)   
   > 1f02       1664 mtdblock2 (driver?)   
   > 1f03        448 mtdblock3 (driver?)   
   > 1f04         48 mtdblock4 (driver?)   
   > 1f05          8 mtdblock5 (driver?)   
   > 1f06          8 mtdblock6 (driver?)   
   > No filesystem could mount root, tried:  ext3 ext2 vfat fuseblk   
   > Kernel panic - not syncing: VFS: Unable to mount root fs on   
   > unknown-block(1,0)   
   >   
   > # Below *would* have been a normal continuation for a successful boot   
   >   
   > VFS: Mounted root (ext2 filesystem).   
      
   So you appear to be making an ext2 FS and gzipping it.  Do you get the   
   'RAMDISK: Compressed image found' in the crash scenario?   
      
   Searching on "Magic mismatch, very weird" comes up with some threads. One is   
   hardware failure, the other is about using a non-1k blocksize with (old) mke2fs   
   and a 2007-era ramdisk implementation that doesn't support other than 1k:   
   https://sourceforge.net/p/e2fsprogs/bugs/175/#b0df   
      
   Perhaps you could try -b1024 on the mkfs.ext2 command?  Or experiment with   
   other blocksizes?   
      
   Theo   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)