Your message dated Sat, 17 Apr 2010 20:11:54 +0200 with message-id <4BC9F9EA.9010304@debian.org> and subject line Re: Bug#578136: live-initramfs failing to mount filesystem.squashfs in Debian Live Squeeze 6.0alpha1 CD image has caused the Debian Bug report #578136, regarding please enable uuid for the filesystem image by default to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 578136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578136 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: live-initramfs failing to mount filesystem.squashfs in Debian Live Squeeze 6.0alpha1 CD image
- From: Shankar Gopalakrishnan <shankargopal@myfastmail.com>
- Date: Sat, 17 Apr 2010 14:04:31 +0530
- Message-id: <h2l37e06c391004170134oe6c34485wa3fc19ab9113c13a@mail.gmail.com>
Package: live-initramfs Downloaded image from here: http://cdimage.debian.org/cdimage/squeeze_live_alpha1/i386/iso-hybrid/debian-live-60alpha1-i386-gnome-desktop.iso All md5sums check out ok at all stages. Then undertook following steps: 1. Mounted image and copied all contents (including .disk directory) to third partition of flash drive. 2. Changed name of isolinux directory and isolinux.cfg to syslinux; edited all configuration files in isolinux directory to say "syslinux" in path; did not change name of isolinux.bin. 3. Installed syslinux from Puppy Linux on to boot record of this partition. 4. Included stanza in Grub on MBR of flash drive to boot from partition using chainloader. This procedure has worked fine with seven other Live CD images so far, including three other Debian Live images (LXDE and GNOME versions for Lenny from Debian Live site; Debian Eee 1.0b3 image, based on Squeeze). All have booted normally and allowed me to run persistent systems. Upon boot, main menu is presented. Choosing option for "Live" or "686" (and possibly all other options as well, have not tried) initiates boot sequence. Just after the line "squashfs 4.0" appears, boot process halts with this message: Can not mount /dev/loop0 (/live/image/live/filesystem.squashfs) on //filesystem.squashfs The file live.log that is created contains this: Mounting "/live/image/live/filesystem.squashfs" on "filesystem.squashfs" via "/dev/loop0" ... mount: mounting /dev/loop0 on //filesystem.squashfs failed : Invalid argument I rechecked all checksums, they check out. In case it was a version mismatch I ran "file filesystem.squashfs" from Puppy Linux and got this: /mnt/cdrom/live/filesystem.squashfs: Squashfs filesystem, little endian, version 4.0, -1880381185 bytes, 149287 inodes, blocksize: 66 bytes, created: Thu Nov 10 06:08:16 1938 So it appears to be a 4.0 squashfs file, which should mount (and incidentally does mount from Puppy). Bug 540000 appears to describe a similar event but this was closed without resolution. There is also a similar discussion at http://www.mail-archive.com/debian-live@lists.debian.org/msg00863.html but this too did not seem to have been resolved. Both earlier reports are much older.
--- End Message ---
--- Begin Message ---
- To: Shankar Gopalakrishnan <shankargopal@myfastmail.com>
- Cc: 578136-done@bugs.debian.org
- Subject: Re: Bug#578136: live-initramfs failing to mount filesystem.squashfs in Debian Live Squeeze 6.0alpha1 CD image
- From: Daniel Baumann <daniel@debian.org>
- Date: Sat, 17 Apr 2010 20:11:54 +0200
- Message-id: <4BC9F9EA.9010304@debian.org>
- Reply-to: daniel@debian.org
- In-reply-to: <o2g37e06c391004171014z53e6f636za52a8a143d19a4e@mail.gmail.com>
- References: <h2l37e06c391004170134oe6c34485wa3fc19ab9113c13a@mail.gmail.com> <4BC979C8.9050101@debian.org> <l2w37e06c391004170216v82cbc487x86dcb53dc4adc38a@mail.gmail.com> <4BC99197.9010701@debian.org> <o2r37e06c391004170554j859cc5c4t2d8bd37c7f9c0f73@mail.gmail.com> <4BC9B429.5020204@debian.org> <q2u37e06c391004170649hb59ad692y5d2a0669eac7267b@mail.gmail.com> <4BC9BDD2.1000505@debian.org> <j2j37e06c391004170657mcc671e7by8feeb2be38806806@mail.gmail.com> <4BC9BF62.2000907@debian.org> <o2g37e06c391004171014z53e6f636za52a8a143d19a4e@mail.gmail.com>
retitle 578136 please enable uuid for the filesystem image by default tag 578136 unreproducible tag 578136 moreinfo severity 578136 wishlist reassign 578136 live-helper thanks On 04/17/2010 07:14 PM, Shankar Gopalakrishnan wrote:Ok, I figured it out. It is indeed a 'bug' but it is due to a configuration that is most likely unique to me in the entire world :).this should be avoidable by making use of live-uuid in live-initramfs. -- Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baumann@panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-baumann/
--- End Message ---