[warn] Cannot find EFI boot manager utility with veeam Agent free for linux

[Stevo63]

Hopefully i'm right here ...

i run an standard debian stretch* 64bit laptop for private use with veeam agent for linux free v.2.01.665. backup and restore runs fine.

without making major changes besides the standard debian updates offered to user, veeam gives a "[warn] Cannot find EFI boot manager utility" message. Last backup without this message was 2019-06-02, first backup with this message was 2019-07-02. i searched a while for a solution, but dont find anything that helps me.

i updated to veeam 3.01.1046 64 bit but this did not solve the problem.

it seems to me that something in the debian updates interferes with veeam agent, but i'm not that specialist to find out what update and what to do. Can someone pleas help in this case?

Kind regards

Stevo

*
stefan@Stefan-A357:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.9 (stretch)
Release: 9.9
Codename: stretch
stefan@Stefan-A357:~$ uname -a
Linux Stefan-A357 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u3 (2019-06-16) x86_64 GNU/Linux

[PTide]

Hi,

Is your system EFI-based, or BIOS-based? If the latter, then do you have any EFI partitions on the drives? If so, then do you have efibootmgr installed?

Thanks!

[Stevo63]

Hello and thank you for helping me.

Yes, its efi based and booted (sys/firmware/efi is there). In var/log/dpkg.log.1 is see that:

....

Code: Select all

2019-06-19 17:41:02 status installed grub-efi-amd64-bin:amd64 2.02~beta3-5+deb9u1
2019-06-19 17:41:02 remove grub-efi-amd64-bin:amd64 2.02~beta3-5+deb9u1 <keine>
2019-06-19 17:41:02 status half-configured grub-efi-amd64-bin:amd64 2.02~beta3-5+deb9u1
2019-06-19 17:41:02 status half-installed grub-efi-amd64-bin:amd64 2.02~beta3-5+deb9u1
2019-06-19 17:41:02 status config-files grub-efi-amd64-bin:amd64 2.02~beta3-5+deb9u1
2019-06-19 17:41:02 status config-files grub-efi-amd64-bin:amd64 2.02~beta3-5+deb9u1
2019-06-19 17:41:02 status config-files grub-efi-amd64-bin:amd64 2.02~beta3-5+deb9u1
2019-06-19 17:41:02 status not-installed grub-efi-amd64-bin:amd64 <keine>
2019-06-19 17:41:02 status installed efibootmgr:amd64 14-2
2019-06-19 17:41:02 remove efibootmgr:amd64 14-2 <keine>
2019-06-19 17:41:02 status half-configured efibootmgr:amd64 14-2
2019-06-19 17:41:02 status half-installed efibootmgr:amd64 14-2
2019-06-19 17:41:02 status config-files efibootmgr:amd64 14-2
2019-06-19 17:41:02 status config-files efibootmgr:amd64 14-2
2019-06-19 17:41:02 status config-files efibootmgr:amd64 14-2
2019-06-19 17:41:02 status not-installed efibootmgr:amd64 <keine>

....

but how is this possible? also there are the packages grub-pc and grub-pc-bin installed which are for pcbios based systems. grub-efi and grub-efi-amd64-bin etc are not installed.

besides this issue (do i have one?) the installation of efibootmgr fixed the warn message from veeam - thank you very much for that!!!!

But do i habe a efi-problem instead?

kind regards

stevo

[PTide]

When Veeam detects EFI partitions, it attempts to use efibootmgr to get boot entries from EFI Boot Manager. Without that you would have to restore those entires manually after bare-metal recovery. This is the reason why it was giving you the warning.

As to your question - I am not sure that I understand what you mean by efi-problem, please elaborate.

Thanks!

[Stevo63]

thank you.

to my understanding, the packages grub-pc and grub-pc-bin are for bios-based pc's. as my laptop boots with (u)efi, i wondered why and how this is possible without the proper grub-efi and grub-efi-amd64-bin packages installed. i thought of this being my so called (maybe?) "efi-problem"

im not *that* experienced in this so my apologies ...

[PTide]

This is what man dpkg says:

Code: Select all

half-installed
              The  installation  of  the  package  has  been  started, but not
              completed for some reason.

<...>
half-configured
              The package is unpacked and configuration has been started,  but
              not yet completed for some reason.
