VM failed to start - logical volume disappeared

animalvet

Member
Aug 26, 2018
2
0
6
60
Backup of a Windows VM failed when the backup disk became full
the guest continued to run
Upon reboot the guest failed to start
Error: start failed

The logical volume info from lvdisplay looks like this:
--- Logical volume ---
LV Path /dev/pve/base-100-disk-1
LV Name base-100-disk-1
VG Name pve
LV UUID UBu5B1-6gQp-nSnH-NypB-S83B-h2tL-BLTx5Z
LV Write Access read only
LV Creation host, time bastet, 2018-08-08 10:59:57 -0700
LV Pool name data
LV Status NOT available
LV Size 155.00 GiB
Current LE 39680
Segments 1
Allocation inherit
Read ahead sectors auto

I've tried lvchange -ay /dev/pve/base-100-disk-1

no change: LV Status NOT available

I added /dev/pve/base-100-disk-1 to Datacenter storage
when selected the status reads
Enabled Yes
Active Yes
Content Disk image, Container
Type LVM
Usage 96.56% (449.00 GiB of 465.00 GiB)

What steps need to be taken
to get this logical volume active/available
mounted and/or recognized by the host
and the guest started?

Thank you,

storage.cfg

dir: local
path /var/lib/vz
content vztmpl,iso,backup

lvmthin: local-lvm
thinpool data
vgname pve
content images,rootdir

dir: share
path /mnt/share
content images
shared 1

dir: backup
path /mnt/backup
content iso,vztmpl,images,backup
maxfiles 5
shared 1

cat /etc/pve/qemu-server/100.conf

agent: 1

bootdisk: virtio0

cores: 3
ide0: local:iso/2012.R2VL.ESD.ENU.June2016.iso,media=cdrom,size=4790784K
ide1: local:iso/virtio-win-0.1.141.iso,media=cdrom,size=309208K
ide2: cdrom,media=cdrom
memory: 8192
name: Win2012AVImarkServer
net0: virtio=FE:47:A4:00:34:68,bridge=vmbr0
numa: 0
onboot: 1
ostype: win8
scsihw: virtio-scsi-pci
smbios1: uuid=b0cc979e-3003-4bbe-9410-82daa3734ca2
sockets: 1
template: 1
usb0: host=05dc:a81d
virtio0: local-lvm:base-100-disk-1,size=155G
virtio2: /dev/disk/by-id/lvm-pv-uuid-b3nE9b-qXpC-Sw7P-mWrQ-qyoy-EUMa-TeR8XD,size=499557318144

--
update

Error attempting to clone
unable to parse volume ID /dev/disk/by-id/lvm-pv-uuid-b3nE9b-qXpC-Sw7P-mWrQ-qyoy-EUMa-TeR8XD (500)

this file doesn't exist: ls /dev/disk/by-id

ata-WDC_WD40EZRZ-00GXCB0_WD-WCC7K7FRZVE0 scsi-3600605b004b4b5d0230a33726bb0e2cf
ata-WDC_WD40EZRZ-00GXCB0_WD-WCC7K7FRZVE0-part1 scsi-3600605b004b4b5d0230a33726bb0e2cf-part1
dm-name-pve-root wwn-0x50014ee2ba8b6c9a
dm-name-pve-swap wwn-0x50014ee2ba8b6c9a-part1
dm-uuid-LVM-AWRx8lyg2QjVqXsAXt8fgf8H6XfEEwXekiUEwX1ItHGXiZGcv518B4dQHp7ya6KR wwn-0x600605b004b4b5d022fd6e3f096f513e
dm-uuid-LVM-AWRx8lyg2QjVqXsAXt8fgf8H6XfEEwXemytJ9t0t3POnUsdNmZeM1c8PSiDZmwzC wwn-0x600605b004b4b5d022fd6e3f096f513e-part1
lvm-pv-uuid-wJx1yU-VWf1-jzxV-42Hi-MeS1-OwAt-TNz4rJ wwn-0x600605b004b4b5d022fd6e3f096f513e-part2
scsi-3600605b004b4b5d022fd6e3f096f513e wwn-0x600605b004b4b5d022fd6e3f096f513e-part3
scsi-3600605b004b4b5d022fd6e3f096f513e-part1 wwn-0x600605b004b4b5d0230a33726bb0e2cf
scsi-3600605b004b4b5d022fd6e3f096f513e-part2 wwn-0x600605b004b4b5d0230a33726bb0e2cf-part1


the UUID from the line LV UUID from lvdisplay does not exist either
I don't know where to go from here
 
Last edited:
SOLVED:

edited /etc/pve/qemu-server/100.conf
removed lines template: 1 and redundant non-existent virtio2: /dev/disk/by-id/UUID- blah...
cloned the guest to a new VM
started the cloned VM
 

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!