2 Problems: backup hangs and start failed: got timeout

McBane

Member
Dec 17, 2019
5
2
8
47
Hello,
we used proxmox for a couple of weeks. We installad several debian machines (pihole, postfix/dovecot, nextcloud, samba-ad, roundcube) and a W10 machine to managa AD for samba. We have two bad problems:
1. After a few days the automatic nightly backup of the pihole VM hangs and we were not able to stop it in a normal way. Only a hard rebbot of the host helps. This happens 3 times in 5 weeks.
2. We stopped automatic backup of pihole. After 5 days without probs the backup of the mailserver hangs in the same way. The host was busy and we were not able to access any of the VMs. After hard reboot everythings works except the W10 machine. A start ends in a timeout. (qm showcmd to get the correct syntax for the console did not help). Restoring the machine did not help.
Infos:
pve-manager/6.1-5/9bf06119 (running kernel: 5.0.21-1-pve)

qm showcmd:
/usr/bin/kvm -id 103 -name Win10Verwaltung -chardev 'socket,id=qmp,path=/var/run/qemu-server/103.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/103.pid -daemonize -smbios 'type=1,uuid=8f3d6064-d065-4288-b599-888bdaf85289' -smp '4,sockets=2,cores=2,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/103.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_ipi,enforce' -m 4096 -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'vmgenid,guid=30005964-ae22-4faa-ba1e-d43f7647525f' -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:956629db9aa3' -drive 'file=/var/lib/vz/images/103/vm-103-disk-0.qcow2,if=none,id=drive-ide0,format=qcow2,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap103i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=0A:ED:3E:52:67:17,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc+pve1' -global 'kvm-pit.lost_tick_policy=discard'

THX for tips
Best regards
Greg
 
Can you please show the output of the command pveversion -v?
 
Hi Aaron,

it looks like we don not need help anymore.
The server had a problem with the filesystem. The Raid was configured in a wrong way. We corrected this and since then the system is in stable state.

I will give an update in a few weeks.

Best regards
Greg
 
  • Like
Reactions: aaron
Could you please mark the thread as solved? Editing the first post and setting the title prefix accordingly. :)
 

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!