VM Failing to open

[Jarvar]

I noticed that my VM is not starting like it used to.
I made a clone, but had to move the server briefly. Maybe there was a disconnect of power and it restarted.

Now I get this error when starting
Virtual Environment 6.0-4

Task viewer: VM 101 - Start

OutputStatus

Stop
/dev/sde: open failed: No medium found
/dev/sdf: open failed: No medium found
/dev/sdg: open failed: No medium found
kvm: -drive file=/dev/pve/vm-101-disk-0,if=none,id=drive-sata0,format=raw,cache=none,aio=native,detect-zeroes=on: Could not open '/dev/pve/vm-101-disk-0': No such file or directory
TASK ERROR: start failed: command '/usr/bin/kvm -id 101 -name WS2K19Standard -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/101.pid -daemonize -smbios 'type=1,uuid=accac417-7c05-4a1f-95c0-dfb65dac5f89' -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/101.vnc,password -no-hpet -cpu 'kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,hv_synic,hv_stimer,hv_tlbflush,hv_ipi,enforce' -m 4096 -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'vmgenid,guid=50916b92-9b3f-451c-beb9-e398103d7cdb' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'VGA,id=vga,bus=pci.0,addr=0x2' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:352369c340db' -drive 'file=/var/lib/vz/template/iso/17763.379.190312-0539.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/dev/pve/vm-101-disk-0,if=none,id=drive-sata0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ahci0.0,drive=drive-sata0,id=sata0,rotation_rate=1,bootindex=100' -drive 'file=/dev/pve/vm-101-disk-1,if=none,id=drive-sata1,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ahci0.1,drive=drive-sata1,id=sata1,rotation_rate=1' -netdev 'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=12:1B:4D:FD:B6:F7,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1



Any help would be greatly appreciated.
I got this error when i tried to rollback to a previous snapshot.
before that when I tried starting the VM it would be in the endless progress circle before the Windows Login screen. This was left going for a day, even overnight without a login screen.
Surprisingly the clone works up to login screen but won't accept any of my credentials.
We can't sign you in with these credentials because your domain isn't available. The network connection symbol has a red X.

 

[oguz]

hi,

kvm: -drive file=/dev/pve/vm-101-disk-0,if=none,id=drive-sata0,format=raw,cache=none,aio=native,detect-zeroes=on: Could not open '/dev/pve/vm-101-disk-0': No such file or directory

your VM can't find the disk, so it can't boot. probably related to your power disconnect.

maybe something went wrong with your lvm?
check output of 'lvs -a', 'pvs -a', and 'vgs -a'

also on another note,

Surprisingly the clone works up to login screen but won't accept any of my credentials.
We can't sign you in with these credentials because your domain isn't available. The network connection symbol has a red X.

when cloning a random mac address will be assigned. your mac filter might be blocking the network connection?

 

[Jarvar]

Thank you so much for your reply.
What am I looking for when I type commands lvs -a pvs -a and vgs -a ?
things look pretty standard.

I don't have a mac filter on my router, but the network symbol shows a Red X at login screen. I am trying to find a way to configure my network settings when I can't login...

 

[oguz]

What am I looking for when I type commands lvs -a pvs -a and vgs -a ?
things look pretty standard.

for the disk vm-101-disk-0, since it appears to be unreachable/missing

I don't have a mac filter on my router, but the network symbol shows a Red X at login screen. I am trying to find a way to configure my network settings when I can't login...

can you send me the configuration of the original VM and the clone? qm config VMID should do it.

 

[Jarvar]

This is for the original VM

qm config 101
bootdisk: sata0
cores: 1
ide2: local:iso/17763.379.190312-0539.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.iso,media=cdrom,size=4985424K
memory: 4096
name: WS2K19Standard
net0: e1000=12:1B:4D:FD:B6:F7,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win10
parent: Tracker_Instlld_08302019
protection: 1
sata0: local-lvm:vm-101-disk-0,size=100G,ssd=1
sata1: local-lvm:vm-101-disk-1,size=960G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=accac417-7c05-4a1f-95c0-dfb65dac5f89
sockets: 1
usb0: host=0bc2:ab28,usb3=1
vmgenid: 50916b92-9b3f-451c-beb9-e398103d7cdb

This is for the clone

