On Monday 09 December 2002 17:55, Rafael E. Herrera wrote:
Try not using custom options in mke2fs and gzip. The program that tries to load the image may no be smart enough to handle non default options.
Just tried it. It didn't work. However, I noticed an error message that must have passed me by earlier. "fsck.ext2: Filesystem has unsupported feature(s) while trying to open /dev/ram2" Then there's the bit about corrupt superblocks: "The superblock could not be read or does not describe a correct filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap of ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>" Unsupported features? The SuSE rescue disk, which my rescue disk is based on, uses SuSE 5.3/libc5. The system I use to generate the rescue disk is SuSE 7.3. Is that important? The kernel is the same, version 2.4. I tried "mke2fs -O none", which is supposed to turn off some features if you're going to use the file system with a pre-2.2 kernel, just in case. It didn't work either.