Info: Checking filesystem /var/tmp/mic/imgcreate-ed6rwf/tmp-gJGpI9/root.img
Info: Checking filesystem /var/tmp/mic/imgcreate-ed6rwf/tmp-gJGpI9/fimage.img
Info: Checking filesystem /var/tmp/mic/imgcreate-ed6rwf/tmp-gJGpI9/home.img
Info: Pack all loop images together to sfe-f5121-2.1.1.26.tar.bz2
Info: Running pack scripts ...
/home/mgh01/buildingpot/sfe-f5121-2.1.1.26 /home/mgh01/buildingpot
0+0 records in
0+0 records out
0 bytes (0 B) copied, 1.1736e-05 s, 0.0 kB/s
File descriptor 4 (socket:[200877]) leaked on pvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 5 (/dev/null) leaked on pvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 7 (/dev/urandom) leaked on pvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 9 (/dev/null) leaked on pvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 10 (/dev/null) leaked on pvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 11 (/dev/null) leaked on pvcreate invocation. Parent PID 21551: /bin/bash
  Physical volume "/dev/loop0" successfully created
File descriptor 4 (socket:[200877]) leaked on vgcreate invocation. Parent PID 21551: /bin/bash
File descriptor 5 (/dev/null) leaked on vgcreate invocation. Parent PID 21551: /bin/bash
File descriptor 7 (/dev/urandom) leaked on vgcreate invocation. Parent PID 21551: /bin/bash
File descriptor 9 (/dev/null) leaked on vgcreate invocation. Parent PID 21551: /bin/bash
File descriptor 10 (/dev/null) leaked on vgcreate invocation. Parent PID 21551: /bin/bash
File descriptor 11 (/dev/null) leaked on vgcreate invocation. Parent PID 21551: /bin/bash
  Volume group "sailfish" successfully created
losetup: root.img: failed to set up loop device: No such file or directory
e2fsck 1.42.4 (12-June-2012)
/sbin/e2fsck: Invalid argument while trying to open /dev/loop1

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
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>

We got ourselves root blocks _ _
/usr/bin/expr: syntax error
after maths size _ _
File descriptor 4 (socket:[200877]) leaked on lvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 5 (/dev/null) leaked on lvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 7 (/dev/urandom) leaked on lvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 9 (/dev/null) leaked on lvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 10 (/dev/null) leaked on lvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 11 (/dev/null) leaked on lvcreate invocation. Parent PID 21551: /bin/bash
  Invalid argument for --size: B
  Error during parsing of command line.
losetup: /dev/loop1: detach failed: No such device or address
File descriptor 4 (socket:[200877]) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 5 (/dev/null) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 7 (/dev/urandom) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 9 (/dev/null) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 10 (/dev/null) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 11 (/dev/null) leaked on vgchange invocation. Parent PID 21551: /bin/bash
  0 logical volume(s) in volume group "sailfish" now active
dd: invalid number `'
losetup: home.img: failed to set up loop device: No such file or directory
e2fsck 1.42.4 (12-June-2012)
/sbin/e2fsck: Invalid argument while trying to open /dev/loop1

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
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>

We got ourselves home size _ _
/usr/bin/expr: syntax error
File descriptor 4 (socket:[200877]) leaked on lvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 5 (/dev/null) leaked on lvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 7 (/dev/urandom) leaked on lvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 9 (/dev/null) leaked on lvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 10 (/dev/null) leaked on lvcreate invocation. Parent PID 21551: /bin/bash
File descriptor 11 (/dev/null) leaked on lvcreate invocation. Parent PID 21551: /bin/bash
  Invalid argument for --size: B
  Error during parsing of command line.
losetup: /dev/loop1: detach failed: No such device or address
File descriptor 4 (socket:[200877]) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 5 (/dev/null) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 7 (/dev/urandom) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 9 (/dev/null) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 10 (/dev/null) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 11 (/dev/null) leaked on vgchange invocation. Parent PID 21551: /bin/bash
  0 logical volume(s) in volume group "sailfish" now active
dd: invalid number `'
File descriptor 4 (socket:[200877]) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 5 (/dev/null) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 7 (/dev/urandom) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 9 (/dev/null) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 10 (/dev/null) leaked on vgchange invocation. Parent PID 21551: /bin/bash
File descriptor 11 (/dev/null) leaked on vgchange invocation. Parent PID 21551: /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, 1.4512e-05 s, 68.9 kB/s
e2fsck 1.42.4 (12-June-2012)
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 correct ext2
filesystem.  If the device is valid and it really contains an ext2
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>

resize2fs 1.42.4 (12-June-2012)
/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/loop1,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
umount: /home/mgh01/buildingpot/sfe-f5121-2.1.1.26/tmp.BRxQZ21595: not mounted
rmdir: /home/mgh01/buildingpot/sfe-f5121-2.1.1.26/tmp.BRxQZ21595: Directory not empty
e2fsck 1.42.4 (12-June-2012)
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 correct ext2
filesystem.  If the device is valid and it really contains an ext2
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>

resize2fs 1.42.4 (12-June-2012)
/sbin/resize2fs: Bad magic number in super-block while trying to open fimage.img
Couldn't find valid filesystem superblock.
/tmp/ks-script-m6lQYA: line 95: /usr/bin/img2simg: No such file or directory
/tmp/ks-script-m6lQYA: line 105: /usr/bin/img2simg: No such file or directory
mv: cannot stat `*.bin': No such file or directory
/home/mgh01/buildingpot
Info: The new image can be found here:
  /home/mgh01/buildingpot/sfe-f5121-2.1.1.26/Jolla-2.1.1.26-f5121-armv7hl.ks
  /home/mgh01/buildingpot/sfe-f5121-2.1.1.26/Jolla-2.1.1.26-f5121-armv7hl.ks
  /home/mgh01/buildingpot/sfe-f5121-2.1.1.26/Jolla-2.1.1.26-f5121-armv7hl.packages
  /home/mgh01/buildingpot/sfe-f5121-2.1.1.26/Jolla-2.1.1.26-f5121-armv7hl.urls
  /home/mgh01/buildingpot/sfe-f5121-2.1.1.26/SailfishOS-2.1.1.26-f5121-0.0.1+master.20170125170904.537a491.1.tar.bz2
  /home/mgh01/buildingpot/sfe-f5121-2.1.1.26/extracting-README.txt
  /home/mgh01/buildingpot/sfe-f5121-2.1.1.26/hw-release
  /home/mgh01/buildingpot/sfe-f5121-2.1.1.26/sailfish-release
  /home/mgh01/buildingpot/sfe-f5121-2.1.1.26/sfe-f5121-2.1.1.26.tar.bz2
  /home/mgh01/buildingpot/sfe-f5121-2.1.1.26/sfe-f5121-2.1.1.26.xml
  /home/mgh01/buildingpot/sfe-f5121-2.1.1.26/tmp.BRxQZ21595

Info: Finished.
Warning: Can't cleanup loop device /dev/loop12
Warning: Can't cleanup loop device /dev/loop11
Warning: Can't cleanup loop device /dev/loop10
PlatformSDK mgh01@mgh01-laptop:~/buildingpot$