Wondering how to fix “Could not find a suitable hcpdriver module for your system” error? We can help you.
Often our customers report to us that their r1soft backup fails with this error.
Here at Bobcares, we handle requests from our customers to fix similar errors as a part of our Server Management Services.
Today we will see how our Support Engineers fix this for our customers.
How to fix Could not find a suitable hcpdriver module for your system
A typical error looks like the one given below:
Error replicating device / (a0dbe4b6-4ea0-11e8-85a3-064c640112c6) An exception occurred during the request. The replication driver was not detected (detail: Could not find a suitable hcpdriver module for your system; Please run "r1soft-setup --get-module " on your Agent to install one. ). Agent reported error during requested operation
This error occurs when the hcpdriver module required by the backup server is not installed on the server.
Steps to fix this error
1. Firstly we need to run the following command:
2. After downloading the script successfully we can install the hcpdriver module.
Then we can try running the backup again.
3. In case If the installation isn’t successful it will show the following error messages:
Failed to get suitable module for this system: Failed to build module: No builders found. Get module failed. Falling back to old get-module ...
The above error infers that the server’s kernel is quite new and R1Soft doesn’t have the hcpdriver module for that particular kernel version yet. Generally, it affects newer Linux OS versions such as Ubuntu 18.04.2 TLS.
Checking the kernel version
Using the following command we can chek the kernel version:
root@host# uname -a
We may get the output given below:
Linux ubuntu1804-64b 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
The hcpdriver module for kernel version 4.15.* is still in beta. However, we can download it and install it manually using the following command:
cd /lib/modules/r1soft/ root@host:/lib/modules/r1soft# wget -c http://beta.r1soft.com/modules/hcpdriver-cki-4.15.0-51-generic.ko --2019-06-07 15:04:04-- http://beta.r1soft.com/modules/hcpdriver-cki-4.15.0-51-generic.ko Resolving beta.r1soft.com (beta.r1soft.com)... 126.96.36.199 Connecting to beta.r1soft.com (beta.r1soft.com)|188.8.131.52|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 117232 (114K) [text/plain] Saving to: ‘hcpdriver-cki-4.15.0-51-generic.ko’ hcpdriver-cki-4.15.0-51-generic.ko 100%[========================================================================================================================================>] 114.48K 106KB/s in 1.1s 2021-06-07 15:04:10 (106 KB/s) - ‘hcpdriver-cki-4.15.0-51-generic.ko’ saved [117232/117232]
Restarting the backup agent
After downloading and saving the file in /lib/modules/r1soft folder, we need to restart the backup agent.
For this, we can use the following:
# /etc/init.d/cdp-agent restart
Once done, we can verify whether the backup agent is running by using the following command:
# /etc/init.d/cdp-agent status
We may get an output like the one given below:
● sbm-agent.service - R1Soft CDP Agent service Loaded: loaded (/etc/systemd/system/sbm-agent.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2019-06-07 15:05:32 +08; 32s ago Docs: man:sbm-agent Process: 3165 ExecStop=/usr/sbin/r1soft/service-scripts/agent-service stop (code=exited, status=0/SUCCESS) Process: 3240 ExecStart=/usr/sbin/r1soft/service-scripts/agent-service start (code=exited, status=0/SUCCESS) Main PID: 3255 (cdp-2-6) Tasks: 3 (limit: 1109) CGroup: /system.slice/sbm-agent.service └─3255 /usr/sbin/r1soft/bin/cdp -s -c /usr/sbin/r1soft/conf/agent_config Jun 07 15:05:32 ubuntu1804-64b systemd: Starting R1Soft CDP Agent service... Jun 07 15:05:32 ubuntu1804-64b agent-service: /usr/sbin/r1soft/service-scripts/agent-service start: cdp started Jun 07 15:05:32 ubuntu1804-64b systemd: Started R1Soft CDP Agent service.
We can now try running the backup again.
[Need assistance? We can help you]
In short, we saw how our Support Techs fix “Could not find a suitable hcpdriver module for your system” error for our customers.