Live System Create Write to USB Drive Fails

Please try to start the Systemback with the following command:

DBGLEV=3 systemback-sustart

After the error, show me the terminal output (use paste.ubuntu.com).

Thanks for getting back. Exit Code 2, not much help...

SBROOT is empy this time - no file at all.

mke2fs 1.42.9 (4-Feb-2014)
Filesystem label=SBROOT
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1978592 inodes, 7910143 blocks
395507 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
242 block groups
32768 blocks per group, 32768 fragments per group
8176 inodes per group
Superblock backups stored on blocks:
         32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208,
         4096000

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

mkfs.fat 3.0.26 (2014-03-07)
1+0 records in
1+0 records out
440 bytes (440 B) copied, 0.0090847 s, 48.4 kB/s

  An error occurred while executing the following command:

   tar -xf "/home"/systemback_live_2016-09-25.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

On 09/27/2016 11:57 AM, Kendek wrote:
> Your question #402341 on Systemback changed:
> https://answers.launchpad.net/systemback/+question/402341
>
> Status: Open => Needs information
>
> Kendek requested more information:
> Please try to start the Systemback with the following command:
>
> DBGLEV=3 systemback-sustart
>
> After the error, show me the terminal output (use paste.ubuntu.com).
>

Yeah, the exit code 2 is belongs to tar. Fatal error has happened, this means that some fatal, unrecoverable error occurred. Unfortunately, it really doesn't help too much...

Kendek,

I used KDE Partition Mgr and did a repair on the SBROOT. Then I tried a
manual copy:

sudo tar -xf /home/systemback_live_2016-09-25.sblive -C
/media/greg/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

tar: ./casper/filesystem.squashfs: Wrote only 5632 of 10240 bytes
tar: Exiting with failure status due to previous errors

/casper folder on SBROOT is blank

This ran for 47 minutes writing to the USB Drive

I have a SanDisk 32Gb drive coming, I'll try that when it arrives. Both
of these generic drive are failing.

On 09/28/2016 10:02 AM, Kendek wrote:
> Your question #402341 on Systemback changed:
> https://answers.launchpad.net/systemback/+question/402341
>
> Kendek posted a new comment:
> Yeah, the exit code 2 is belongs to tar. Fatal error has happened, this
> means that some fatal, unrecoverable error occurred. Unfortunately, it
> really doesn't help too much...
>

Problem was the two USB 2.0 32Gb Drives I was using. I tried a new
Sandisk Cruz 32Gb and Write took about an hour (others that failed took
over 2 hrs) and completed no errors.

Thanks, we are good and thanks for your time to create such a nice
interface for backup.

On 09/28/2016 10:02 AM, Kendek wrote:
> Your question #402341 on Systemback changed:
> https://answers.launchpad.net/systemback/+question/402341
>
> Kendek posted a new comment:
> Yeah, the exit code 2 is belongs to tar. Fatal error has happened, this
> means that some fatal, unrecoverable error occurred. Unfortunately, it
> really doesn't help too much...
>

This question was expired because it remained in the 'Open' state without activity for the last 15 days.