#154 Issue `closed`: WARNING! There was an error (Nr. 141) during archive creation.¶

Labels: support / question

cwnam14 opened issue at 2012-09-05 06:36:¶

I've got following error, when I run the backup. Pls help me out.

[root@STM-Secondary rear]# rear -v mkbackup
Relax and Recover 1.13.0 / 2012-04-17
Creating disk layout
Creating root FS layout
WARNING: To login as root via ssh you need to setup an authorized_keys file in /root/.ssh
Copy files and directories
Copy binaries and libraries
Copying kernel modules
Checking udev
Create initramfs
Copying resulting files to usb location
Creating tar archive '/tmp/rear.UtaUpLgdeR30965/outputfs/STM-Secondary/backup.tar.gz'
Preparing archive operationOK
WARNING !
There was an error (Nr. 141) during archive creation.
Please check the archive and see '/tmp/rear-STM-Secondary.log' for more information.

Since errors are oftenly related to files that cannot be saved by
tar, we will continue the mkbackup process. However, you MUST
verify the backup yourself before trusting it !


Finished in 30 seconds

This error log

2012-09-05 15:28:58 Creating tar archive '/tmp/rear.UtaUpLgdeR30965/outputfs/STM-Secondary/backup.tar.gz'
2012-09-05 15:28:58 tar --sparse --block-number --totals --verbose --no-wildcards-match-slash --one-file-system --ignore-failed-read --gzip -X /tmp/rear.UtaUpLgdeR30965/tmp/backup-exclude.txt -C / -c -f /tmp/rear.UtaUpLgdeR30965/outputfs/STM-Secondary/backup.tar.gz / /boot /tmp/rear-STM-Secondary.log
tar: /tmp/rear.UtaUpLgdeR30965/outputfs/STM-Secondary/backup.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: Removing leading `/' from member names
2012-09-05 15:29:01 WARNING !
There was an error (Nr. 141) during archive creation.
Please check the archive and see '/tmp/rear-STM-Secondary.log' for more information.

Since errors are oftenly related to files that cannot be saved by
tar, we will continue the mkbackup process. However, you MUST
verify the backup yourself before trusting it !

gdha commented at 2012-09-05 06:59:¶

Can you share the /etc/rear/local.conf file please?

On Wed, Sep 5, 2012 at 8:36 AM, cwnam14 notifications@github.com wrote:

I've got following error, when I run the backup. Pls help me out.

[root@STM-Secondary rear]# rear -v mkbackup
Relax and Recover 1.13.0 / 2012-04-17
Copying resulting files to usb location
Creating tar archive '/tmp/rear.UtaUpLgdeR30965/outputfs/STM-Secondary/backup.tar.gz'
Preparing archive operationOK

Seems to be an USB disk somehow. Did you implement any special security
rule for the USB disk (SElinux)?

cwnam14 commented at 2012-09-05 07:01:¶

Here we go;

# sample local configuration

# Create Rear rescue media as ISO image
# OUTPUT=ISO

BACKUP=NETFS
OUTPUT=USB
#BACKUP_URL="usb:///dev/sdb1"
BACKUP_URL="usb:///dev/disk/by-label/REAR-000"


KERNEL_CMDLINE="console=tty0 console=ttyS1"

dagwieers commented at 2012-09-05 07:17:¶

I noticed this is a relative old release. We have improved the handling of tar in the meantime due to an issue you reported before (#119). Is there a reason why you insist on using this older release ?

cwnam14 commented at 2012-09-05 07:19:¶

No, I don't have any reason to use the old one. But I downloaded it from ReaR website.
Please let me know how to get the new one.

dagwieers commented at 2012-09-05 07:24:¶

Try: http://relax-and-recover.org/download/ and use the latest snapshot release !

cwnam14 commented at 2012-09-05 08:10:¶

As I know, when I recover the os, I have to clean up boot area using dd command.
Can I have any way to skip this procedure?

dagwieers commented at 2012-09-05 09:57:¶

I do not understand what you are talking about. What do you mean with boot area ? And why should you clean it up ?

gdha commented at 2012-09-05 12:08:¶

I assume @cwnam14 means the MBR area:

./layout/prepare/GNU/Linux/10_include_partition_code.sh
dd if=/dev/zero of=$disk bs=512 count=1

cwnam14 commented at 2012-09-05 12:20:¶

That's right.

cwnam14 commented at 2012-09-05 12:24:¶

I,d like to skip this procedure.

dagwieers commented at 2012-09-05 13:18:¶

Why do you have to clean up the MBR ? It should not be necessary to manually use dd on the MBR.

Please show us what you are doing and explain why you are doing this, I do not want to make assumptions in order to help you. In fact, I prefer to do other things rather than help you if you insist on making it hard for me to grasp what you need help with. Sigh...

@gdha Feel free to handle this issue if you can see through the vagueness.

gdha commented at 2012-10-12 12:06:¶

Is this issue still open? If yes, run once rear dump to view your current setup and paste it here. As @dagwieers already mentioned there is no need to run manually a MBR.
By the way, did you format the USB disk before running rear -v mkbackup ?

cwnam14 commented at 2012-10-15 04:36:¶

Let me close this issue. Thanks.

[Export of Github issue for rear/rear.]

#154 Issue closed: WARNING! There was an error (Nr. 141) during archive creation.¶