LogFiles and kernal corupt error + vm's don't start the windows is damaged

T

Timmm

New Member
May 8, 2015
17
0
1
Hi,

I have three errros on my server after reboot, i'am going to the datacenter for the server. He runs now on a old outdated kernal of proxmox

my pveversion :



root@hosted-by:~# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-19-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-37-pve: 2.6.32-150
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-11-pve: 2.6.32-66
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-17
qemu-server: 3.1-8
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
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: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
root@hosted-by:~# mount -t ext2 /dev/hdb1 /data
mount: special device /dev/hdb1 does not exist
root@hosted-by:~# mount /dev/sdb1 /data
root@hosted-by:~# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-19-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-37-pve: 2.6.32-150
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-11-pve: 2.6.32-66
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-17
qemu-server: 3.1-8
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
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: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
root@hosted-by:~#

The server don't work and the windows don't work can please everybody help my on this problem thank you.
 
Timmm said:
Hi,

I have three errros on my server after reboot, i'am going to the datacenter for the server. He runs now on a old outdated kernal of proxmox

my pveversion :



root@hosted-by:~# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-19-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-37-pve: 2.6.32-150
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-11-pve: 2.6.32-66
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-17
qemu-server: 3.1-8
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
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: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
root@hosted-by:~# mount -t ext2 /dev/hdb1 /data
mount: special device /dev/hdb1 does not exist
root@hosted-by:~# mount /dev/sdb1 /data
root@hosted-by:~# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-19-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-37-pve: 2.6.32-150
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-11-pve: 2.6.32-66
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-17
qemu-server: 3.1-8
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
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: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
root@hosted-by:~#

The server don't work and the windows don't work can please everybody help my on this problem thank you.
Click to expand...
Hi,
there are one issue visible:

You don't run the latest kernel, but there is an 2.6.32-37 installed
this shows that you don't upgraded grub! Do you have done and "apt-get dist-upgrade", or an "apt-get upgrade" only?


Do you use the pve-nosubscription-repro?

Udo

Hmm, second view: your kernel and pve-manager 3.1 don't fit together! how do you get the 2.6.32-37 kernel?? This is not the real problem, but shows that it's don't be an clean system.
 
Last edited:
Yes, Its works butt now have a problem with de ip config the vm don't network i have restart the network service.
 
Timmm said:
Yes, Its works butt now have a problem with de ip config the vm don't network i have restart the network service.
Click to expand...

Hi,
you newer wrote, from which version you start your upgrade...

Long ago, there was an change in the network-syntax. Perhaps you must look for that.

Save your config (like "cp -p /etc/pve/qemu-server/*.conf /root/" ) and remove the network from one VM. Assign the network again and see if it's work and look for differences in the config-file.

On windows-VMs take the same mac-address+ driver (like e1000/virtio).

Udo
 
You must log in or register to reply here.
Top Bottom