Proxmox Nodes crashed during vm backup

[ulf.kosack]

Hello,

in the last 6 months I had two node crashes during a vm backup. The only chance to rerun the node was to reset it. After start I had to unlock the vm, that was backuped before the crash.

Before reset I only see this console output:



The system consists of one node with

• pve-manager/3.4-11/6502936f (running kernel: 2.6.32-43-pve)
  
• only local storage via RAID-Controller Adaptec 6805

VMs and backup are located on different mounts:
/dev/mapper/pvelocal-pvebackups 3.0T 2.1T 755G 74% /var/backups/pvebackup
/dev/mapper/pvelocal-pveImages 4.0T 1.1T 2.8T 27% /var/lib/vz/lvmImages

The raid controller report no errors (via monitoring). The wellknown logfiles consists no informational data for me. I backuped some logs on my computer to give information, if you need.

Can someone help to find the error?

Thanks
Ulf

 

[dietmar]

I just upload a new kernel including the latest aacraid driver from adaptec to pvetest.
Please can you test if that helps?

# wget http://download1.proxmox.com/debian...pve-kernel-2.6.32-44-pve_2.6.32-170_amd64.deb
# dpkg -i pve-kernel-2.6.32-44-pve_2.6.32-170_amd64.deb

 

[ulf.kosack]

Sorry, yesterday to late seen. I will test on thursday evening. Too much impact, if it goes wrong, because I'm not on the location every day. Is this ok for you?

Thanks.
Ulf

 

[dietmar]

Sorry, yesterday to late seen. I will test on thursday evening. Too much impact, if it goes wrong, because I'm not on the location every day. Is this ok for you?

Sure - thanks!

 

[ulf.kosack]

The file is gone . I only get 404 on download.

 

[tom]

The file is gone . I only get 404 on download.

go for:

# wget http://download.proxmox.com/debian/...pve-kernel-2.6.32-44-pve_2.6.32-171_amd64.deb
# dpkg -i pve-kernel-2.6.32-44-pve_2.6.32-171_amd64.deb

 

[ulf.kosack]

Thanks a lot. Kernel is installed, all vm's are up and running. Next backup is scheduled for the next weekend.

I will report

Best regards
Ulf

 

[ulf.kosack]

No further crashes since the new kernel. I hope this fixed the problem and the next kernel releases will include this driver.

Thanks for the fast solution.
Ulf