VMs won't start start after power surge. /dev/pve/vm-103-disk-0 not found

ecwyne

New Member
Jan 28, 2024
2
1
3
Output of lvs
Code:
  LV            VG  Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  data          pve twi---tz--   1.67t
  data_meta0    pve -wi-------  15.81g
  data_meta1    pve -wi-------  15.81g
  root          pve -wi-ao----  96.00g
  swap          pve -wi-ao----   8.00g
  vm-100-disk-0 pve Vwi---tz--  40.00g data
  vm-101-disk-0 pve Vwi---tz--  32.00g data
  vm-102-disk-0 pve Vwi---tz--  40.00g data
  vm-103-disk-0 pve Vwi---tz-- 750.00g data
  vm-104-disk-0 pve Vwi---tz-- 250.00g data
  vm-105-disk-0 pve Vwi---tz--  32.00g data
  vm-105-disk-1 pve Vwi---tz--   1.00t data

Output of /etc/pve/qemu-server/103.conf
Code:
agent: 1
boot: order=sata0;ide2;net0
cores: 16
ide2: none,media=cdrom
memory: 32768
name: docker
net0: virtio=06:9B:6A:16:4D:03,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: local-lvm:vm-103-disk-0,size=750G
scsihw: virtio-scsi-pci
smbios1: uuid=c81ad829-5450-4b67-bd3c-fa23989a38fa
sockets: 1
vmgenid: 51ea69eb-0b17-4d01-b5d0-fced8408e5a5

Output of lvscan
Code:
ACTIVE            '/dev/pve/swap' [8.00 GiB] inherit
  ACTIVE            '/dev/pve/root' [96.00 GiB] inherit
  inactive          '/dev/pve/data' [1.67 TiB] inherit
  inactive          '/dev/pve/vm-101-disk-0' [32.00 GiB] inherit
  inactive          '/dev/pve/vm-102-disk-0' [40.00 GiB] inherit
  inactive          '/dev/pve/vm-100-disk-0' [40.00 GiB] inherit
  inactive          '/dev/pve/vm-103-disk-0' [750.00 GiB] inherit
  inactive          '/dev/pve/vm-104-disk-0' [250.00 GiB] inherit
  inactive          '/dev/pve/vm-105-disk-0' [32.00 GiB] inherit
  inactive          '/dev/pve/vm-105-disk-1' [1.00 TiB] inherit
  inactive          '/dev/pve/data_meta0' [15.81 GiB] inherit
  inactive          '/dev/pve/data_meta1' [15.81 GiB] inherit

Any direction/advice would be greatly appreciated
 
please check your logs for any errors related to LVM during bootup.

what happens if you run "vgchange -ay"?
 
Thank you! I was actually able to figure it out. I needed to deactivate pve/data_mdatatable (or something like that, I don't remember exactly). After that I was able to activate all of the other drives.
 
  • Like
Reactions: fabian