The cases in question are edge cases as far as the Launchpad build farm is concerned. Most of our builders are on at least trusty (3.13), and will be upgraded to xenial (4.4) soon. However, we haven't yet moved all armhf and powerpc builds off some relatively old bare-metal hosting yet, so some of those are still on precise (3.2).
armhf will be fixed soon (we have a newer builder cloud ready to be swapped in as soon as we've finished upgrading them from wily to xenial). For powerpc, it will take rather longer to get that up and running in our new cloud builder architecture; but only one of our nine builders is still running a precise kernel, and it should be possible to upgrade that to the backported trusty kernel independently. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1598136 Title: Fails to produce a loop-mountable FS on powerpc/armhf Status in cloud-images: In Progress Status in e2fsprogs package in Ubuntu: New Bug description: In yakkety cloud image builds for each of powerpc and armhf (but not amd64, i386, ppc64el, arm64 or s390x) we see the following failure: [2016-07-01 09:51:08] lb_binary_chroot P: Begin copying chroot... [2016-07-01 09:51:08] lb_binary_rootfs P: Begin building root filesystem image... 0+0 records in 0+0 records out 0 bytes copied, 3.7116e-05 s, 0.0 kB/s mke2fs 1.43.1 (08-Jun-2016) ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether binary/boot/filesystem.ext4 is mounted. Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata and journal checksum features. Discarding device blocks: 4096/343040 done Creating filesystem with 343040 4k blocks and 171600 inodes Filesystem UUID: 43ff7fc9-12bb-4151-8549-77c8e1e35e2c Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Allocating group tables: 0/11 done Writing inode tables: 0/11 done Creating journal (8192 blocks): done Writing superblocks and filesystem accounting information: 0/11 done mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. This is caused by this code in live-build's lb_binary_rootfs script: dd if=/dev/zero of=binary/${INITFS}/filesystem.${LB_CHROOT_FILESYSTEM} bs=1024k count=0 seek=${REAL_DIM} mkfs.${LB_CHROOT_FILESYSTEM} -F -b ${LB_EXT_BLOCKSIZE:-1024} -i 8192 -m 0 -L ${LB_HDD_LABEL} ${LB_EXT_RESIZEBLOCKS:+-E resize=${LB_EXT_RESIZEBLOCKS}} binary/${INITFS}/filesystem.${LB_CHROOT_FILESYSTEM} mkdir -p filesystem.tmp ${LB_ROOT_COMMAND} mount -o loop binary/${INITFS}/filesystem.${LB_CHROOT_FILESYSTEM} filesystem.tmp To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1598136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp

