Created
September 16, 2017 18:07
-
-
Save stephgosling/453be67319e2677bacb860ca3aa63330 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Info: Checking filesystem /var/tmp/mic/imgcreate-7pg4rM/tmp-WRdYgX/root.img | |
Info: Checking filesystem /var/tmp/mic/imgcreate-7pg4rM/tmp-WRdYgX/fimage.img | |
Info: Checking filesystem /var/tmp/mic/imgcreate-7pg4rM/tmp-WRdYgX/home.img | |
Info: Pack all loop images together to sfe-f5121-2.1.1.26-stephg03.tar.bz2 | |
Info: Running pack scripts ... | |
/home/steph/hadk/sfe-f5121-2.1.1.26-stephg03 /home/steph/hadk | |
0+0 records in | |
0+0 records out | |
0 bytes (0 B) copied, 7.627e-06 s, 0.0 kB/s | |
File descriptor 3 (/tmp/repolic3Oq8Bg/adaptation-community-common-f5121-2.1.1.26_LICENSE.txt (deleted)) leaked on pvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 4 (socket:[3876384]) leaked on pvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 6 (/dev/null) leaked on pvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 7 (/dev/urandom) leaked on pvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 9 (/dev/null) leaked on pvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 10 (/dev/null) leaked on pvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 11 (/dev/null) leaked on pvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 12 (/dev/null) leaked on pvcreate invocation. Parent PID 30444: /bin/bash | |
Physical volume "/dev/loop7" successfully created | |
File descriptor 3 (/tmp/repolic3Oq8Bg/adaptation-community-common-f5121-2.1.1.26_LICENSE.txt (deleted)) leaked on vgcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 4 (socket:[3876384]) leaked on vgcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 6 (/dev/null) leaked on vgcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 7 (/dev/urandom) leaked on vgcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 9 (/dev/null) leaked on vgcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 10 (/dev/null) leaked on vgcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 11 (/dev/null) leaked on vgcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 12 (/dev/null) leaked on vgcreate invocation. Parent PID 30444: /bin/bash | |
Volume group "sailfish" successfully created | |
losetup: root.img: failed to set up loop device: No such file or directory | |
e2fsck 1.43.1 (08-Jun-2016) | |
/sbin/e2fsck: Invalid argument while trying to open /dev/loop10 | |
The superblock could not be read or does not describe a valid ext2/ext3/ext4 | |
filesystem. If the device is valid and it really contains an ext2/ext3/ext4 | |
filesystem (and not swap or ufs or something else), then the superblock | |
is corrupt, and you might try running e2fsck with an alternate superblock: | |
e2fsck -b 8193 <device> | |
or | |
e2fsck -b 32768 <device> | |
resize2fs 1.43.1 (08-Jun-2016) | |
/sbin/resize2fs: Invalid argument while trying to open /dev/loop10 | |
We got ourselves root blocks _ _ | |
/usr/bin/expr: syntax error | |
after maths size _ _ | |
File descriptor 3 (/tmp/repolic3Oq8Bg/adaptation-community-common-f5121-2.1.1.26_LICENSE.txt (deleted)) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 4 (socket:[3876384]) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 6 (/dev/null) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 7 (/dev/urandom) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 9 (/dev/null) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 10 (/dev/null) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 11 (/dev/null) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 12 (/dev/null) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
Invalid argument for --size: B | |
Error during parsing of command line. | |
losetup: /dev/loop10: detach failed: No such device or address | |
File descriptor 3 (/tmp/repolic3Oq8Bg/adaptation-community-common-f5121-2.1.1.26_LICENSE.txt (deleted)) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 4 (socket:[3876384]) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 6 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 7 (/dev/urandom) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 9 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 10 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 11 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 12 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
0 logical volume(s) in volume group "sailfish" now active | |
2 logical volume(s) in volume group "kubuntu-vg" now active | |
dd: invalid number `' | |
losetup: home.img: failed to set up loop device: No such file or directory | |
e2fsck 1.43.1 (08-Jun-2016) | |
/sbin/e2fsck: Invalid argument while trying to open /dev/loop10 | |
The superblock could not be read or does not describe a valid ext2/ext3/ext4 | |
filesystem. If the device is valid and it really contains an ext2/ext3/ext4 | |
filesystem (and not swap or ufs or something else), then the superblock | |
is corrupt, and you might try running e2fsck with an alternate superblock: | |
e2fsck -b 8193 <device> | |
or | |
e2fsck -b 32768 <device> | |
resize2fs 1.43.1 (08-Jun-2016) | |
/sbin/resize2fs: Invalid argument while trying to open /dev/loop10 | |
We got ourselves home size _ _ | |
/usr/bin/expr: syntax error | |
File descriptor 3 (/tmp/repolic3Oq8Bg/adaptation-community-common-f5121-2.1.1.26_LICENSE.txt (deleted)) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 4 (socket:[3876384]) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 6 (/dev/null) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 7 (/dev/urandom) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 9 (/dev/null) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 10 (/dev/null) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 11 (/dev/null) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
File descriptor 12 (/dev/null) leaked on lvcreate invocation. Parent PID 30444: /bin/bash | |
Invalid argument for --size: B | |
Error during parsing of command line. | |
losetup: /dev/loop10: detach failed: No such device or address | |
File descriptor 3 (/tmp/repolic3Oq8Bg/adaptation-community-common-f5121-2.1.1.26_LICENSE.txt (deleted)) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 4 (socket:[3876384]) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 6 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 7 (/dev/urandom) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 9 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 10 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 11 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 12 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
0 logical volume(s) in volume group "sailfish" now active | |
2 logical volume(s) in volume group "kubuntu-vg" now active | |
dd: invalid number `' | |
File descriptor 3 (/tmp/repolic3Oq8Bg/adaptation-community-common-f5121-2.1.1.26_LICENSE.txt (deleted)) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 4 (socket:[3876384]) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 6 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 7 (/dev/urandom) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 9 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 10 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 11 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
File descriptor 12 (/dev/null) leaked on vgchange invocation. Parent PID 30444: /bin/bash | |
0 logical volume(s) in volume group "sailfish" now active | |
1+0 records in | |
1+0 records out | |
1 byte (1 B) copied, 5.5339e-05 s, 18.1 kB/s | |
e2fsck 1.43.1 (08-Jun-2016) | |
ext2fs_open2: Bad magic number in super-block | |
/sbin/e2fsck: Superblock invalid, trying backup blocks... | |
/sbin/e2fsck: Bad magic number in super-block while trying to open fimage.img | |
The superblock could not be read or does not describe a valid ext2/ext3/ext4 | |
filesystem. If the device is valid and it really contains an ext2/ext3/ext4 | |
filesystem (and not swap or ufs or something else), then the superblock | |
is corrupt, and you might try running e2fsck with an alternate superblock: | |
e2fsck -b 8193 <device> | |
or | |
e2fsck -b 32768 <device> | |
resize2fs 1.43.1 (08-Jun-2016) | |
/sbin/resize2fs: Bad magic number in super-block while trying to open fimage.img | |
Couldn't find valid filesystem superblock. | |
pigz: skipping: root.img does not exist | |
md5sum: root.img.gz: No such file or directory | |
pigz: skipping: home.img does not exist | |
md5sum: home.img.gz: No such file or directory | |
mount: wrong fs type, bad option, bad superblock on /dev/loop10, | |
missing codepage or helper program, or other error | |
In some cases useful info is found in syslog - try | |
dmesg | tail or so. | |
umount: /home/steph/hadk/sfe-f5121-2.1.1.26-stephg03/tmp.iAVho30500: not mounted | |
rmdir: /home/steph/hadk/sfe-f5121-2.1.1.26-stephg03/tmp.iAVho30500: Directory not empty | |
e2fsck 1.43.1 (08-Jun-2016) | |
ext2fs_open2: Bad magic number in super-block | |
/sbin/e2fsck: Superblock invalid, trying backup blocks... | |
/sbin/e2fsck: Bad magic number in super-block while trying to open fimage.img | |
The superblock could not be read or does not describe a valid ext2/ext3/ext4 | |
filesystem. If the device is valid and it really contains an ext2/ext3/ext4 | |
filesystem (and not swap or ufs or something else), then the superblock | |
is corrupt, and you might try running e2fsck with an alternate superblock: | |
e2fsck -b 8193 <device> | |
or | |
e2fsck -b 32768 <device> | |
resize2fs 1.43.1 (08-Jun-2016) | |
/sbin/resize2fs: Bad magic number in super-block while trying to open fimage.img | |
Couldn't find valid filesystem superblock. | |
"fimage.img" size (1400000001) is not a multiple of the block size (4096). | |
mv: cannot stat `*.bin': No such file or directory | |
/home/steph/hadk | |
Info: The new image can be found here: | |
/home/steph/hadk/sfe-f5121-2.1.1.26-stephg03/Jolla-2.1.1.26-f5121-armv7hl.ks | |
/home/steph/hadk/sfe-f5121-2.1.1.26-stephg03/Jolla-2.1.1.26-f5121-armv7hl.ks | |
/home/steph/hadk/sfe-f5121-2.1.1.26-stephg03/Jolla-2.1.1.26-f5121-armv7hl.packages | |
/home/steph/hadk/sfe-f5121-2.1.1.26-stephg03/Jolla-2.1.1.26-f5121-armv7hl.urls | |
/home/steph/hadk/sfe-f5121-2.1.1.26-stephg03/SailfishOS--stephg03-2.1.1.26-f5121-0.0.1+master.20170125170904.537a491.1.tar.bz2 | |
/home/steph/hadk/sfe-f5121-2.1.1.26-stephg03/extracting-README.txt | |
/home/steph/hadk/sfe-f5121-2.1.1.26-stephg03/hw-release | |
/home/steph/hadk/sfe-f5121-2.1.1.26-stephg03/sailfish-release | |
/home/steph/hadk/sfe-f5121-2.1.1.26-stephg03/sfe-f5121-2.1.1.26-stephg03.tar.bz2 | |
/home/steph/hadk/sfe-f5121-2.1.1.26-stephg03/sfe-f5121-2.1.1.26-stephg03.xml | |
/home/steph/hadk/sfe-f5121-2.1.1.26-stephg03/tmp.iAVho30500 | |
Info: Finished. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment