I encountered this a few times in the past 2 3 years i'm using catalyst. I never could fix it. Instead i switched to zisofs. That is if you don't mind having some 20-30Mb extra space on the iso. Also i have to note that this happened always after some time since the last stage2 building. So for me it was just the portage tree that changed. Then switching back to squashfs after 2 3 months was sometimes ok but not all the time. In my experience, i don't think this has to do with catalyst versioning. I tried numerous times to rebuild but this led me no where. Zisofs did the trick although i'm still wondering why. Sorry i can't be of more help. Erick sent from Android Le 3 août 2009, 2:44 PM, "lurker" a écrit : A few days ago I made a few small changes (just to the root overlay) to a catalyst project of mine and re-ran from livecd2 stage. For some reason boot now fails during init: [...] >> Mounting squashfs filesystem mount: mounting /dev/loop0 on /newroot/mnt/livecd failed: Invalid argument !! Failed to $1: failing back to the shell... BusyBox v1.7.4 [...] If I then, from the ash shell that you're thrown into, run "mount -o loop -t squashfs /newroot/mnt/cdrom/image.squashfs /newroot/mnt/livecd" I get the same error as above (invalid argument). Nothing appears in dmesg. I've tried upgrading catalyst from 2.0.6 to 2.0.6.905, and genkernel (the one used "inside" the catalyst project) from 3.4.10-r2 to 3.4.10.905, but nothing helps. Not that I expected it to do anything since the changes I made since my last successful build cannot possibly have anything to do with any of the bugs fixed in the newer versions. How can I troubleshoot this further?