980_verify_rootfs.sh line 29¶

Labels: support / question, fixed / solved / done

cloudwitch opened issue at 2018-10-08 17:03:¶

ReaR version ("/usr/sbin/rear -V"):
Relax-and-Recover 2.3 / Git
Installed via apt.
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):

 ▲ /etc/rear lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:    18.04
Codename:   bionic

ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
http://paste.ubuntu.com/p/DcyqktwQNt/
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
BareMetal
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
x86_64
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
UEFI Grub
Storage (lokal disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
Local disk. Borg backs up over ssh. ISO would be sent to nfs mount had it gotten that far.
Description of the issue (ideally so that others can reproduce it):
Getting the following error when running rear -dD mkrescue -vvv. Unable to build recovery iso.

ERROR:
====================
BUG in /usr/share/rear/build/default/980_verify_rootfs.sh line 29:
'ReaR recovery system in '/tmp/rear.T4aINC89mSqvt9o/rootfs' is broken: 'ldd /bin/bash' failed'

Work-around, if any:
log:
http://paste.ubuntu.com/p/Pz6RhYrYcB/

Not sure if it helps, but, ldd is at /usr/bin/ldd not, `/bin/ldd'.

 ▲ /etc/rear which ldd                                                                                                                                                                                                                   50s
/usr/bin/ldd

gozora commented at 2018-10-08 17:25:¶

I see some similarities with https://github.com/rear/rear/issues/1689. Especially with @jsmeix https://github.com/rear/rear/issues/1689#issuecomment-356949870.
Your ubuntu pastebin indicates that there is much more in your config as it should be.

Can you try to reduce it to bare minimum e.g.

# Borg
OUTPUT=ISO
OUTPUT_URL=nfs://lilguy.fionabuckner.xyz/redpool

BACKUP=BORG
BORGBACKUP_HOST="lilguy.fionabuckner.xyz"
BORGBACKUP_USERNAME="backup"
BORGBACKUP_REPO="/redpool/borg/r510"
BORGBACKUP_REMOTE_PATH="/usr/bin/borg"

# Automatic archive pruning
# (https://borgbackup.readthedocs.io/en/stable/usage.html#borg-prune)
BORGBACKUP_PRUNE_WEEKLY=2

# Archive compression
# (https://borgbackup.readthedocs.io/en/stable/usage.html#borg-create)
BORGBACKUP_COMPRESSION="lzma,9"     # Slowest backup, best compression

# Repository encryption
# (https://borgbackup.readthedocs.io/en/stable/usage.html#borg-init)
#BORGBACKUP_ENC_TYPE="keyfile"
#export BORG_PASSPHRASE="S3cr37_P455w0rD"
#COPY_AS_IS_BORG=( "/root/.config/borg/keys/" )

# Borg environment variables
# (https://borgbackup.readthedocs.io/en/stable/usage.html#environment-variables)
export BORG_RELOCATED_REPO_ACCESS_IS_OK="yes"
export BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK="yes"

And try again ?

V.

cloudwitch commented at 2018-10-08 17:32:¶

That worked, thank you!

jsmeix commented at 2018-10-09 07:40:¶

@pheonix991
can you explain to us how it happened that you have
the whole usr/share/rear/conf/default.conf
as your /etc/rear/local.conf
because
you are the second Ubuntu user who has that issue
(cf. https://github.com/rear/rear/issues/1689)
and I would like to understand if there is perhaps something
unexpected happening on Ubuntu that leads to such issues
(I do not use ReaR on Ubuntu because am not a Ubuntu user).

jsmeix commented at 2018-10-09 07:46:¶

@gozora
thank you for your awesome fast solution !

[Export of Github issue for rear/rear.]