qm config 103
bootdisk: sata0
cores: 1
ide2: local:iso/17763.379.190312-0539.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.iso,media=cdrom
memory: 8192
name: Test042019
net0: e1000=12:1B:4D:FD:B6:F7,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
protection: 1
sata0: local-lvm:vm-103-disk-1,size=100G,ssd=1
sata1: local-lvm:vm-103-disk-0,size=960G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=9dcc3fcb-7ecb-4f60-a0f8-73a0078c1dca
sockets: 1
usb0: host=0bc2:ab28
usb1: host=0bc2:ab28,usb3=1
vmgenid: 23dacc29-3bf6-497e-9f2d-6b137cc5bc8a

 

[oguz]

hi,

you have same MAC address 12:1B:4D:FD:B6:F7for both VMs. maybe that's why you don't get network connection.

however i think the problem can be because of the power disconnect. it's likely that your disk got corrupted or the lvm metadata was deleted.

not possible to tell without the output from pvs -a, lvs -a and vgs -a

 

[Jarvar]

Here is the output:

pvs -a
/dev/sdd: open failed: No medium found
/dev/sde: open failed: No medium found
/dev/sdf: open failed: No medium found
PV VG Fmt Attr PSize PFree
/dev/sda1 --- 0 0
/dev/sdb2 --- 0 0
/dev/sdb3 pve lvm2 a-- <2.73t 576.00m
/dev/sdc1

lvs -a
/dev/sdd: open failed: No medium found
/dev/sde: open failed: No medium found
/dev/sdf: open failed: No medium found
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
data pve twi-aotz-- 2.58t 50.35 6.44
data_meta0 pve -wi-a----- 15.81g
[data_tdata] pve Twi-ao---- 2.58t
[data_tmeta] pve ewi-ao---- 15.81g
[lvol1_pmspare] pve ewi------- 15.81g
root pve -wi-ao---- 96.00g
snap_vm-100-disk-0_August242019 pve Vri---tz-k 100.00g data vm-100-disk-0
snap_vm-101-disk-0_August28_Not_Setup pve Vri---tz-k 100.00g data
snap_vm-101-disk-0_Prior_to_installing_Tracker08292019 pve Vri---tz-k 100.00g data
snap_vm-101-disk-0_Tracker_Instlld_08302019 pve Vri---tz-k 100.00g data
snap_vm-101-disk-1_August28_Not_Setup pve Vri---tz-k 960.00g data
snap_vm-101-disk-1_Prior_to_installing_Tracker08292019 pve Vri---tz-k 960.00g data vm-101-disk-1
snap_vm-101-disk-1_Tracker_Instlld_08302019 pve Vri---tz-k 960.00g data vm-101-disk-1
swap pve -wi-ao---- 8.00g
vm-100-disk-0 pve Vwi-a-tz-- 100.00g data 7.94
vm-100-state-August242019 pve Vwi-a-tz-- <4.49g data 43.04
vm-101-disk-1 pve Vwi-a-tz-- 960.00g data snap_vm-101-disk-1_August28_Not_Setup 23.26
vm-101-state-August28_Not_Setup pve Vwi-a-tz-- <8.49g data 43.22
vm-101-state-Prior_to_installing_Tracker08292019 pve Vwi-a-tz-- <8.49g data 44.53
vm-101-state-Tracker_Instlld_08302019 pve Vwi-a-tz-- <8.49g data 44.28
vm-103-disk-0 pve Vwi-aotz-- 960.00g data 100.00
vm-103-disk-1 pve Vwi-aotz-- 100.00g data 100.00


And finally:

vgs -a
/dev/sdd: open failed: No medium found
/dev/sde: open failed: No medium found
/dev/sdf: open failed: No medium found
VG #PV #LV #SN Attr VSize VFree
pve 1 19 0 wz--n- <2.73t 576.00m

 

[Jarvar]

hi,

you have same MAC address 12:1B:4D:FD:B6:F7for both VMs. maybe that's why you don't get network connection.

however i think the problem can be because of the power disconnect. it's likely that your disk got corrupted or the lvm metadata was deleted.

not possible to tell without the output from pvs -a, lvs -a and vgs -a

I tried changing the mac address to see if the network would work. It did not. So I changed it back now.
Good catch though.

 

[oguz]

hi,

are you still having the problem?

 

[Jarvar]

Yeah, I think probably had something to do with the hard drive as well. it looks like everything on my proxmox storage disappeared. The hard drive was taken from an old external usb which was having errors before I retired it. Maybe not the best move, but I've had some hard drives resurrect themselves after reformatting and running additional disk tools on it.