Booting from the newest LiveCD (install-x86-minimal-20090602.iso) fails consistently on several computers that ran Gentoo LiveCDs just fine before. Reproducible: Always Steps to Reproduce: 1. download current Gentoo Minimal Install CD from http://www.gentoo.org/main/en/where.xml 2. burn CD 3. boot Actual Results: while booting: >> Media found on /dev/hdc >> Determining root device... >> Determining looptype ... >> Mounting squashfs filesystem mount: mounting /dev/loop0 on /newroot/mnt/livecd failed: Invalid argument !! Failed to $1; failing back to shell... BusyBox v1.7.4 (2009-06-02 18:20:53 UTC) built-in shell (ash) Enter 'help' for a list of build-in commands. /bin/ash: can't access tty; job control turned off # Expected Results: well...boot correctly, of course :-) The error occurred when trying to set up a new server. At first I suspected a bad media, so I burnt another one from a m5sum-verified iso file. After getting the exact same error I tried booting from the iso image with VirtualBox and got the same behavior. The old LiveCD (2008.0) boots fine on all computers that failed with the current LiveCD.
It looks like the newer kernels do not support the older sqaushfs format. The error message is: SQUASHFS error: Major/Minor mismatch, older Squashfs 3.1 filesystems are unsupported On poseidon (the x86/amd64 build machine), we're using squashfs-tools-3.3, which is the latest stable. Perhaps it's time to stabilize squashfs-tools-4.0.
I've heard from others that this bug would be fixed by using squashfs-tools-4.0, so please stabilise it for arch :)
*** Bug 272869 has been marked as a duplicate of this bug. ***
From others? You mean my comment on this bug right above your comment?
*** Bug 272984 has been marked as a duplicate of this bug. ***
I've opened bug #273131 requesting stabilization of squashfs-tools-4.0. In the mean time, I'll force installation of the newer squashfs-tools on the x86/amd64 build machine.
Hi folks, I am currently having this issue with install-amd64-minimal-20090604.iso too. Anyone knows the latest working version of LiveCD or if the tonight builds will fix this bug? I need the latest kernel available (ie 2.6.29-gentoo-r5) because i am having I/O problems when formating an EXT3 partition with the LSI 1064E SAS Controler using 2008.0 LiveCD. Thanks in advance and keep the nice work you do! Best regards, Andres Montalban
@Andres: Last week's build (0526) worked fine for me, and you should be able to do what you are wanting to, with it.
sys-fs/squashfs-tools-4.0 has been marked stable for: alpha/amd64/ia64/sparc/x86 (bug #273131) Now we just have to wait for tonight's autobuild - and all should be well! :)
(In reply to comment #9) > sys-fs/squashfs-tools-4.0 has been marked stable for: > alpha/amd64/ia64/sparc/x86 (bug #273131) > > Now we just have to wait for tonight's autobuild - and all should be well! :) > I have this problem with minimal iso for amd64 downloaded yesterday # md5sum ~mmokrejs/tmp/gentoo/install-amd64-minimal-20090604.iso 04d6dc1d0a144f98f17764dac3994790 /home/mmokrejs/tmp/gentoo/install-amd64-minimal-20090604.iso # Seems the file date are June 4 still: http://distfiles.gentoo.org/releases/amd64/current/
(In reply to comment #10) > (In reply to comment #9) > > I have this problem with minimal iso for amd64 downloaded yesterday > > # md5sum ~mmokrejs/tmp/gentoo/install-amd64-minimal-20090604.iso > 04d6dc1d0a144f98f17764dac3994790 > /home/mmokrejs/tmp/gentoo/install-amd64-minimal-20090604.iso > # Fixed in install-amd64-minimal-20090611.iso.
Sorry to revive this, but this seems to be occurring in the latest livedvd. Perhaps slightly changed (now with aufs module) but seems to be the same bug, no? >> Mounting squashfs & aufs2 filesystems >> Loading aufs module mount: mounting /dev/loop0 on /mnt/static failed: Invalid argument $ md5sum livedvd-amd64-multilib-2012.1.iso eb0e08edcb13091c6707ce267338dcf2 livedvd-amd64-multilib-2012.1.iso
(In reply to comment #12) > Sorry to revive this, but this seems to be occurring in the latest livedvd. It would be great if you don't revive 3 year old bugs for different issues. Can you file a new bug so it gets triaged properly? Thanks.
