Update kernel freeze

Jorge Teixeira

Renowned Member
Oct 30, 2016
36
12
73
55
Hi.
When upgrading the new kernel today, it froze at generating initramfs and now when i try again, it says "could not get lock /var/lib/dpkg/lock - open ". I have not yet reboot as i am afraid of not being able to do it any more. What should i do?
 
what happened after the "freeze" (did you kill the upgrade with ctrl+c? where there any error messages? ...)? is there still a dpkg process running? if you have a separate /boot, is there still enough free space there?
 
what happened after the "freeze" (did you kill the upgrade with ctrl+c? where there any error messages? ...)? is there still a dpkg process running? if you have a separate /boot, is there still enough free space there?
Hi Fabian.
Thanks for the quick reply. After the freeze i issued a "pkill dpkg". I do not have a separate boot and my boot ssd is 128GB. Right now everything is running fine but i' am afraid of rebooting.
 
what happened after the "freeze" (did you kill the upgrade with ctrl+c? where there any error messages? ...)? is there still a dpkg process running? if you have a separate /boot, is there still enough free space there?
I have done a "dpkg --configure -a" command and it seems that it instaled the kernel just fine this time. Also the error with the lock is gone. Do you think its safe to reboot?
 
I have done a "dpkg --configure -a" command and it seems that it instaled the kernel just fine this time. Also the error with the lock is gone. Do you think its safe to reboot?

if you have local access or iKVM you should always be able to boot using the previous kernel/initrd combination if the new one is not correctly installed. just select the old one in the advanced options submenu of the Grub boot menu.

you can also re-install the pve-kernel-XXX package to make sure ("apt-get install --reinstall pve-kernel-4.4.59-1-pve" in this case).
 
if you have local access or iKVM you should always be able to boot using the previous kernel/initrd combination if the new one is not correctly installed. just select the old one in the advanced options submenu of the Grub boot menu.

you can also re-install the pve-kernel-XXX package to make sure ("apt-get install --reinstall pve-kernel-4.4.59-1-pve" in this case).
I have reinstaled the kernel and it worked. Many thanks .
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!