Error on Boot up: A start job is running for Activation of LVM2 logical volumes

sector001

New Member
Sep 22, 2018
3
0
1
44
I am getting this error on boot up.

Found volume group "pve" using metadata type lvm2
/sbin/modprobe failed: 1
Can't process LV pve/data: thin-pool target support missing from kernel?
Can't process LV /ve-vm-100-disk-1: thin target support missing from kernel?
Can't process LV /ve-vm-100-disk-2: thin target support missing from kernel?
Can't process LV /ve-vm-101-disk-1: thin target support missing from kernel?

A start job is running for Activation of LVM2 logical volumes...

I googled it and I found another thread with this same problem but there is not enough detail in that thread to tell me how to fix this problem.

Does anyone know how to fix this problem?
 

Attachments

  • IMG_20180921_180231.jpg
    IMG_20180921_180231.jpg
    269.9 KB · Views: 44
I am getting this error on boot up.

Found volume group "pve" using metadata type lvm2
/sbin/modprobe failed: 1
Can't process LV pve/data: thin-pool target support missing from kernel?
Can't process LV /ve-vm-100-disk-1: thin target support missing from kernel?
Can't process LV /ve-vm-100-disk-2: thin target support missing from kernel?
Can't process LV /ve-vm-101-disk-1: thin target support missing from kernel?

those are harmless (the early boot stages don't know how to handle LVM-thin, but they don't need to since only guest volumes are stored there).

A start job is running for Activation of LVM2 logical volumes...

I googled it and I found another thread with this same problem but there is not enough detail in that thread to tell me how to fix this problem.

Does anyone know how to fix this problem?

the question is why does LV activation fail? boot some kind of rescue/live environment, and see if you can manually activate the 'pve' VG and its LVs. perhaps your LVM-thin metadata space is exhausted?
 
the question is why does LV activation fail? boot some kind of rescue/live environment, and see if you can manually activate the 'pve' VG and its LVs. perhaps your LVM-thin metadata space is exhausted?

Sorry for being a noob but how would I manually activate the pve VG and LV? I'm still relatively new to Proxmox so I don't know the commands.
 
Sorry for being a noob but how would I manually activate the pve VG and LV? I'm still relatively new to Proxmox so I don't know the commands.

see the man pages of "vgchange" and "lvchange" ;)
 
  • Like
Reactions: DerDanilo
Hello,

we are just running into the same problem after updating from 4.4 to 5.2.

Is there a chance to get this fixed, or do we have to do a restore ?

Thanks for any help.

Greetings Marco.
 
I have the same problem here. Boot is stuck on "A job is running..." Any suggestions are appreciated. Thanks.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!