Bobcares

wesupport

CLIENT AREACall Us 1-800-383-5193
Bobcares

wesupport

Call Us 1-800-383-5193
Bobcares

wesupport

Call Us 1-800-383-5193

Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Logical volumes not found: OnApp Error

by | Sep 17, 2021

Logical volumes not found: OnApp Error shows up in the logs while we delete the virtual machine.

As part of our Server Virtualization Technologies and Services, we assist our customers with several OnApp queries.

Today, let us see how we can fix this OnApp error.

 

Logical volumes not found: OnApp Error

Generally, the error looks like the following:

Running: Storage API Call: PUT xxx.xxx.xx.x:8080/lvm/Datastore/onapp-xxxxxxxxxxxxxx/VDisk/yyyyyyyyyyyyyy "{\"state\":2}"
OnApp::Actions::Fatal Storage API Call failed: {"result"=>"FAILURE", "Error"=>"Error running lvchange: One or more specified logical volume(s) not found.\n"}
Fatal: OnApp::Actions::Fatal Storage API Call failed: {"result"=>"FAILURE", "Error"=>"Error running lvchange: One or more specified logical volume(s) not found.\n"}
Executing Rollback...

This is likely to happen to any OnApp using LVM Datastore.

Mostly, the cause of this is an incorrect database update. In addition, OnApp tries to delete the logical volume for the second time after it was deleted from the datastore.

 

How can we fix ‘Logical volumes not found’?

Moving ahead, let us see how our Support Techs fix this error for our customers.

To do so, first, we create the disk on the hypervisor in the correct data store (volume group).

It is likely that we may need to ssh into the Hypervisor/Compute Resource or Backup Server.

The server mentioned in the Storage API call should work just fine for this.

From the error message, we take the information and run:

[[email protected]]# ssh [email protected]
[[email protected]]# lvcreate -L1G -n yyyyyyyyyyyyyy onapp-xxxxxxxxxxxxxx

This will create an empty 1GB disk so that the delete VM will not fail to destroy on the next attempt.

Then we run the destroy through the interface and it will eventually complete.

Sometimes there occurs an error if the new LV is only 1GB.

In such a case, we need to create the new LV with the size of the deleted disk and try again.

[Need help with the fix? We’d be happy to do it for you]

 

Conclusion

In short, we saw how our Support Techs fix the OnApp Error quickly for our customers.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Categories

Tags