Bug#764596: vmdebootstrap generated sid images fail to boot on fsck error loop
Control: affects -1 xen-tools
Hi,
Ben Hutchings wrote:
I just tried to build an image of current sid for running autopkgtests
in:
$ sudo vmdebootstrap --verbose --serial-console --distribution=sid
--user=adt/adt --size=20 --mbr --image=adt-sid.raw
This worked in the past, but now they are stuck in a boot failure
loop;
$ kvm -m 2048 -snapshot -drive file=adt-sid.raw,if=virtio -monitor none
-nographic -serial stdio
[...]
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top
... done.
Begin: Running /scripts/local-premount ... done.
Begin: Checking root file system ... fsck from util-linux 2.25.1
fsck: error 2 (No such file or directory) while executing fsck.ext4 for
/dev/vda1
fsck exited with status code 8
done.
[...]
Same counts for Sid Xen DomU bootstrapped via xen-tools (at least with
the git version, both with the modification mentioned below as well as
with an unmodified git checkout):
$ xen-create-image --dist sid --hostname domu1 --force --lvm vg0 --dhcp
--verbose --pygrub --noaccounts --boot; xl console domu1
[...]
Begin: Checking root file system ... fsck from util-linux 2.25.2
fsck: error 2 (No such file or directory) while executing fsck.ext3 for
/dev/xvda2
fsck exited with status code 8
done.
Failure: An automatic file system check (fsck) of the root filesystem failed.
A manual fsck must be performed, then the system restarted.
The fsck should be performed in maintenance mode with the
root filesystem mounted in read-only mode.
Warning: The root filesystem is currently mounted in read-only mode.
A maintenance shell will now be started.
After performing system maintenance, press CONTROL-D
to terminate the maintenance shell and restart the system.
sulogin: cannot open password database!
[3.510843] sulogin[84]: segfault at 8 ip 004018e0 sp
7fff8510bce0 error 4 in sulogin[40+3000]
Segment violation
Failure: Attempt to start maintenance shell failed.
Will restart in 5 seconds.
[8.518847] reboot: Restarting system
This might be a regression from recent util-linux, or some
misconfiguration, or incompatibility with extlinux, not sure.
fsck.ext4 definitively exists (i. e. e2fsprogs is installed), and
/dev/vda1 also exists; it's also apparently able to map the root UUID
to /dev/vda1.
[...]
fsck.ext4 is not present in the initramfs, probably because
initramfs-tools was installed before e2fsprogs. Unfortunately, we
cannot simply make initramfs-tools depend on the appropriate package
because it depends on which filesystem is used for root.
vmdebootstrap should install the kernel last so that all programs that
may be wanted in the initramfs will be available when the initramfs is
built.
I expected that this would count for xen-tools as well and tried to
fix it by explicitly installing e2fsprogs before initramfs-tools and
the kernel. But the above still happens despite I used this code to
install e2fsprogs, initramfs-tools and kernel:
installDebianPackage ${prefix} e2fsprogs
installDebianPackage ${prefix} initramfs-tools
installDebianPackage ${prefix} $KERNEL_PKG
So I doubt that this can be fixed by reordering the package
installations.
The following fsck binary is in the initrd:
# lsinitramfs -l /mnt/tmp//boot/initrd.img-3.16-3-amd64 | fgrep fsck
-rwxr-xr-x 1 root root35664 Oct 24 19:02 sbin/fsck
#
Regards, Axel
--
,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764596: vmdebootstrap generated sid images fail to boot on fsck error loop
Control: affects -1 - xen-tools Hi again, Axel Beckert wrote: Control: affects -1 xen-tools Sorry, this mail went to the wrong clone of the initial report. It was meant for #765614. (Didn't expect that the bug against initramfs-tools is the clone one and not the original one.) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764596: vmdebootstrap generated sid images fail to boot on fsck error loop
Control: clone -1 -2 Control: reassign -1 vmdebootstrap Control: retitle -1 vmdebootstrap should install kernel last Control: retitle -2 Missing fsck.type should be non-fatal On Thu, 2014-10-09 at 14:53 +0200, Martin Pitt wrote: Package: vmdebootstrap Version: 0.3-1 Hello, I just tried to build an image of current sid for running autopkgtests in: $ sudo vmdebootstrap --verbose --serial-console --distribution=sid --user=adt/adt --size=20 --mbr --image=adt-sid.raw This worked in the past, but now they are stuck in a boot failure loop; $ kvm -m 2048 -snapshot -drive file=adt-sid.raw,if=virtio -monitor none -nographic -serial stdio [...] Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Checking root file system ... fsck from util-linux 2.25.1 fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/vda1 fsck exited with status code 8 done. [...] This might be a regression from recent util-linux, or some misconfiguration, or incompatibility with extlinux, not sure. fsck.ext4 definitively exists (i. e. e2fsprogs is installed), and /dev/vda1 also exists; it's also apparently able to map the root UUID to /dev/vda1. [...] fsck.ext4 is not present in the initramfs, probably because initramfs-tools was installed before e2fsprogs. Unfortunately, we cannot simply make initramfs-tools depend on the appropriate package because it depends on which filesystem is used for root. vmdebootstrap should install the kernel last so that all programs that may be wanted in the initramfs will be available when the initramfs is built. But also, a fsck failure because fsck.type is missing should not be fatal. Ben. -- Ben Hutchings Life is what happens to you while you're busy making other plans. - John Lennon signature.asc Description: This is a digitally signed message part
Bug#764596: vmdebootstrap generated sid images fail to boot on fsck error loop
On Thu, 16 Oct 2014 17:57:07 +0200 Ben Hutchings b...@decadent.org.uk wrote: This might be a regression from recent util-linux, or some misconfiguration, or incompatibility with extlinux, not sure. fsck.ext4 definitively exists (i. e. e2fsprogs is installed), and /dev/vda1 also exists; it's also apparently able to map the root UUID to /dev/vda1. [...] fsck.ext4 is not present in the initramfs, probably because initramfs-tools was installed before e2fsprogs. Unfortunately, we cannot simply make initramfs-tools depend on the appropriate package because it depends on which filesystem is used for root. vmdebootstrap should install the kernel last so that all programs that may be wanted in the initramfs will be available when the initramfs is built. Installing the kernel separately is awkward due to the extra dependencies and a need to re-run debootstrap which is a slow task. Is it sufficient to just run update-initramfs -u later in the process? It works at this end (for extlinux grub) with a small change to vmdebootstrap. This results in a process like: $ sudo ./vmdebootstrap --verbose --image=sid.img --distribution=sid --mirror=http://mirror.bytemark.co.uk/debian --owner=neil Creating disk image Creating partitions Creating filesystem ext4 Mounting /dev/mapper/loop0p1 on /tmp/tmpyiZMML Debootstrapping Give root an empty password Removing udev persistent cd and net rules Setting up networking Updating the initramfs Installing extlinux Changing owner to neil Cleaning up $ I've pushed the change to master, if this sounds ok, Ben, I'll upload with this change. -- Neil Williams = http://www.linux.codehelp.co.uk/ signature.asc Description: PGP signature
Bug#764596: vmdebootstrap generated sid images fail to boot on fsck error loop
Hello Neil, Neil Williams [2014-10-16 19:55 +0100]: Installing the kernel separately is awkward due to the extra dependencies and a need to re-run debootstrap which is a slow task. Is it sufficient to just run update-initramfs -u later in the process? Ah, this is normally being done through the dpkg trigger, but I guess that wouldn't work with debootstrap. update-initramfs -u should totally be sufficient for this indeed. Thank you! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#764596: vmdebootstrap generated sid images fail to boot on fsck error loop
On Thu, 2014-10-16 at 19:55 +0100, Neil Williams wrote: On Thu, 16 Oct 2014 17:57:07 +0200 Ben Hutchings b...@decadent.org.uk wrote: This might be a regression from recent util-linux, or some misconfiguration, or incompatibility with extlinux, not sure. fsck.ext4 definitively exists (i. e. e2fsprogs is installed), and /dev/vda1 also exists; it's also apparently able to map the root UUID to /dev/vda1. [...] fsck.ext4 is not present in the initramfs, probably because initramfs-tools was installed before e2fsprogs. Unfortunately, we cannot simply make initramfs-tools depend on the appropriate package because it depends on which filesystem is used for root. vmdebootstrap should install the kernel last so that all programs that may be wanted in the initramfs will be available when the initramfs is built. Installing the kernel separately is awkward due to the extra dependencies and a need to re-run debootstrap which is a slow task. Is it sufficient to just run update-initramfs -u later in the process? [...] I've pushed the change to master, if this sounds ok, Ben, I'll upload with this change. Sounds fine to me. If you could change the installation order then that would avoid building the initramfs twice, but as that requires doing much more work twice then this is a better workaround. Ben. -- Ben Hutchings Life is what happens to you while you're busy making other plans. - John Lennon signature.asc Description: This is a digitally signed message part
Bug#764596: vmdebootstrap generated sid images fail to boot on fsck error loop
tag 764596 + help thanks On Thu, 9 Oct 2014 14:53:54 +0200 Martin Pitt mp...@debian.org wrote: Package: vmdebootstrap Version: 0.3-1 Hello, I just tried to build an image of current sid for running autopkgtests in: $ sudo vmdebootstrap --verbose --serial-console --distribution=sid --user=adt/adt --size=20 --mbr --image=adt-sid.raw This worked in the past, but now they are stuck in a boot failure loop; $ kvm -m 2048 -snapshot -drive file=adt-sid.raw,if=virtio -monitor none -nographic -serial stdio [...] Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Checking root file system ... fsck from util-linux 2.25.1 fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/vda1 fsck exited with status code 8 done. Failure: An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode. Warning: The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press CONTROL-D to terminate the maintenance shell and restart the system. sulogin: cannot open password database! [1.380144] tsc: Refined TSC clocksource calibration: 2594.111 MHz [3.237861] sulogin[94]: segfault at 8 ip 004018e0 sp 7324d340 error 4 in sulogin[40+3000] Segment violation Failure: Attempt to start maintenance shell failed. Will restart in 5 seconds. [8.245048] Unregister pv shared memory for cpu 0 [8.294086] reboot: Restarting system [8.295631] reboot: machine restart Then the kernel reboots, and it goes back to the very same problem again, over and over. This might be a regression from recent util-linux, or some misconfiguration, or incompatibility with extlinux, not sure. fsck.ext4 definitively exists (i. e. e2fsprogs is installed), and /dev/vda1 also exists; it's also apparently able to map the root UUID to /dev/vda1. I also tried with --grub; image generation succeeds and it says Configuring grub2 Installing extlinux Cleaning up at the end, but booting in qemu doesn't work at all (there's not a single message). That's a different bug/report, but I wanted to mention it. I see the same fsck problems with extlinux but with a test using grub, I get grub loading properly and then the same fsck error causing a retry. (I do get a Segment violation just before the retry) sudo vmdebootstrap --image sid2.img --distribution=sid --owner=neil --verbose --grub I'm not sure what is going wrong here, wheezy images work fine. Mounting the image using an offset works fine and fsck from outside the KVM using kpartx and /dev/mapper/loop1p1 works without errors too. I'm not sure this is a bug in vmdebootstrap. A test with Jessie and grub works: sudo vmdebootstrap --image jessie.img --distribution=jessie --owner=neil --verbose --grub That uses util-linux 2.20.1-5.11 I'm going to pull the package list out of the working jessie and diff against the broken sid... -- Neil Williams = http://www.linux.codehelp.co.uk/ signature.asc Description: PGP signature
Bug#764596: vmdebootstrap generated sid images fail to boot on fsck error loop
Package: vmdebootstrap Version: 0.3-1 Hello, I just tried to build an image of current sid for running autopkgtests in: $ sudo vmdebootstrap --verbose --serial-console --distribution=sid --user=adt/adt --size=20 --mbr --image=adt-sid.raw This worked in the past, but now they are stuck in a boot failure loop; $ kvm -m 2048 -snapshot -drive file=adt-sid.raw,if=virtio -monitor none -nographic -serial stdio [...] Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Checking root file system ... fsck from util-linux 2.25.1 fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/vda1 fsck exited with status code 8 done. Failure: An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode. Warning: The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press CONTROL-D to terminate the maintenance shell and restart the system. sulogin: cannot open password database! [1.380144] tsc: Refined TSC clocksource calibration: 2594.111 MHz [3.237861] sulogin[94]: segfault at 8 ip 004018e0 sp 7324d340 error 4 in sulogin[40+3000] Segment violation Failure: Attempt to start maintenance shell failed. Will restart in 5 seconds. [8.245048] Unregister pv shared memory for cpu 0 [8.294086] reboot: Restarting system [8.295631] reboot: machine restart Then the kernel reboots, and it goes back to the very same problem again, over and over. This might be a regression from recent util-linux, or some misconfiguration, or incompatibility with extlinux, not sure. fsck.ext4 definitively exists (i. e. e2fsprogs is installed), and /dev/vda1 also exists; it's also apparently able to map the root UUID to /dev/vda1. I also tried with --grub; image generation succeeds and it says Configuring grub2 Installing extlinux Cleaning up at the end, but booting in qemu doesn't work at all (there's not a single message). That's a different bug/report, but I wanted to mention it. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
