Couldn't find device with uuid '***' - lvm

If you have a lost device that is no longer used, but the device data is available to the lvm, lvm will throw an error like the following:
Couldn't find device with uuid '**'

This is because lvm isn't able find the physical disk related to the UUID in it's database. A quick work around is to use vgreduce to removemissing attribute. This will remove any content related to the lost device. First you should test this. For example if the volumegroup in the lost device was vg0, the command would be like following:
vgreduce --removemissing --test vg0

This will return what are they going to perform, like deleting lv etcs. If everything seems alright, then run the following:
vgreduce --removemissing vg0

Sometimes, vgreduce may fail, if the device is lost, we can assume the related LVs are no longer necessary or exists. You may safely run the command with force:
vgreduce --removemissing vg0 --force

Please remember to understand the relations available before running the above command.

Once done, you should be able to run pvscan and pvs to see your existing physical volumes. 

  • lvm, uuid, lost device, centos, linux
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

R1soft Backup Error - Failed To Backup LVM/MD Configuration

It looks like R1Soft manages it's own lvm.static file to process lvm backups. But sometimes it...

Does R1Soft work with LVM?

It does. But it is not fully supported as of 28th November, 2017. If you have a solid logical...

Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)

CentOS 7 / CloudLinux 7 / RHEL 7 may show the following error while restarting Apache/Exim or...

[957833.048873] EXT4-fs warning (device dm-0): ext4_dx_add_entry:2016: Directory index full!

A dedicated server customer came with an error of failed WHM login. When I tried to enter, I...

lfd on ***.***.***: ModSecurity persistent IP database size alert

LFD was throwing the following error for sometime in a server: ModSecurity persistent IP...