Wondering how to fix R1Soft Error – Could Not Start Snapshot? We can help you!

Here at Bobcares, we often 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 do this for our customers.

How to fix R1Soft Error – Could Not Start Snapshot

Before going into the steps for fixing this error we will see what causes this error.

Symptom

Error with 3.x Agent unloading properly in all versions of CDP:

Cause:

This happens when there is a problem with the unloading of the Agent in any 3.x version.

When the agent module is removed (rmmod) the problem occurs and the only fix is to reboot the Host OS.

At times the problem may exist in upgrades since the process of the upgrade performs a rmmod on the cdp-agent module.

Steps to fix this error:

1. If we are using version 3.6.x, we have to do the following prior to upgrading above 3.6, or we can install a newer Agent.

a) Firstly we have to Unlock the hcpdriver:

# /usr/sbin/r1soft/bin/cdp -u

b) Then stop the Agent:

# /etc/init.d/cdp-agent stop

c) After that we will remove the driver:

# rmmod hcpdriver

2. If we are using version 3.7.5, we have to do the following prior to upgrading above 3.7, or we can install a newer Agent.

The procedure below will also allow us to fix the StartSnaphot:88 error without having to reboot.

a) We can start the cdp-agent after removing the hcpdriver manually.

b) Following command can be used to stop the Agent:

# /etc/init.d/cdp-agent stop

c) And finally remove the driver:

# rmmod hcpdriver

[Need assistance? We can help you]

Conclusion

To conclude, we saw the steps that our Support Techs follow to fix the R1Soft Error – Could Not Start Snapshot for our customers.