Search results

Seems the update Fixed it.... THANK YOU. I had an error in my repos that I never noticed. I run By weekly updates so I assumed it was up to date... BUT NOPE... The VM has not crashed since the Updates...

No backups running at the time. Thank you for pointing out that my PVE was quite old... I found and error in my repo. Updating now...

Crashed again.... Aug 25 23:47:50 novafreakvm kernel: mce: [Hardware Error]: Machine check events logged Aug 25 23:47:50 novafreakvm kernel: Memory failure: 0x644e057: Sending SIGBUS to kvm:1065790 due to hardware memory corruption Aug 25 23:47:50 novafreakvm kernel: Memory failure: 0x644e057...

AN update... I thought that I have disabled backups for that VM, but it turned out that I hadn't Since stopping backups... the server has not crashed...

Aug 22 23:13:01 novafreakvm systemd[1]: Finished Proxmox VE replication runner. Aug 22 23:13:08 novafreakvm kernel: mce: [Hardware Error]: Machine check events logged Aug 22 23:13:08 novafreakvm kernel: Memory failure: 0xd9ebcb: Sending SIGBUS to kvm:2288 due to hardware memory corruption Aug 22...

No memory errors

looking good so far...

Alright, this should finish some time next week... lol

thank you... I had a mishap while posting and did not know if my post made it t or not. I searched and did not see it so I submitted another.

Could it still be the hardware memory when only one of my Linux VMs is exhibiting this behavior?

I have an Ubuntu 20.04.6 LTS VM: Host is a Dell PowerEdge r820 4 X Intel(R) Xeon(R) CPU E5-4640 0 @ 2.40GHz 48 X 16gb dual rank 1333 MHz = 768 GB RAM Promox - 5.11.22-4-pve #1 SMP PVE 5.11.22-8 the syslog on host: Aug 17 23:16:24 novafreakvm kernel: mce: [Hardware Error]: Machine check...

I have a Ubuntu 20.04.6 LTS vm with the following hardware config: PRXMOX VE - 5.11.22-4-pve #1 SMP PVE 5.11.22-8 running on a Dell PowerEdge R820 with 4 X Intel(R) Xeon(R) CPU E5-4640 0 @ 2.40GHz with 48 X 16GB 1333 MHz RAM for total of 768GB I do have 2 other vms running on this server that...

It was in a Hardware Raid 5... I ended up mounting the pool in read only and copying the VM Disks off to another server. Then I rebuilt my VE server and blew away the ZFS and mounted the disk as local storage... Then I recreated the VMs from the VM conf files that I also copied off... and then I...

Ahhhh... Ok... I will do some more reading and research before I rebuild with this server.

YES.... I found another thread and started commenting.... not noticing it was marked resolved... Luckily someone helped me :) thank you!

The Pool is is striped across 6 disks on a R5 ... Hardware RAID... PERC card...

well... i tried something off the cuff here... after mounting my POOL as read only... I was able to CLONE my VMs :D and they start up just fine... Now I will blow away the old ones and do a fresh install of PROXMOX... Start over and not make the same mistakes again... Like not having...

Thought I would also add that I was able to figure out a way to mount the disk as read only and copy data from them.... root@novafreakVM:/dev/zvol/Pool_1# ls -w 1 vm-100-disk-0 vm-100-disk-0-part1 vm-100-disk-0-part2 vm-110-disk-0 vm-110-disk-0-part1 vm-110-disk-0-part2 vm-110-disk-1...

I am not sure which file is the .RAW file... looks like each "Disk" has a file for each partition maybe?

I was able to use the copy command,,,, will this be enough to restore these machines to a new Host? root@novafreakVM:/dev/zvol/Pool_1# ls vm-100-disk-0 vm-100-disk-0-part1 vm-100-disk-0-part2 vm-110-disk-0 vm-110-disk-0-part1 vm-110-disk-0-part2 vm-110-disk-1 vm-120-disk-0...