<...>
 --configure package...|-a|--pending
              Configure  a  package  which  has  been  unpacked  but  not  yet
              configured.  If -a or --pending is given instead of package, all
              unpacked but unconfigured packages are configured.

That is, you should try to run dpkg --configure -a and check the log again. Please let me know how it goes.

Thanks!

[Stevo63]

i figured out, that the mentioned section of the log above is ok. packages are all well, exept that these 2 were removed. reading from top to bottom (which is not to be seen in the above snippet, cause they have all the same timestamp) the log says that the 2 packages are removed.

i reinstalled efibootmgr which solves the problem with the veeam warning now.

i've no clue why the 2 were removed and why there are the pc-bios based grub packages grub-pc and grub-pc-bin installed on my laptop instead the corresponding efi-packages grub-efi and grub-efi-amd64-bin packages while my laptop boots with efi. efi is a special thing and i think i have so ask in the debian forum to not wasting your time.

thanks again for the help with veeam, i really appreciate that!!

stevo

[szabkel]

I am using the free linux agent to backup my workstation.
When I am backing up the linux system with veeam, I have a warn:


I have two NVMe SSD-s. One has Windows 10 installed, the other one has Linux Mint 21.1. I boot from the linux one, it has an entry to windows as well.

Booting works from either ssd, if I select the windows ssd as a boot device in bios, I boot into windows immediately. If I select the linux ssd, grub is displayed with options to select linux mint or windows. The boot-repair utility says the linux has the boot sector on my linux ssd:


My disks:

Code: Select all

szabkel@mint10900:~$ sudo fdisk -l /dev/nvme0n1
[sudo] password for szabkel:     
Disk /dev/nvme0n1: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 970 EVO Plus 1TB            
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 0FFFD452-185F-4DF1-B369-48B00892351F

Device          Start        End    Sectors   Size Type
/dev/nvme0n1p1   2048     206847     204800   100M EFI System
/dev/nvme0n1p2 206848     239615      32768    16M Microsoft reserved
/dev/nvme0n1p3 239616 1953523711 1953284096 931,4G Microsoft basic data

szabkel@mint10900:~$ sudo fdisk -l /dev/nvme1n1
Disk /dev/nvme1n1: 953,87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: ADATA SX8200PNP                         
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 0E9690A3-2899-4952-9F7A-4D44FBFBD0F2

Device           Start        End    Sectors   Size Type
/dev/nvme1n1p1    2048    1050623    1048576   512M EFI System
/dev/nvme1n1p2 1050624 2000408575 1999357952 953,4G Linux filesystem

When I setup the backup job and select a volume, veeam displays me this:


I tried to restore the linux backup to a VM, but it failed.:


Previous community post: https://community.veeam.com/discussion- ... -guid-5111

[Mildur]

Hello szabkel

That sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic. Without case number, the topic will eventually be deleted by moderators.

The error in the backup job session could be related to a missing or corrupted efibootmgr installation. But without debug logs analyzed by our support team I cannot say for sure. Such issues must be solved by a support ticket.
--> post333545.html#p333545

Also please not, Linux Mint 21.1 was never tested by us and is therefore not supported by Veeam:
https://helpcenter.veeam.com/docs/agent ... tml?ver=60

Best regards,
Fabian

[PTide]

Hello,

What does 'efibootmgr -v' says?

Thanks!

[szabkel]

@PTide

Code: Select all

BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0000,0001
Boot0000* Windows Boot Manager	HD(1,GPT,5224ad67-a459-4f7c-9e90-7b7d0cc8a906,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...5................
Boot0001* Hard Drive	BBS(HD,,0x0)..GO..NO........q.S.a.m.s.u.n.g. .S.S.D. .9.7.0. .E.V.O. .P.l.u.s. .1.T.B....................A...........................%8V.P.......4..Gd-.;.A..MQ..L.S.6.P.7.N.G.0.R.6.0.0.7.3.6.N........BO..NO........k.A.D.A.T.A. .S.X.8.2.0.0.P.N.P....................A..........................................Gd-.;.A..MQ..L.2.N.1.4.2.L.2.6.D.7.K.W........BO
Boot0002* ubuntu	HD(1,GPT,5224ad67-a459-4f7c-9e90-7b7d0cc8a906,0x800,0x32000)/File(\EFI\UBUNTU\SHIMX64.EFI)

@Mildur
I am not sure what could be wrong. I can boot just fine. The boot sector is not missing.