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
OUTPUT=USB: REAL_USB_DEVICE mounted both below /tmp/rear... and /var/tmp/rear... #2924
Comments
Dear @frilogg, please install ReaR version 2.7, e.g. from http://download.opensuse.org/repositories/Archiving:/Backup:/Rear/RHEL_7/ and try again In the rescue system you'll have to type |
Hi @schlomo , thank you for feedback, but .. had hoped to figure it out with this version. I have used rear for many of my customers, and some of the problem is that they "only" want to use the version that is with the official redhat repo. I also noticed that with redhat 9.1 version 2.6 is default also.. So for this cause no good quick tips or you notice anything from the logs provided ? |
Well, line 11 of your log says:
(don't understand why you would export something in a ReaR config anyway as everything is one large shell script) Besides that you didn't provide anything about the actual problem which is during recovery, right? |
Hi and good morning @schlomo , this was corrected but I still had the problem. I followed your advice and installed Rear 2.7., so thats the version Im on now.
|
The reason we want to export and use another tmpdir or else it would not be enough space on device. I ran now export TMPDIR=/home/rear - and now the backup is created. In rear 2.4 we could have this string in the local.conf but it seems that its not working anymore?! |
I have now the same problem as #2920 |
Sorry @frilogg, we need to somewhat change the mode of our conversation here:
With the information you shared I don't even know what to look at. If you do this for a customer then maybe a commercial support option might be better suited for you where one of us will join you in a remote screen sharing session to look at your situation. About your
As it is exported there you don't need to (and shouldn't) export it again |
@frilogg Concerning your customers who want to use the official rear version delivered with their disribution - they have the right to submit an incident at RH and RH support will pick it up and try to help them or provide a fix (which will be merged in our master repo). RH and Suse are activily committing enhancemants and bug fixes in our ReaR master repo. |
Thank you for quick feedback, and sorry for late response from my side. |
Only as a side note FYI Sigh! |
@frilogg Your
because it ends with
where it still errors out with
as in your |
@frilogg
so it seems some 'umount' is somehow somewhere missing |
Now I see it:
versus
i.e. |
@frilogg
and run "rear -D mkbackup" again and |
@jsmeix this error was gone when I exported the TMPDIR, so the backup ran. When I did not have this I could not make a complete backup at all. And it is this backup that I am trying to restore. You still want me to add this?
|
@frilogg To get a clean state without possibly broken First redo "rear -D format" for your USB disk Then run "rear -D mkbackup" again and also Then try to boot this new ReaR recovery system Provided this works you can try to recreate your system When you run "rear recover" on some hardware or VM |
Hi @jsmeix , I have now created the usb again with But I still get the same error when running
|
Done some more research and with a help from a colleague we made following changes to
This made the script go pass the error
The backup starting to create but stops and "freeze" when trying to finish.
Any suggestion to this error when its freezing? |
@frilogg |
I have now got it to work but I had to do the following
Its working for now, but if I get the time I will try doing more research but the workaround in the 350 script worked. |
@frilogg I will have a look when time permits. |
Stale issue message |
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
ReaR version ("/usr/sbin/rear -V"):
Relax-and-Recover 2.4.16 / Git
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
NAME="Red Hat Enterprise Linux Server"
VERSION="7.9 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.9"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.9 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.9:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
OUTPUT=USB
BACKUP=NETFS
BACKUP_URL="usb:///dev/disk/by-label/REAR-000"
BACKUP_PROG_EXCLUDE=('/home/rear' '/var/log/audit')
USB_UEFI_PART_SIZE="1648"
HOSTNAME="sp7-ui"
USB_DEVICE_FILESYSTEM="ext4"
export TMPDIR="/home/rear"
Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
PC Dell Precision 3450
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
uname -a
Linux solx8ht 3.10.0-1160.66.1.el7.x86_64 #1 SMP Wed Apr 27 20:34:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
Grub2
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):
Description of the issue (ideally so that others can reproduce it):
We cant restore backup. After "enter" on relax and recover option it doesnt "fire up" loading files.
Workaround, if any:
Haven't found any
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
rear-solx8ht.log
The text was updated successfully, but these errors were encountered: