Booted into the USB, Can't Recover

[gaia]

• 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
  

• Workaround: ?

[gozora]

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

V.

[gozora]

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

V.

[gaia]

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)

[gozora]

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]

sorry, what is missing from the template?

[gaia]

it is missing from the rescue disk

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

[gozora]

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]

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