Re: initrd problem: not yet fixed
> This message appears in the cramfs code, and it's printed when the
> code finds an invalid magic number in the superblock. (Rather
> obvious.) This is very strange, since the previous message indicates
> the magic number is there.
> I mounted the initrd image on a loop device: OK.
> I copied the image to a ram disk, and tried to mount that: I get the
> same error (wrong magic).
did you have a look at the magic number inside the initrd root system?