Proxmox keeps crashing

[synden]

Hey!
My Proxmox crashes now and then. Have mounted disks directly to a VM, where I run Samba and NFS. Two of the drives are NTFS and two disks are ext4. I can access them etc and everything works fine, I think. But sometimes, once a day it seems crash. See picture below. Is it the hdds? Or is there something else that is the problem?


The computer's CPU http://ark.intel.com/sv/products/777...Cache-3_50-GHz
"Intel® Virtualization Technology for Directed I / O = No" (If that makes any sense.)

Anyone know the reason for this? And how do I solve it?
When I get home I'll try and update the kernel and see if that helps If not, I will try and to run Proxmox without the Samba Vm where I've mounted the 4 internal hdds and see if it changes. I will also try without the hdds mounted and see if it makes any difference. Would be nice to be able to solve this without reinstalling everything. Shall I try to mount the hdds directly inside Proxmox and let the VMs access the drives that way? And how do I do that? Without losing my data/wares on those 4 internal hdds.

Thanks!

 

[synden]

I'm alway having problems with VMs that freezes. Anyway knows what these problems can be? What logs do you guys need to help me solve this problem? Tired of Proxmox and the VMs keep crashing

 

[mir]

How are you able to mount disks directly without a CPU supporting VTd?

PS. your link is broken.

 

[mir]

What does pveversion -v show?

 

[synden]

How are you able to mount disks directly without a CPU supporting VTd?


PS. your link is broken.

I'm mounting the hard drives inside one of my VMs which is running Samba server.
I followed this: https://pve.proxmox.com/wiki/Physical_disk_to_kvm using lshw.

The link was ark.intel.com/sv/products/77769/Intel-Core-i3-4330-Processor-4M-Cache-3_50-GHz (Just a site with information about my Intel i3 4330 CPU showing that it has:
"Intel® Virtualization Technology for Directed I / O = No" if that does make any sense for this problem.
Do you need some log files to solve my problem easier? Not so good at either Proxmox or Linux

What does pveversion -v show?

proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-37-pve)
pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e)
pve-kernel-2.6.32-37-pve: 2.6.32-147
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.3-20
pve-firmware: 1.1-3
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-31
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-12
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

 

[spirit]

Hi,
maybe can you try with pve-kernel 3.10 ?

it should not be a problem to use disk directly. (but I'm not sure you'll have big speed difference vs .raw files)

also, you can try to upgrade you bios (which upgrade also cpu microcodes). I have had some crash problem like that in the past.

and check in your bios that you don't have any saving power feature enabled (dynamic frequency, cores idling,...).

 

[mir]

And also disable all C-state features in the BIOS.

 

[synden]

Hi,
maybe can you try with pve-kernel 3.10 ?

it should not be a problem to use disk directly. (but I'm not sure you'll have big speed difference vs .raw files)

also, you can try to upgrade you bios (which upgrade also cpu microcodes). I have had some crash problem like that in the past.

and check in your bios that you don't have any saving power feature enabled (dynamic frequency, cores idling,...).

okey i will check bios today thanks for the top! it could be something in that.

How do i upgrade pve-kernel to 3.10?

 

[udo]

How do i upgrade pve-kernel to 3.10?

Hi,

apt-get install pve-kernel-3.10.0-8-pve

Udo

 

[synden]

Now I've upgrade the kernel to 3.10.0-11. It didnt find the -8 version. Does it matter?

pveversion -v now:
proxmox-ve-2.6.32: 3.3-147 (running kernel: 3.10.0-3-pve)
pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e)
pve-kernel-2.6.32-37-pve: 2.6.32-147
pve-kernel-3.10.0-3-pve: 3.10.0-11
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.3-20
pve-firmware: 1.1-3
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-31
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-12
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1


I will see how everything is working and. I will check BIOS tomorrow also

 

[udo]

Now I've upgrade the kernel to 3.10.0-11. It didnt find the -8 version. Does it matter?

pveversion -v now:
proxmox-ve-2.6.32: 3.3-147 (running kernel: 3.10.0-3-pve)
pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e)
pve-kernel-2.6.32-37-pve: 2.6.32-147
pve-kernel-3.10.0-3-pve: 3.10.0-11
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.3-20
pve-firmware: 1.1-3
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-31
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-12
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1


I will see how everything is working and. I will check BIOS tomorrow also

Hi,
have you done an "apt-get update" before?

http://download.proxmox.com/debian/dists/wheezy/pve-no-subscription/binary-amd64/pve-kernel-3.10.0-8-pve_3.10.0-30_amd64.deb

Udo

 

[synden]

Hi,
have you done an "apt-get update" before?

http://download.proxmox.com/debian/dists/wheezy/pve-no-subscription/binary-amd64/pve-kernel-3.10.0-8-pve_3.10.0-30_amd64.deb

Udo

Yeah I did. I will try again with that code. with -30. and tomorrow i will check the BIOS.

EDIT: Check post above. For some reason my new post came above this one.

 

[synden]

Now I've reinstalled my Proxmox and had one crash like my first picture. It took a few hours before it came.
I think the server was idle and no one was using the server.

When I reinstalled Proxmox I ran update and upgrade. When the crash happened I ran the apt-get install pve-kernel command and update the server to 3.10.-30. So now I will see if anything happens.

proxmox-ve-2.6.32: 3.3-147 (running kernel: 3.10.0-8-pve)
pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e)
pve-kernel-3.10.0-8-pve: 3.10.0-30
pve-kernel-2.6.32-37-pve: 2.6.32-147
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.3-20
pve-firmware: 1.1-3
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-31
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-12
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

Though one of my VMs freezes for some reason. Can I check the reason for it? On that server I run Ubuntu Server 14.04.2 with docker and the needo37/plex.

Would love if someone could help me fix this damn problem so I can have a stable server. lol.
Do you guys need some logfile or something to figure out the problems I have? I will try and update the BIO and check the power savings.
I have motherboard: Gigabyte H87M-D3H. If anyone knows the right power settings to change, let me know. Like dynamic frequency, cores idling and C-state.

 

[mir]

I am pretty sure that what you are facing is bad hardware: CPU, RAM, or motherboard. Either alone or in combination.

 

[synden]

I am pretty sure that what you are facing is bad hardware: CPU, RAM, or motherboard. Either alone or in combination.

i will run a ram test today.
i dont think it's Motherboard or cpu. maybe ram

 

[synden]

It seems it war my ram. I am running the server with 2 8GB RAM from my main computer in the server and it works like a charm. Seems that is one or more ram sticks that the server doesn't like so I will run memtest on those three ram sticks in my main computer.

Think this is solved now. Thanks guys for you help