1-800-691-1991 | 9am - 8pm ET
EN

Veeam Recovery Media for Linux OS, Workarounds

KB ID: 4183
Product: Veeam Agent for Linux 5.0
Published: 2021-06-17
Last Modified: 2021-08-09
This article documents rare issues that may be experienced when using the Veeam Recovery Media for Linux OSs and workarounds for them.

Veeam Recovery Media fails to boot with USB flash drive created with third-party ISO flashing software.

Challenge

A Linux machine cannot boot the Veeam Recovery Media from a USB flash drive created using a third-party tool to image the ISO onto the USB flash drive. 

 

Cause

Third-party ISO-to-USB imaging software may alter the way the image boots when writing the ISO contents to the flash drive.

 

Workaround

Write the ISO image to the USB flash drive using the dd command-line program.

Example:

sudo dd bs=4M if=/path/to/veeam-recovery-amd64-5.0.0.iso of=/dev/sdx status=progress oflag=sync
The if and of parameters in the command above will need to be adjusted for the environment.

Some hardware is not recognized in the Veeam Recovery Media

Challenge

  • Hardware is not recognized in the Veeam Recovery Media environment. 
  • Using Custom Veeam Recovery Media also fails to recognize the hardware.

Workaround

  1. Create and boot into a Live CD of the Linux distro that is compatible with the hardware.
  2. Install Veeam Agent for Linux inside this Live CD environment. 
    Note: The veeamsnap kernel module is not required for restores, so you can break the veeamsnap dependency to avoid installing kernel-headers.
  3. Enable recovery UI by adding the following line to /etc/veeam/veeam.ini 

    [recoveryui]
    enableOnLiveSystem = 1


  4. Open Recovery UI using the command:

    veeamconfig recoveryui

 

Patched Custom Veeam Recovery ISO does not start veeamservice on boot

Challenge

When booting from a recovery media image patched on specific Linux kernels, veeamservice does not start correctly. As a result, the recovery UI is inaccessible. The following output is displayed instead:

Linux veeam-recovery-iso 4.18.0-240.22.1.e18_3.x86_64 #1 SMP Thu Mar 25 14:36:04 EDT 2021 X86_64
Welcome to Veeam Agent for Linux Recovery Media.
To open Veeam Recovery UI execute 'sudo veeam'.
No such file or directory
Failed to connect: /var/tmp/veeam/socket/veeamservice.sock.
Failed to connect to veeamservice daemon.
To open Veeam Recovery UI execute 'sudo veeam'.
veeamservice start at boot failure

Cause

This is related to a squashfs bug123 in Linux kernel 5.9, which appears in the Enterprise Linux distributions: RHEL 8.3 and specific versions of Oracle Linux. 

Workaround

To access the recovery UI, reboot and press TAB in the Boot menu of the Recovery Media. Add " selinux=0" to the end of the kernel command line and press Enter to finish the boot process.

selinux setting
KB ID: 4183
Product: Veeam Agent for Linux 5.0
Published: 2021-06-17
Last Modified: 2021-08-09

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later
Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.