local-lvm goes wrong after upgrade to pve 7.0

HinataKato

New Member
Sep 17, 2021
3
0
1
22
I upgraded PVE from 6.4 to 7.0 by guide, and after rebooting, I found that the task log was full of
Code:
Could not open '/dev/pve/vm-vmid-disk-0': No such file or directory
and my local-lvm went straight to 0 GB of xxx GB occupancy
Here is my boot log
https://pastebin.com/gW616XQU

lvscan
Code:
root@hinatakato-pve:~# lvscan
  ACTIVE            '/dev/pve/swap' [8.00 GiB] inherit
  ACTIVE            '/dev/pve/root' [58.00 GiB] inherit
  inactive          '/dev/pve/data' [<147.38 GiB] inherit
  inactive          '/dev/pve/vm-100-disk-0' [52.00 MiB] inherit
  inactive          '/dev/pve/vm-200-disk-0' [50.00 GiB] inherit
  inactive          '/dev/pve/vm-200-disk-1' [4.00 MiB] inherit
  inactive          '/dev/pve/vm-300-disk-0' [3.00 GiB] inherit
  inactive          '/dev/pve/vm-301-disk-0' [308.00 MiB] inherit
  inactive          '/dev/pve/vm-101-disk-0' [4.00 GiB] inherit
  inactive          '/dev/pve/vm-101-disk-1' [4.00 MiB] inherit
  inactive          '/dev/pve/vm-302-disk-0' [160.00 MiB] inherit
  inactive          '/dev/pve/vm-400-disk-0' [8.00 GiB] inherit
  inactive          '/dev/pve/vm-303-disk-0' [204.00 MiB] inherit
  inactive          '/dev/pve/snap_vm-301-disk-0_vzdump' [308.00 MiB] inherit
  inactive          '/dev/pve/vm-100-disk-1' [4.00 MiB] inherit
  ACTIVE            '/dev/pve/vm-900-disk-0' [4.00 MiB] inherit
vgdisplay
Code:
root@hinatakato-pve:~# vgdisplay
  --- Volume group ---
  VG Name               ST1000DM003
  System ID            
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  38
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                0
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               <931.51 GiB
  PE Size               4.00 MiB
  Total PE              238466
  Alloc PE / Size       0 / 0  
  Free  PE / Size       238466 / <931.51 GiB
  VG UUID               FbH505-vIQv-X685-1Izg-QTsr-GtEM-Pfue1v
  
  --- Volume group ---
  VG Name               pve
  System ID            
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  414
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                16
  Open LV               2
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               232.38 GiB
  PE Size               4.00 MiB
  Total PE              59490
  Alloc PE / Size       55394 / 216.38 GiB
  Free  PE / Size       4096 / 16.00 GiB
  VG UUID               1XpVy7-Rrnz-eYbL-GdlD-E7y3-k9MR-pUxNWf
some of the system report
https://pastebin.com/93jUzNmR

Any help pls?

Update:
It looks like I have to manually reactivate the logical volume every time I reboot
 
Last edited:
Nvm, it fixed itself
lmao lmao lmao lmao lmao lmao


NOPE, it broke again after reboot
 
Last edited:

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!