There exist three types of messages:

1) Informational  - Messagenumber ends with I

2) Warning - Messagenumber ends with W

3) Error - Messagenumber ends with E

Most errormessages of raspiBackup give detailed information about the root cause. Sometimes it's required to get additional information in order to get rid of them. raspiBackup has abou 200 errormessages and it's soo boring to explain all of them here. If you miss a message just add list the message text in a comment at the end of the page and the message with mor detailed explanations will be addded on this page. That way the most common raspiBackup messages will show up on this page.

 
Backup failed. Check previous error messages for details.

Root cause:

raspiBackup ends with an error and didn't create a backup

Suggested actions:

There should be another error message preceding this message. Lookup this message and fix the root cause.

 

RBK0019E: Missing option -a and -o.

raspiBackup allows to backup a running system. Before saving the system important services should be stopped and started afterwards to make sure the backup is consistent.

Suggested actions:

Use both options to define the services to stop and start. See details on FAQ page.

 

RBK0021E: Backupprogram for type %1 failed with RC %2.

Root cause:

dd, tar or rsync used to create a backup terminated with an error. RC is the return code of the backup program.

Suggested actions:

Leading messages should point to the root cause of the error. If this doesn't help use option -v with tar or rsync to get detailed informations from the backup program. Then pass the error messages into your favorit search engine to find the root cause. See the FAQ page where a lot of error messages and their root cause is explained.

You can also ignore errors from tar and rsync. See FAQ32.

 

RBK0027E: No external device mounted on %1. SD card would be used for backup.

Root cause:

raspiBackup checks whether there is an external backup partition mounted on the backup path. Otherwise the backup would be stored on the SD card which doesn't make sense and if the SD card is small it will be blown up.

Suggested actions:

Let's assume %1 is /backup which is the default backup path. You should mount either your local your backup partition which resides on an USB stick or -disk or a remote backup partition on /backup. Use /etc/fstab to define the mount point /backup. Check with

findmnt /backup

until the remote partition is mounted.

 

RBK0105I: Deleting new backup directory %1.

Root cause:

raspiBackup failed with an error and deletes the empty or inconsistent backup directory.

Suggested actions:

Fix the root cause why raspiBackup failed.

 

RBK0154E: Restore is not possible when a partition of device %1 is mounted.

Root cause:

A partition must be not mounted when it's written to.

Suggested actions:

Use command sudo mount | grep <device> (<device> is mentioned in the message) to find the mounted partition and use sudo umount <partition> where <partition> should be the partition name, e.g. /dev/sda1 to umount the partition.

 

RBK0160E: Target %1 with %2 is smaller than backup source with %3.

Root cause:

The dd backup is larger than the SD card used for restore and therefore it's impossible to restore the image. This message is written only for a dd backup. A tar or rsync restore will adjust the size accordingly.

Suggested actions:

Used a larger SD card for restore. You also can use pishrink to shrink the dd image first and then restore it with raspiBackup. See also FAQ26.

 

RBK0193W: No hardlinks supported on %1.

Root cause:

rsync will use hardlinks in order to reduce backup time and backup space. Hardlinks are supported by ext3/ext4 filesystems mounted locally or via nfs. Samba and sshfs doesn't support hardlinks.

Suggested actions:

Either use a backup partition which supports hardlinks to get the benefits of hardlinks or just ignore the message. But keep in mind every backup will be a full backup which requires much more space and time.