SBLive creation fails during write

Asked by David on 2018-12-30

Hi

I have a 4.3GB Sblive which I have been trying to create a bootable usb from. When I try to create using Systemback Live System Create, the write to the usb fails around 17% thru with the following error message "Live Write aborted. An error occurred while unpacking the Live System files". Tried it several times and its consistent and always in the same spot.
Anyone seen this and resolved it ?

Regards and Happy Xmas

David

Question information

Language:
English Edit question
Status:
Solved
For:
Systemback Edit question
Assignee:
No assignee Edit question
Solved by:
David
Solved:
2019-01-02
Last query:
2019-01-02
Last reply:
2018-12-30
Kendek (nemh) said : #1

This is a general error message, for more information, please try again from terminal with a higher debug option. The command is:

DBGLEV=3 systemback-sustart

and when the problem is occurred, just check the terminal output.

David (d-billingham) said : #2

terminal output below

Systemback

 Version: 1.8.402_05.16.2016_Qt5.5.1_GCC5.3.1_i386
 Compilation date and time: May 16 2016 11:16:01
 Installed files: /etc/xdg/autostart/sbschedule-kde.desktop
                  /etc/xdg/autostart/sbschedule.desktop
                  /usr/bin/systemback
                  /usr/bin/systemback-cli
                  /usr/bin/systemback-sustart
                  /usr/lib/systemback/libsystemback.so
                  /usr/lib/systemback/libsystemback.so.1
                  /usr/lib/systemback/libsystemback.so.1.0
                  /usr/lib/systemback/libsystemback.so.1.0.0
                  /usr/lib/systemback/sbscheduler
                  /usr/lib/systemback/sbsustart
                  /usr/lib/systemback/sbsysupgrade
                  /usr/share/applications/systemback-kde.desktop
                  /usr/share/applications/systemback.desktop
                  /usr/share/systemback/lang/systemback_ar_EG.qm
                  /usr/share/systemback/lang/systemback_ca_ES.qm
                  /usr/share/systemback/lang/systemback_cs.qm
                  /usr/share/systemback/lang/systemback_da_DK.qm
                  /usr/share/systemback/lang/systemback_de.qm
                  /usr/share/systemback/lang/systemback_en_GB.qm
                  /usr/share/systemback/lang/systemback_es.qm
                  /usr/share/systemback/lang/systemback_fi.qm
                  /usr/share/systemback/lang/systemback_fr.qm
                  /usr/share/systemback/lang/systemback_gl_ES.qm
                  /usr/share/systemback/lang/systemback_hu.qm
                  /usr/share/systemback/lang/systemback_id.qm
                  /usr/share/systemback/lang/systemback_pt_BR.qm
                  /usr/share/systemback/lang/systemback_ro.qm
                  /usr/share/systemback/lang/systemback_ru.qm
                  /usr/share/systemback/lang/systemback_tr.qm
                  /usr/share/systemback/lang/systemback_uk.qm
                  /usr/share/systemback/lang/systemback_zh_CN.qm
 Operating system: Ubuntu 16.04.5 LTS
 Mounted filesystems: /dev/sda4 / ext4 rw,relatime,errors=remount-ro,data=order
                      ed 0 0
                      /dev/sdb1 /media/david/SBLIVE vfat rw,nosuid,nodev,relati
                      me,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,i
                      ocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,er
                      rors=remount-ro 0 0
                      /dev/sdb2 /media/david/SBROOT ext2 rw,nosuid,nodev,relati
                      me,block_validity,barrier,user_xattr,acl 0 0
 System language: en_GB
 Translation: auto

mke2fs 1.42.13 (17-May-2015)
/dev/sdb2 contains a ext2 file system labelled 'SBROOT'
 last mounted on /.sblivesystemwrite/sbroot on Sun Dec 30 15:37:22 2018
Creating filesystem with 15167744 4k blocks and 3792896 inodes
Filesystem UUID: 8ed791de-27f7-4452-b45d-9101f90d5788
Superblock backups stored on blocks:
 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
 4096000, 7962624, 11239424

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

mkfs.fat 3.0.28 (2015-05-16)
1+0 records in
1+0 records out
440 bytes copied, 0.0137708 s, 32.0 kB/s

 An error occurred while executing the following command:

  tar -xf "/home"/systemback_live_2018-12-02.sblive -C
 /.sblivesystemwrite/sbroot --exclude=.disk --exclude=boot --exclude=EFI --exclude=syslinux --exclude=casper/initrd.gz --exclude=casper/vmlinuz --exclude=live/initrd.gz --exclude=live/vmlinuz --no-same-owner --no-same-permissions

 Exit code: 2

Kendek (nemh) said : #3

So the tar process is exited with a code 2. Unfortunately, this is not an exact error, just a general one. See the tar manual:

https://www.gnu.org/software/tar/manual/html_section/tar_19.html#Synopsis

But definitely a decompression issue, maybe the .sblive file is corrupt or something.

David (d-billingham) said : #4

Hmmm. Just created another sblive file - this time 4.4GB in size. It fails in exactly the same way (and the same place 17%) as the one above.
I also tried an old sblive file (just 2.2GB) on my system, and that one was written successfully to the usb drive. Can't really understand what's going on here but I'm currently unable to create a bootable sblive usb. Anyone got any relevant experience or solutions ?

Thanks

David

Extract from more recent log failing log file:

mke2fs 1.42.13 (17-May-2015)
Creating filesystem with 15167744 4k blocks and 3792896 inodes
Filesystem UUID: 467d72d7-df21-4378-8edc-d33eca4065ed
Superblock backups stored on blocks:
 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
 4096000, 7962624, 11239424

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

mkfs.fat 3.0.28 (2015-05-16)
1+0 records in
1+0 records out
440 bytes copied, 0.0285211 s, 15.4 kB/s

 An error occurred while executing the following command:

  tar -xf "/home"/sblive_2018_12_30.sblive -C /.sblivesystemwrite/sbroot
 --exclude=.disk --exclude=boot --exclude=EFI --exclude=syslinux --exclude=casper/initrd.gz --exclude=casper/vmlinuz --exclude=live/initrd.gz --exclude=live/vmlinuz --no-same-owner --no-same-permissions

 Exit code: 2

Kendek (nemh) said : #5

The difference is that if the .sblive size is less than 4 GB, then the Systemback is creating only one, FAT32 partition on the USB device. But if greater, then there is an ext2 too for the big filesystem image. This is the 'sbroot' directory, and after the files are unpacked on the FAT32 partition, the other tar process is failing with the 'filesystem.squashfs' file. But unfortunately I am not sure why.

David (d-billingham) said : #6

Unfortunately this means that I can no longer rely on Systemback as a backup/restore solution. So have installed another solution. Pity really, been using SB for 7 years. All good things come to an end

Kendek (nemh) said : #7

Yes, but please note that the development of the Systemback is over. So I tried to solve your problem, but the thing is, eventually you need to find another solution.

David (d-billingham) said : #8

Kendek

Many thanks for what was a great, almost magical bit of software. Can’t quite believe that it’s all over for me. Will miss it’s simplicity and it’s sheer brilliance

Take care

David