LVMDriver : Failed to create LVM Instance

[skbtw]

Hello,
After installed the agent, when I try to configure it I get this message : LVMDriver : Failed to create LVM Instance.
Can you help me to know what is wrong ?
Thanks,
Sokha

[PTide]

Hi,

At which step do you get that message? Also do you have lvm packages installed on the system (what system do you use BTW?) ?

Thanks

[simon021]

I'm getting the same error on a fresh install of Redhat 7.

Only things I have done was add the EPEL and install veeam after updating the system and rebooting.

http://i.imgur.com/tBASt5B.png

[simon021]

I get this same error upon starting up Veeam after a fresh install on a fresh install of RedHat 7.

Also not sure why my other reply was removed...

[simon021]

I found your reply in another topic.


Re: VAL stops with latest ArchLinux - [ID# 02133145]
Veeam Logoby PTide » Wed May 03, 2017 9:41 am
Hi,

Please try to set units=”h” in /etc/lvm/lvm.conf.

Thanks

I was able to add the "units="h"" into my lvm.conf and after a reboot veeam does not give the LVM Instance error anymore.

[skbtw]

Hi,
Thanks for your answer,
I get this message once the agent installed when I press C to configure. I'm using use RHEL 7.
Which are the lvm packages required ?
Sokha

[PTide]

Simon,

Thank you for bringing that here and sorry about the post, it seems that someone deleted it by mistake.

@skbtw,

Please try editing /etc/lvm/lvm.conf as Simon has described.

Thanks

[bpayne]

I ran into this error "LVMDriver : Failed to create LVM Instance" after a new CentOS setup. Support pointed me to this KB https://www.veeam.com/kb2334.

Note in my experience, the solution was the other way around. I needed to change the units value from r to h, not h to r (as stated in the KB). I found another Veeam forum post with the same problem and it was successful changing the value from r to h.

Perhaps the KB article can be fixed?

[PTide]

Hi,

There is no mistake, as the article describes that in RHEL 7.4 the unit has changed from 'h' to 'r'. So, it has to be changed back, from 'r' to 'h'. However, I agree that the wording in the KB might be confusing, it will be fixed.

Thank you for bringing this up!

[mkiselev]

Hi, I've run into the problem described in the topic: veeam-agents-for-linux-mac-aix-solaris- ... 44748.html
Kernel: Linux ipa.opentech.local 4.18.0-348.2.1.el8_5.x86_64 #1 SMP Tue Nov 16 14:42:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
OS: CentOS 8-Stream
Veeam: veeam-5.0.2.4567-1.el8.x86_64 veeamsnap-5.0.2.4567-1.noarch
I tried to fix it by changing the config /etc/lvm/lvmlocal.conf:

Code: Select all

sudo lvmconfig 
config {
}
dmeventd {
}
activation {
}
global {
	units="h"
}
shell {
}
backup {
}
log {
}
allocation {
}
devices {
}

But it did not help

[PTide]

Hi,

Unfortunately, CentOS 8-Stream is not supported by VAL.

The best thing that you could do is to post a link to the full log bundle so that someone could check what's wrong.
Since it will be purely community effort, please don't expect the solution to appear soon (if ever).

Thanks!

[PlintuZz]

Operating System: CentOS Stream 8
CPE OS Name: cpe:/o:centos:centos:8
Kernel: Linux 4.18.0-365.el8.x86_64

veeamsnap-5.0.2.4567-1.noarch.rpm
veeam-5.0.2.4567-1.el8.x86_64.rpm

Code: Select all

[21.04.2022 10:49:25.713] <140597258773824> lpbcomm| Loading config file [/etc/veeam/veeam.ini].
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm|   Upgrading config file.
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm|   Upgrading config file. ok.
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm| Loading config file [/etc/veeam/veeam.ini]. ok.
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm| Initializing new log filter.
[21.04.2022 10:49:25.713] <140597258773824>        | ====================================================================================
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm| {
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm|   Veeam Agent for Linux: veeam.
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm|   PID: 527021
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm|   Version: 5.0.2.4567
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm|   Build date: 08/12/2021
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm|   hostname: portal.acticomp.local
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm|   uname
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm|     sysname : Linux
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm|     release : 4.18.0-365.el8.x86_64
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm|     version : #1 SMP Thu Feb 10 16:11:23 UTC 2022
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm|     machine : x86_64
[21.04.2022 10:49:25.713] <140597258773824> lpbcomm| }
[21.04.2022 10:49:25.713] <140597258773824> lpbcore| Connecting to veeamservice...
[21.04.2022 10:49:25.714] <140597258773824> lpbcore| Connecting to veeamservice... ok.
[21.04.2022 10:49:25.714] <140597258773824> lpbconf| Control session ID is set to: {e2f94cbe-b194-4546-a13b-e7c7c2fafeef}
[21.04.2022 10:49:25.714] <140597258773824>        | Entering FIPS 140-2 mode of operation
[21.04.2022 10:49:25.725] <140597258773824> lpbcore| Detecting whether we are running under recovery ISO.
[21.04.2022 10:49:25.725] <140597258773824> lpbcore|   Distribution ID: "centos"
[21.04.2022 10:49:25.725] <140597258773824> lpbcore| Recovery ISO: [0].
[21.04.2022 10:49:25.725] <140597258773824> lpbcore| Connecting to veeamservice...
[21.04.2022 10:49:25.726] <140597258773824> lpbcore| Connecting to veeamservice... ok.
[21.04.2022 10:49:25.730] <140597258773824> lpbconf| Current group name [root]
[21.04.2022 10:49:25.730] <140597258773824> lpbconf| Running command [ui] with arguments: [{ui}].
[21.04.2022 10:49:25.731] <140597258773824> ncurses| Library [libncursesw.so.5] loaded.
[21.04.2022 10:49:25.739] <140597258773824> lpbconf| Standalone management mode.
[21.04.2022 10:49:25.739] <140597258773824> lpbconf| Welcome wizard is not needed.
[21.04.2022 10:49:25.749] <140596659386112> cli    | Thread [LicWarn timer].
[21.04.2022 10:49:25.770] <140597258773824> lpbconf| CShareRepoPageCtrl::updateView.
[21.04.2022 10:49:25.840] <140596650993408> cli    | Thread [SessionList timer].
[21.04.2022 10:49:25.840] <140596642600704> cli    | Thread [SessionInfo].
[21.04.2022 10:49:25.840] <140596425520896> cli    | Thread [NcInputHandler].
[21.04.2022 10:49:25.841] <140596417128192> cli    | Thread [NcEvtDispatcher].
[21.04.2022 10:49:25.841] <140596408735488> cli    | Thread [PaintTimer timer].
[21.04.2022 10:49:25.874] <140596417128192> lpbconf|   CShareRepoPageCtrl::updateView.
[21.04.2022 10:49:27.888] <140596417128192> lpbconf|   CJobWizardCtrl::Show().
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | WARN|Method invocation was not finalized. Method id [21]. Class: [lpbcorelib::interaction::ILpbService]
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | ERR |LvmDriver: Failed to create LVM instance.
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |--tr:in static void lvmlib::CLvmDriver::initLvm() at /mnt/Sources/LvmLib/lvmlib/LvmDriver.cpp:668
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |--tr:CRealLvmScanner: Failed to scan.
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |--tr:in virtual void lpbdevenumlib::accessor::CRealLvmScanner::Scan(lpbdevenumlib::accessor::CLvmVolumeGroupStorage::Map&) at /mnt/Sources/LpbDevEnumLib/lpbdevenumlib/accessor/lvm/impl/RealLvmScanner.cpp:72
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |--tr:CLvmAccessor: Failed to scan volume groups.
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |--tr:in void lpbdevenumlib::accessor::CLvmAccessor::Scan() at /mnt/Sources/LpbDevEnumLib/lpbdevenumlib/accessor/lvm/LvmAccessor.cpp:36
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |--tr:LvmDevsEnumerator: Failed to enumerate devices.
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |--tr:in virtual lpbdevenumlib::enumeration::CEnumDevsCollection::Ptr lpbdevenumlib::enumeration::CLvmDevsEnumerator::Enumerate() at /mnt/Sources/LpbDevEnumLib/lpbdevenumlib/enumeration/LvmDevsEnumerator.cpp:53
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |--tr:CLinuxDevsEnumerator: Failed to enumerate devices.
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |--tr:in virtual lpbdevenumlib::enumeration::CEnumDevsCollection::Ptr lpbdevenumlib::enumeration::CLinuxDevsEnumerator::Enumerate() at /mnt/Sources/LpbDevEnumLib/lpbdevenumlib/enumeration/LinuxDevsEnumerator.cpp:74
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |--tr:Failed to execute method [21] for class [lpbcorelib::interaction::ILpbService].
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |--tr:in void remoting::CStubBase<TStub, TObject>::ExecuteMethod(remoting::method_id_t, remoting::IStub::SDispatchContext&) const [with TStub = lpbcorelib::interaction::proxystub::CLpbServiceStub; TObject = lpbcorelib::interaction::ILpbService; remoting::method_id_t = unsigned int] at /mnt/Sources/VeeamLPBService/server/../../LPBCoreLib/lpbcorelib/interaction/proxystub/../../../../ProtocolLib/remoting/StubBase.h:78
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |--tr:Failed to invoke method [21] in class [lpbcorelib::interaction::ILpbService].
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |--tr:in void remoting::CProxyBase::CMethodInvocationStream<TObject>::FinalizeExc() [with TObject = lpbcorelib::interaction::ILpbService] at /mnt/Sources/LPBCoreLib/lpbcorelib/interaction/proxystub/../../../../ProtocolLib/remoting/ProxyBase.h:92
[21.04.2022 10:49:27.927] <140596417128192> prtcl  | >>  |An exception was thrown from thread [140596417128192].
[21.04.2022 10:49:27.927] <140596417128192> lpbconf|   CJobWizardCtrl::Show(). Failed.
[21.04.2022 10:49:27.929] <140596417128192> lpbconf| ERR |CSessionListThread: Failed to process pressed key [c (char: c)].
[21.04.2022 10:49:27.929] <140596417128192> lpbconf| >>  |LvmDriver: Failed to create LVM instance.

[PlintuZz]

UPD. Work on 8 stream
edit lvm.conf
Unccomit units = "r" in global, and change to units = "h"

[philrandal]

This also affects RHEL 8.6 which was released yesterday.

The change to lvm.conf fixes it.

[tyler-no-work]

@philrandal is correct, with the new RHEL kernel release, the lvm.conf change fixes this failure. Odd though that the KB article referenced above is now gone, that link just goes to a 404 error now.

[arogarth]

Same here - RHEL 8.6

LvmDriver: Failed to create LVM instance.

I opened a ticket to the Support...

[arogarth]

Hey, VEEAM created a HotFix for RHEL 8.6 - Please contact support to get the new RPM packages.

I installed them and it works great!

Thanks to VEEAM Team!!

[aj_potc]

> Linux oraclelinuxdb 5.4.17-2136.306.1.3.el8uek.x86_64

That seems to be Oracle's own kernel. I'm not aware if that's supported by Veeam, as it's outside of the RHEL ecosystem.

If you boot into the regular Red Hat kernel (which should be version 4.18), do you still have a problem?

[sfaits]

Running into the same issue after updating our test RHEL 8 vm.
Just wanted to post a thanks for the information on the workaround (tested successfully with the units = "h") and opened a support ticket on the hotfix.

Thanks much everyone!

[riahc3]

How do I install Veeam Agent for Linux CentOS 8?

[PTide]

You can use Veeam Backup & Replication server to install the agent, or you can install the agent manually using packages. Please check the user guide for details.