Hey everyone,
I’ve been attempting to utilize Proxmox as a replacement for Hyper-V in my homelab and have run into issues with LVM pool utilized to store the majority of my VM disk images.
The primary hard drive configured as an LVM-Thin pool always fails to initiate/start. When attempting to view it via the GUI I get the following error:
I previously had this occur and found the following commands to resolve the issue
Unfortunately when I tried this fix today after restarting my node they no-longer appear to work. When running them I get the following error:
I was wondering if anyone knew a solution to this error?
I’ve been attempting to utilize Proxmox as a replacement for Hyper-V in my homelab and have run into issues with LVM pool utilized to store the majority of my VM disk images.
The primary hard drive configured as an LVM-Thin pool always fails to initiate/start. When attempting to view it via the GUI I get the following error:
I previously had this occur and found the following commands to resolve the issue
Code:
lvchange -a n Hard-Drive/Hard-Drive_tmeta
lvchange -a n Hard-Drive/Hard-Drive_tdata
lvchange -ayUnfortunately when I tried this fix today after restarting my node they no-longer appear to work. When running them I get the following error:
Code:
root@RB-AU-HYV-PB-03:~# lvchange -an Hard-Drive/Hard-Drive_tmeta
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
device-mapper: remove ioctl on (252:4) failed: Device or resource busy
Unable to deactivate Hard--Drive-Hard--Drive_tmeta (252:4).I was wondering if anyone knew a solution to this error?