Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ROOTFS_DIR '/tmp/rear..' is broken, chroot bash test failed #29

Closed
dagwieers opened this issue Mar 28, 2012 · 11 comments
Closed

ROOTFS_DIR '/tmp/rear..' is broken, chroot bash test failed #29

dagwieers opened this issue Mar 28, 2012 · 11 comments

Comments

@dagwieers
Copy link
Contributor

Reported by sid23 as SF#3431201 on 2011-10-31 06:22:17 PDT

Original report

Linux rl01 3.0.0-12-server #20-Ubuntu SMP Fri Oct 7 16:36:30 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

ReaR V1.11.0 in a VM with Ubuntu 11.10 (Supervisor is Ubuntu 11.04 and KVM)

ERROR: BUG BUG BUG! ROOTFS_DIR '/tmp/rear.FZOsVVBdbPLqMth/rootfs' is broken, chroot bash test failed. 
Please report this as a bug to the authors of Relax & Recover

local.conf:

# Create ReaR rescue media as ISO image
OUTPUT=ISO

# optionally define (non-default) backup software, e.g. TSM, NBU, DP, BACULA
BACKUP=NETFS
NETFS_URL=nfs://192.168.1.99/share/local
#NETFS_OPTIONS=credentials=/etc/rear/user.credentials
@ghost ghost assigned schlomo Mar 28, 2012
@dagwieers
Copy link
Contributor Author

More information about this issue is in the original report at SF#3431201

@dagwieers
Copy link
Contributor Author

We are waiting for feedback from the original reporter in order to get this ball rolling again...

@schlomo: Is there a possibility to get in contact with the reporter using private email ?

@schlomo
Copy link
Member

schlomo commented Apr 6, 2012

I just went over the SF bug again. I would say close it and wait if it pops up again. I hope that we will have some Ubuntu 64bit as part of our regular test setup. Who knows, maybe he upgraded his system from something older and that caused his /lib dirs to be different.

Also, I think that now we have even smarter /lib cloning code so maybe it already fixed it for this user.

(I don't know this user and don't have private contact)

@dagwieers
Copy link
Contributor Author

Alright, closing this issue because we lack feedback about a recent and relevant release. If this is still an issue, please re-open this issue.

@jpeschke
Copy link

Hi, I ran into the same issue:

root@icinga:~/rear/manual/rear-1.13.0# rear mkbackup
ERROR: BUG BUG BUG!  ROOTFS_DIR '/tmp/rear.6xGZWDET8u49JGS/rootfs' is broken, chroot
        Please report this as a bug to the authors of Relax and Recover
Aborting due to an error, check /tmp/rear-icinga.log for details
Finished in 9 seconds
You should also rm -Rf /tmp/rear.6xGZWDET8u49JGS
Terminated

I ran into this error with Debian/Ubuntu Package from opensuse build service with Version 1.12 and tried the newer 1.13 Release as tar.gz (purged any debian package before). My local.conf:

OUTPUT=ISO
MODULES_LOAD=( vmxnet )
ISO_DIR=/localbackup/sysrescue
BACKUP=EXTERNAL
COPY_AS_IS=(${COPY_AS_IS[@]} /usr/local/sbin/restore_localhost.sh)
EXTERNAL_BACKUP="/usr/local/sbin/backup_localhost.sh"
EXTERNAL_RESTORE="/usr/local/sbin/restore_localhost.sh

running on system: Ubuntu 11.10

The bug did'nt show up on rear version 1.10 I used before; but this version didn't allow me to restore the system (as stated in some other bugreport) so I tried to upgrade.
A manual chroot to reproduce the behaviour also failed:

root@icinga:~# chroot /tmp/rear.2SahWSVBl6Oualf/rootfs/
chroot: failed to run command `/bin/bash': No such file or director

where /tmp/rear.2SahWSVBl6Oualf/rootfs/bin/bash is existing and executable

I tried also to chroot into a rear-rootfs I copied from a debian system to the ubuntu-box, that worked for fine me.

Kind regards
Jan

@jpeschke
Copy link

Hi,
played around a bit and got it working through copying some more libs explicitly into the rescue image. I extended my local.conf the following way:

COPY_AS_IS=(${COPY_AS_IS[@]} /usr/local/sbin/restore_localhost.sh /lib/x86_64-linux-gnu/*

I assume there is a cleaner way to include this into rear (maybe some rule especially for Ubuntu 11.10 so that rear works out of the box.

reagards

Jan

@dagwieers dagwieers reopened this Jun 11, 2012
@dagwieers
Copy link
Contributor Author

@jpeschke What version did you try ? We made an important change in the master branch that should have fixed the issue you see. And so we would like to know if that effectively fixes your issue as well. I would appreciate if you could test the version in the master branch. This is also the first release that can be used without requiring to install it, so you can simply do a git clone and then run ./usr/sbin/rear.

@jpeschke
Copy link

I tried this version https://github.com/downloads/rear/rear/rear-1.13.0.tar.gz
and the debian package from here
http://download.opensuse.org/repositories/home:/sschapiro/xUbuntu_11.10/all/rear_1.12.0-1_all.deb
Actually not the masterbranch, maybe I'll find the time to test it.

@dagwieers
Copy link
Contributor Author

The expected fix for your issue was part of issue #36. (c1ef532)

@jpeschke
Copy link

I can confirm, that the masterbranch fixed any issue I had with stable versions on Ubuntu 11.10; thanks a lot.

@jhoekx
Copy link
Contributor

jhoekx commented Jun 18, 2012

Ok, good to hear!

Closing this again.

@jhoekx jhoekx closed this as completed Jun 18, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants