I: Syncing back the patched tree I: Repacking /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25/patcher-tmp/work /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25 0+0 records in 0+0 records out 0 bytes copied, 0.000164125 s, 0.0 kB/s Physical volume "/dev/loop0" successfully created. Volume group "sailfish" successfully created e2fsck 1.43.4 (31-Jan-2017) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/loop1: 25063/116640 files (0.1% non-contiguous), 264442/466176 blocks We got ourselves root blocks _ 398289 _ after maths size _ 1631391744 _ Rounding up size to full physical extent 1.52 GiB Logical volume "root" created. 1 logical volume(s) in volume group "sailfish" now active 398289+0 records in 398289+0 records out 1631391744 bytes (1.6 GB, 1.5 GiB) copied, 7.78859 s, 209 MB/s e2fsck 1.43.4 (31-Jan-2017) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information home: 83/7328 files (3.6% non-contiguous), 13285/16198 blocks We got ourselves home size _ 13290 _ Rounding up size to full physical extent 52.00 MiB Logical volume "home" created. 2 logical volume(s) in volume group "sailfish" now active 13290+0 records in 13290+0 records out 54435840 bytes (54 MB, 52 MiB) copied, 0.163591 s, 333 MB/s 0 logical volume(s) in volume group "sailfish" now active 1+0 records in 1+0 records out 1 byte copied, 0.00015447 s, 6.5 kB/s Usage: mkfs.ext4 [-c|-l filename] [-b block-size] [-C cluster-size] [-i bytes-per-inode] [-I inode-size] [-J journal-options] [-G flex-group-size] [-N number-of-inodes] [-d root-directory] [-m reserved-blocks-percentage] [-o creator-os] [-g blocks-per-group] [-L volume-label] [-M last-mounted-directory] [-O feature[,...]] [-r fs-revision] [-E extended-option[,...]] [-t fs-type] [-T usage-type ] [-U UUID] [-e errors_behavior][-z undo_file] [-jnqvDFSV] device [blocks-count] e2fsck 1.43.4 (31-Jan-2017) ext2fs_open2: Bad magic number in super-block e2fsck: Superblock invalid, trying backup blocks... 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.4 (31-Jan-2017) resize2fs: Bad magic number in super-block while trying to open fimage.img Couldn't find valid filesystem superblock. 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: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25/patcher-tmp/work/tmp.Y3VaMPjpIX: not mounted rmdir: failed to remove '/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25/patcher-tmp/work/tmp.Y3VaMPjpIX': Directory not empty e2fsck 1.43.4 (31-Jan-2017) ext2fs_open2: Bad magic number in super-block e2fsck: Superblock invalid, trying backup blocks... 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.4 (31-Jan-2017) resize2fs: Bad magic number in super-block while trying to open fimage.img Couldn't find valid filesystem superblock.