#2193 Issue closed: Booted into the USB, Can't Recover

Labels: support / question, fixed / solved / done

gaia opened issue at 2019-07-22 06:48:

  • Relax-and-Recover 2.4 / Git (installed via apt)

  • Debian 10

  • BareMetal

  • x86_64

  • UEFI + GRUB

  • Root on mdadm, NVME disk attached, rear on USB flash drive:

  • Booted into the USB disk, ran rear recover, got
    image

  • Workaround: ?

gozora commented at 2019-07-22 06:56:

Can it be, that /usr/share/rear is symlink somewhere, on your original system?

V.

gozora commented at 2019-07-22 06:59:

Sorry for accidental close of this issue. Missclicked on phone :-)

V.

gaia commented at 2019-07-22 07:06:

Can it be, that /usr/share/rear is symlink somewhere, on your original system?

V.

It is not (borg is /usr/sbin/borg -> /path/to/borg-linux64)

image

gozora commented at 2019-07-22 07:41:

At the first sight, it looks like you are missing /usr/share/rear directory in you ReaR recovery system, but based on provided data I can't tell why.
@gaia maybe try to correctly fill ReaR issue template and someone might have an idea what is wrong...

V.

gaia commented at 2019-07-22 15:35:

sorry, what is missing from the template?

gaia commented at 2019-07-22 16:58:

it is missing from the rescue disk

image

is there a variable that needs to be set correctly for it to be included? IMHO it should be included no matter what

gozora commented at 2019-07-22 17:24:

sorry, what is missing from the template?
For me the most important pieces ...

  • ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf")
  • Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):

is there a variable that needs to be set correctly for it to be included? IMHO it should be included no matter what

Normally /usr/share/rear/ is included by COPY_AS_IS in default.conf
Since I've already removed your local.conf from previous issue, and you did not provided any for this issue, I'll do again a blind guess ...
Is there a chance that you've somehow set/reset COPY_AS_IS variable in your local.conf/site.conf ?

V.

gaia commented at 2019-07-22 19:27:

it works now, you guessed right, again. gracias!

[Export of Github issue for rear/rear.]