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=2000000000 --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 00000000004018e0 sp > 00007ffff324d340 error 4 in sulogin[400000+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
