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
Kaspersky Endpoint Security has to be stopped before running ReaR otherwise "ERROR: Unmounting '/tmp/rear.XXX/outputfs' failed." #2559
Comments
Umounting fails because
but I cannot know why it is still in use by something. Your
indicates that you may have your USB disk already mounted By the way: |
Thank you very much for your info (sorry i'm german an my english ist rusty) The lsblk output was made after rear has stopped. The only i did befor was to run rear format and there befor sdd was unmount. Anyway, i try to install latest version an run rear again. |
Additional Info: Kaspersky Endpoint Security 11 for LINUX has to be stopped befor running ReaR. |
@blackjack65 |
@blackjack65 How did you found this out? Any specifi error reported by Kaspersky EPS? |
First ReaR Version 2.6 was installed Probably Kaspersky interfere with ReaR, because Kaspersky runs the AntiCryptor task on the server. |
Another idea what could make a USB drive "in use" Each time I plug in a USB drive it gets used by some automatism that mounts it Unfortunately ;-) I want to use it for ReaR so I need to umount it |
ReaR version ("/usr/sbin/rear -V"): 2.4
OS version: Debian 10.7 buster
ReaR configuration files ("/etc/rear/local.conf"):
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
PC
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
X86
Prozessor Intel Xeon E-2224 / 3,4 GHz
RAM 1 x 16 GB (DDR4)
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
UEFI and GRUB2
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
???
Storage layout ("lsblk"):
Description of the issue (ideally so that others can reproduce it):
Aborting due to an error, check /var/log/rear/rear-xxx.log for details
Exiting rear mkbackup (PID 27631) and its descendant processes
Running exit tasks
Workaround, if any:
???
Attachments, as applicable ("end" of log file):
rear-xxx.log
xxx = (like) Server-33
/dev/sdd USB-Stick 500 GiB (Intenso)
The text was updated successfully, but these errors were encountered: