VM crashing after adding RAM and now won't start at all

[Anon0ne]

Hello, I added some ram to my PC earlier, rebooted and all was fine. Later on the VM started crashing back-to-back and now it won't start at all.

Only changes made today were new ram, and I install qemu-guest-agent as well and enabled it.

Now the error below when we try to start:

kvm: -drive file=/mnt/data/hdd-img//images/103/vm-103-disk-0.qcow2,if=none,id=drive-scsi0,format=qcow2,cache=none,aio=native,detect-zeroes=on: qcow2: Image is corrupt; cannot be opened read/write
TASK ERROR: start failed: command '/usr/bin/kvm -id 103 -name ubuntu -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=688e34c8-c219-46fc-9211-c0e2689b7b11' -smp '4,sockets=4,cores=1,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 -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 4072 -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=f3ee8ac9-57e0-47ab-bf88-33727e848973' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'nec-usb-xhci,id=xhci,bus=pci.1,addr=0x1b' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'usb-host,bus=xhci.0,hostbus=2,hostport=1.2,id=usb0' -device 'VGA,id=vga,bus=pci.0,addr=0x2' -chardev 'socket,path=/var/run/qemu-server/103.qga,server,nowait,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:4c4f8559ce55' -drive 'file=/mnt/data/hdd-img//template/iso/ubuntu-18.04.4-live-server-amd64.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=100' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/mnt/data/hdd-img//images/103/vm-103-disk-0.qcow2,if=none,id=drive-scsi0,format=qcow2,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=200' -drive 'file=/disk1/images/103/vm-103-disk-0.qcow2,if=none,id=drive-scsi1,format=qcow2,cache=none,aio=native,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi1,id=scsi1' -netdev 'type=tap,id=net0,ifname=tap103i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=16:14:C0:8F:F8:67,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -machine 'type=pc+pve1'' failed: exit code 1

 

[openaspace]

try to restore the vm from a backup first

 

[Anon0ne]

try to restore the vm from a backup first

There weren't a backup yet, just started this VM today.

Just realized entire system is becoming unresponsive even the host.


While connected to the host, i performed qemu-img check -r all *filename*

then it allowed me to hit start, right after starting the below message arrived and crashed host:

Message from syslogd@pve at Feb 24 19:59:30 ...
kernel:[ 2286.391453] systemd[1]: segfault at 555848f7c704 ip 00005558c6e00d0d sp 00007ffeaa1ed3f8 error 4 in systemd[5558c6db6000+b1000]

Message from syslogd@pve at Feb 24 19:59:30 ...
kernel:[ 2286.391523] Code: fb ff e9 29 95 fb ff 66 0f 1f 44 00 00 48 85 ff 74 2b 83 7f 08 01 0f 85 1d 95 fb ff 48 63 97 98 08 00 00 48 8d 05 33 bd 07 00 <8b> 04 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 83 ec


edit: removed the ram and rebooted.. it's running right now; hopefully it stays running. Wondering if I got faulty ram, or if there is something that I messed up with the configuration of the ram.

 

[aaron]

edit: removed the ram and rebooted.. it's running right now; hopefully it stays running. Wondering if I got faulty ram, or if there is something that I messed up with the configuration of the ram.

Have you tried to run a memory test to see if it might be faulty?

 

[Anon0ne]

Have you tried to run a memory test to see if it might be faulty?

I tried yesterday and the memtest seem to pass, but I don't really want to risk corruption again. I was making sure I got a backup this time before testing memory.

/e retested memory and it crashed the PC several times. I transferred some memory from another server over to those slots, and it tests good. I am just gonna move the sticks around and hope this doesn't re-appear.