VM fails to start after stopping a hung backup task

[Drax]

The backup task had hung because it was running over 12 hours that should have been 4. I stopped the backup task, the VM would not respond. So the node was restarted. The VM failed to start. It said start failed, VM locked (backup) So I searched and found an unlock command that seemed to unlock the VM, BUT it still fails to start. I get this error when attempting to start.

TASK ERROR: start failed: command '/usr/bin/kvm -id 2134 -chardev 'socket,id=qmp,path=/var/run/qemu-server/2134.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/2134.vnc,x509,password -pidfile /var/run/qemu-server/2134.pid -daemonize -name -smp 'sockets=4,cores=1' -nodefaults -boot 'menu=on' -vga cirrus -cpu kvm64,+x2apic,+sep -k en-us -m 4096 -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' -drive 'file=/data/template/iso/ubuntu-12.04.3-server-amd64.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/data/images/2134/vm-2134-disk-1.qcow2,if=none,id=drive-virtio0,format=qcow2,aio=native,cache=none' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap2134i0,script=/var/lib/qemu-server/pve-bridge,vhost=on' -device 'virtio-net-pci,mac=5A:*.*.*.*,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -machine 'type=pc-i440fx-1.4'' failed: got timeout

How do I fix this? I need to fix this so I can get it running and get good backups before updating to latest Proxmox.

 

[Alwin]

Check if you have all your media available (disks, CD/DVD drives) and that the storage does not have any issues.

 

[Drax]

Proxmox shows the media is there, is there anything else I should check? how do I check if the storage has any issues? I am on VE 3.1

 

[Alwin]

PVE 3 is EoL, current is PVE 5.1.

Are those also accessible on the console (eg. read/write permissions)? Is the qcow2 file consistent (qemu-img check)?

file=/data/template/iso/ubuntu-12.04.3-server-amd64.iso
file=/data/images/2134/vm-2134-disk-1.qcow2

Do you see any further messages in the syslog?

 

[Drax]

YEs I understand PVE 3 is EOL. trying to get the system at a stable place to begin the upgrade to 5.1 Yes the storage is accessible via the PM interface. The VM has now mysteriously started. I honestly don't know why. I didn't do anything or change anything. Thanks for you assistance.

How can I check Drive integrity of the storage? I would like to know that I don't have a drive going bad.

 

[Alwin]

Depends on your storage setup, which tools you need to take. In general on linux you can find hints about drive errors in syslog/kernel.log or smartctl.

 

[Drax]

Got three system emails this morning. what do they mean? Please advise.
1.)
/etc/cron.daily/logrotate:
error: error creating output file /var/log/syslog.1.gz: File exists
run-parts: /etc/cron.daily/logrotate exited with return code 1

2.)
A DegradedArray event had been detected on md device /dev/md/0.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid10]
md0 : active raid10 sda1[0] sdd1[3] sdg1[4](F) sdb1[1]
3906763776 blocks super 1.2 512K chunks 2 near-copies [4/3] [UU_U]

unused devices: <none>

3.)
A SparesMissing event had been detected on md device /dev/md/0.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid10]
md0 : active raid10 sda1[0] sdd1[3] sdg1[4](F) sdb1[1]
3906763776 blocks super 1.2 512K chunks 2 near-copies [4/3] [UU_U]

unused devices: <none>