issue

LIMITED-TIME OFFERVeeam Data Platform + 20% Off Veeam VaultMultiply your resilience with powerful protection at exceptional valueSAVE NOWThis 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 from a USB flash drive created with third-party ISO flashing software.ChallengeA 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.CauseThird-party ISO-to-USB imaging software may alter the way the image boots when writing the ISO contents to the flash drive.WorkaroundWrite the ISO image to the USB flash drive using theddcommand-line program.Example:sudoddbs=4Mif=/path/to/veeam-recovery.isoof=/dev/sdxstatus=progressoflag=syncCopyTheifandofparameters in the command above will need to be adjusted for the environment.Some hardware is not recognized in the Veeam Recovery Media or you are unable to patch Veeam Recovery Media.ChallengeHardware is not recognized in the Veeam Recovery Media environment, and any of the following are also true:UsingCustom Veeam Recovery Mediaalso fails to recognize the hardware.Linux kernel in use was version 3.10 or older.WorkaroundCreate and boot into a Live CD of the Linux distro that is compatible with the hardware.Install Veeam Agent for Linuxinside this Live CD environment.Note: Theveeamsnapkernel module isnotrequired for restores, so to avoid installingkernel-headers,you may either installveeam-nosnap packageor install the veeam package with broken veeamsnap dependency.Enable recovery UI by adding the following line to/etc/veeam/veeam.iniunder the[recoveryui]sectionenableOnLiveSystem=1CopyRestart the veeamservice to apply changes:sudoserviceveeamservice restartCopyOpen Recovery UI using the command:veeamconfig recoveryuiCopyPatched Custom Veeam Recovery ISO does not startveeamserviceon bootChallengeWhen booting from a recovery media image patched on specific Linux kernels,veeamservicedoes 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'.CauseThis is related to asquashfsbug1/2/3in Linux kernel 5.9, which appears in the Enterprise Linux distributions: RHEL 8.3 and specific versions of Oracle Linux.WorkaroundTo 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.Veeam Recovery Media interface doesn't fit within the screen borders.ChallengeVeeam Recovery Media interface doesn't fit within the screen borders.CauseThe screen has a high resolution (1920x1080 and above). Veeam Recovery Media interface screen resolution is 1024x768 by default. This is related to the default video parameter in /boot/grub/grub.cfg:menuentry "Veeam Recovery 4.19.0-17-amd64" { linux /vmlinuz-4.19.0-17-amd64 usbcore.autosuspend=-1 vga=773video=1024x768boot=veeam-live initrd /initrd.img-4.19.0-17-amd64 }WorkaroundReboot and press TAB in the Boot menu of the Recovery Media. Change thevideoparameter to the native display resolution and press Enter to finish the boot process.If this KB article did not resolve your issue or you need further assistance with Veeam software, please create aVeeam Support Case.