VirtualMachine not starting

[shan]

Our proxmox crashed and now i am unable to put online this virtual machine can any one help please


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

TASK ERROR: start failed: command '/usr/bin/kvm -id 109 -chardev 'socket,id=qmp,path=/var/run/qemu-server/109.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/109.pid -daemonize -smbios 'type=1,uuid=b7fc2c7b-650d-4dc2-a640-bbaa1f3fb8d1' -name zabbixomn -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga cirrus -vnc unix:/var/run/qemu-server/109.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 3024 -k es -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 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:98dcd2fbb9b' -drive 'file=/mnt/pve/os-iso/template/iso/zabbix_appliance_3.2.4_x86_64.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 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/pve/vm-109-disk-1,if=none,id=drive-scsi0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap109i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=C2:CE7:38:40:40,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -netdev 'type=tap,id=net1,ifname=tap109i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=2E:BF:FA:3E:19:1E,netdev=net1,bus=pci.0,addr=0x13,id=net1,bootindex=301'' failed: exit code 1

 

[pabernethy]

Could not open '/dev/pve/vm-109-disk-1': No such file or directory

There's your problem. Find out what happened to the disk image.

# lvscan

should give a first impression of the situation.

 

[shan]

There's your problem. Find out what happened to the disk image.

# lvscan

should give a first impression of the situation.

Hi,
First of all thank you so much for your help i really appreciate it. Here is my output thank you

inactive '/dev/lvm-systems/vm-103-disk-3' [32.00 GiB] inherit
inactive '/dev/lvm-systems/vm-102-disk-1' [300.00 GiB] inherit
ACTIVE '/dev/lvm-systems/vm-101-disk-1' [300.00 GiB] inherit
inactive '/dev/lvm-systems/vm-118-disk-1' [45.00 GiB] inherit
ACTIVE '/dev/lvm-systems/vm-102-disk-2' [30.00 GiB] inherit
ACTIVE '/dev/pve/swap' [8.00 GiB] inherit
ACTIVE '/dev/pve/root' [96.00 GiB] inherit
inactive '/dev/pve/data' [438.61 GiB] inherit
inactive '/dev/pve/vm-109-disk-1' [15.00 GiB] inherit
inactive '/dev/pve/data_meta0' [112.00 MiB] inherit
ACTIVE '/dev/pve/vm-101-disk-1' [300.00 GiB] inherit
ACTIVE '/dev/pve/vm-117-disk-1' [32.00 GiB] inherit


inactive '/dev/pve/vm-109-disk-1' [15.00 GiB] inherit

 

[pabernethy]

Not sure why a crash would deactivate the volumes.
Your whole LVM Thin pool is inactive. Please post yout /etc/pve/storage.cfg before you do anything.
You should be able to activate the volume with

# lvchange -ay pve/vm-109-disk-1

 

[shan]

Hi,
here it is

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

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

iscsi: systems
portal 192.168.0.240
target iqn.1994-11.com.netgearsmio-nas01:58f3c025:vmsystemstorage
content none

lvm: lvm-systems
vgname lvm-systems
shared
base systems:0.0.0.scsi-360014050804a7365d1d496dad7ba3895
content rootdir,images

nfs: os-iso
path /mnt/pve/os-iso
export /data/os-iso
server 192.168.0.240
content images,rootdir,backup,vztmpl,iso
maxfiles 0
options vers=3

nfs: sysbackup
path /mnt/pve/sysbackup
export /data/sysbackup
server 192.168.0.240
content images,backup
maxfiles 0
options vers=3

nfs: nfs-systems
path /mnt/pve/nfs-systems
export /data/vmsystems2
server 192.168.0.240
content images
maxfiles 1
options vers=3

nfs: esysbackups
path /mnt/pve/esysbackups
export /data/esysbackups
server 192.168.0.229
content images,backup
maxfiles 0
options vers=3

zfspool: vmdata
pool tank/vmdata
content rootdir,images
sparse

thank you again

 

[pabernethy]

Ok. So you pve pool is enabled as far as PVE is concerned, but for some reason didn't activate. If you didn't already, you can try giving the host a clean reboot, if that's feasible. If that didn't fix it or you can't do it right now, please post the output of vgdisplay and pvdisplay. You could also search through the log if there's a hint why it didn't activate during boot.

 

[shan]

i have already tried the reboot and it seems that that file 109-disk is not anymore in /dev/pve i dont know why it has been deleted here is the output

gdisplay
--- Volume group ---
VG Name lvm-systems
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 65
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 5
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 899.99 GiB
PE Size 4.00 MiB
Total PE 230398
Alloc PE / Size 180992 / 707.00 GiB
Free PE / Size 49406 / 192.99 GiB
VG UUID Y0YPJf-0CYY-recp-RWrf-0WV2-z9lq-q8pW6q

--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 56
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 7
Open LV 3
Max PV 0
Cur PV 1
Act PV 1
VG Size 558.60 GiB
PE Size 4.00 MiB
Total PE 143002
Alloc PE / Size 138992 / 542.94 GiB
Free PE / Size 4010 / 15.66 GiB
VG UUID pmw2z4-qXs9-WfFZ-3VaJ-ESv0-9lZG-UH0PYg

pvdisplay

PV Name /dev/sdb
VG Name lvm-systems
PV Size 900.00 GiB / not usable 0
Allocatable yes
PE Size 4.00 MiB
Total PE 230398
Free PE 49406
Allocated PE 180992
PV UUID hudbDF-YbLS-lA6z-btoe-pNID-2Whb-FI0jLa

--- Physical volume ---
PV Name /dev/sda3
VG Name pve
PV Size 558.61 GiB / not usable 4.28 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 143002
Free PE 4010
Allocated PE 138992
PV UUID pmuZuM-UTFd-egsM-ut20-lfbU-kZwR-9QsOTZ

 

[shan]

well it seems that doing
lvchange -ay pve/vm-109-disk-1 did the trick, the vm is up and running

 

[pabernethy]

Don't forget do activate the other volumes in that pool, if they aren't already. lvm-systems also has some inactive VM disks. Glad that it works, but it would be kinda interesting to know what caused that behaviour.

 

[shan]

I still have no clue why it occured, if you can suggest me some more logs and where to find them we can check them

thank you

 

[Pablo Quispe]

Hello everybody, I am new on this community. I need your help with a common error I suppose.
Well, when I 've started the virtual machine on Proxmox, I got a message that says Error: No accelerator found!.
I hope that you can helo me with this error.
I am using a machine whit this specs:
- 50 GB HDD
- 8 GB RAM
- Core i7-4300 3.6 GHz

The OS guest is W7PRO

Thank you in advance.

 

[tom]

No accelerator

You need to enable Intel VT in your mainboard bios.

 

[Pablo Quispe]

You need to enable Intel VT in your mainboard bios.

Hello, thank you for your reply.
The VT is anabled, but I 've installed Proxmox on VMware Workstation 12. is possible to use proxmox over another virtualization software?
thank you in advance.

 

[tom]

You need to enable "Virtualize Intel VT" in your VMware settings. You can do this only if your physical CPU support this.

This is suitable for testing only (but not super stable or super fast).