Upgrading kernel from 2.6.24-10-pve to 2.6.32-4-pve failed...

P

ps4allnl

New Member
Jun 27, 2011
5
0
1
Hi all,

My first post here, I hope my bad english is understandable to have a problem solved.
I'm using OVH's I7 with 8GB of memory (I7-T2 or something like that) which has been installed and delivered with OVH's changed Proxmox software. They only deliver it that way, but they don't give any support on software (which is quite strange for a (maybe little) problem like this.

Okay the problem;
I have been trying to upgrade everything, even the kernel by issuing the commands;
Code: 
aptitude update
aptitude safe-upgrade
aptitude install proxmox-ve-2.6.32
But after the reboot, it still seems to be running the proxmox-ve-2.6.24-10-pve kernel. After looking around here and there, I found out the file menu.lst was missing it by running the command dpkg-reconfigure pve-kernel-2.6.32-4-pve I got a error called
Code: 
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.".

After running the command mdadm --detail --scan >> /etc/mdadm/mdadm.conf
the right entries seemed to be added to the mdadm.conf file. After that I re-runned the command above (the dpkg-reconfigure one) and no error came out. After searching for the file menu.lst again, it still didn't found the filename. After that I found out I could also try to execute update-grub. After that command, the latest kernel has been added.

Now... normaly you should issue a reboot command to get the server rebooted with the latest kernel. But I would like to have a confirmation everything is configured the right way now and a server hang will be avoided now.


Some details which might be good to know;
Code: 
~# pveversion -v
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.32: 1.8-33
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.24-10-pve: 2.6.24-21
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.27-1pve1
vzdump: 1.2-13
vzprocps: 2.0.11-2
vzquota: 3.0.11-1dso1
pve-qemu-kvm: 0.14.1-1
ksm-control-daemon: 1.0-6

If more information is needed for answering if everything is okay to get the server rebooted, please let me know!


Regards,
Gerrit
 
Got it confirmed by a OVH employee;
------
HI,

yes this seems ok like this:
aptitude update
aptitude safe-upgrade
aptitude install proxmox-ve-2.6.32

mdadm --detail --scan >> /etc/mdadm/mdadm.conf
dpkg-reconfigure pve-kernel-2.6.32-4-pve
update-grub


Best regards,
OVH / A.
 
Hi,

I'm more or less in the same situation. So before proceeding with all those steps, did you find a solution to your crash?

thanks
 
Hi,

Well.... I just took another server at OVH for a short time and transfered all VM's to the new one. After that I did a re-install at OVH with the latest PVE, after that I also did a complete re-install of my DirectAdmin VM. And transfered the other VM's back to the i7 PVE-server. Since then all problems seem to be solved, now it's only time to wait untill there are new updates. If the problem returns It'll be the end of PVE for us. In that case we will go and try another VE because transfering, re-install, maintaining e.g. took us about 3 days.

If you have a OVH server, and got the money... you can order a Kimsufi 5G for a month (currently without setupcost) in that way you can transfer the backups from the main to a temporary server to re-install the main server even while all the VM's keep on running.
 
You must log in or register to reply here.
Top Bottom