From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MXxRW-0005pr-4z for garchives@archives.gentoo.org; Mon, 03 Aug 2009 13:19:10 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9002FE052E; Mon, 3 Aug 2009 13:19:09 +0000 (UTC) Received: from mail-fx0-f211.google.com (mail-fx0-f211.google.com [209.85.220.211]) by pigeon.gentoo.org (Postfix) with ESMTP id 3B2E7E052E for ; Mon, 3 Aug 2009 13:19:09 +0000 (UTC) Received: by fxm7 with SMTP id 7so2488032fxm.34 for ; Mon, 03 Aug 2009 06:19:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=xccvxtu4erirWNnEgMbeuN+ubqUEzeRBdmXgZd0pKW4=; b=qcdqtjAZ1qGnFIXnDm36T6nP4bsBtUO0pbUor25KP1kVuQwTqbuW44DRN8yZh32927 LeKeGRX9UI29dNjZSuaT19qgePCcOKxoIe2XvdhmYqIY2HZqO8UAhjqaOpdxZHy/fPjt X7g226AZA2pFlJZx9SOwP/wFJJM+9CVEkgtOQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=efiV0VgNyTxHUd2rAbDlZpMTOM44CU3iTO/TJYYhbGBapJFWZh4LrF6lGD7WicRhrj GNGQs3QYqBJWsjuulc/Of1orRfDj5/X2bz48x+3MgDsu7uJWYdsGn1WAwpHyykCJIgle i8EGhNs+8XI3XHK8+CApofLNnaDjD3kNNXeg0= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org MIME-Version: 1.0 Received: by 10.239.173.81 with SMTP id d17mr594023hbf.59.1249305548484; Mon, 03 Aug 2009 06:19:08 -0700 (PDT) In-Reply-To: References: Date: Mon, 3 Aug 2009 13:19:08 +0000 Message-ID: Subject: RE : [gentoo-catalyst] Mounting squashfs fails From: Erick Michau To: gentoo-catalyst@lists.gentoo.org Content-Type: multipart/alternative; boundary=001485f6310e6ef1eb04703c9d13 X-Archives-Salt: 5a83a609-4759-4d76-b069-728b6425cd1f X-Archives-Hash: 20779ad24a41ae686d4f38dfa5c5097a --001485f6310e6ef1eb04703c9d13 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 las= t 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 th= e 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=C3=BBt 2009, 2:44 PM, "lurker" a =C3=A9crit : 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? --001485f6310e6ef1eb04703c9d13 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I encountered this a few times in the past 2 3 years i'm using catal= yst. 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 a= ll the time. In my experience, i don't think this has to do with cataly= st 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=C2=A0 more help.

Erick

sent from Android

Le=C2=A03 ao=C3=BBt 2009, 2:44 PM, "lurke= r" <lurker@= lavabit.com>=C2=A0a =C3=A9crit=C2=A0:

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<= br> !! 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?


--001485f6310e6ef1eb04703c9d13--