[SOLVED] how to install an old kernel and boot on it, when your system have proxmox-auto-removal script

hi,
JOduMonT said:
@proxmox team, good job by including an autoremove script while we rebuild kernel
Code: 
Running hook script 'proxmox-auto-removal'..
I mean, how I could reinstall an old kernel without being auto remove by your script
since new kernel don't support my PCI pass-through ????
https://forum.proxmox.com/threads/u...o-drive-since-update.99769/page-2#post-438953
Click to expand...
which kernel are you trying to install? and which one do you have? if you're installing a kernel from our repository that script won't trigger ;)

could you post the full output?
 
I tried pve-kernel-5.11.22-7-pve and pve-kernel-5.11.22-6-pve with their headers but non of them appear with the command


root@pve:~# pve-efiboot-tool kernel list Manually selected kernels: None. Automatically selected kernels: 5.13.19-1-pve 5.13.19-2-pve root@pve:~# proxmox-boot-tool refresh Running hook script 'proxmox-auto-removal'.. Running hook script 'zz-proxmox-boot'.. Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace.. Copying and configuring kernels on /dev/disk/by-uuid/E916-C1BC Copying kernel and creating boot-entry for 5.13.19-1-pve Copying kernel and creating boot-entry for 5.13.19-2-pve Copying and configuring kernels on /dev/disk/by-uuid/E917-1A91 Copying kernel and creating boot-entry for 5.13.19-1-pve Copying kernel and creating boot-entry for 5.13.19-2-pve root@pve:~# apt install pve-kernel-5.11.22-7-pve Reading package lists... Done Building dependency tree... Done Reading state information... Done pve-kernel-5.11.22-7-pve is already the newest version (5.11.22-12). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@pve:~# apt install pve-kernel-5.11.22-7-pve
 
JOduMonT said:
I tried pve-kernel-5.11.22-7-pve and pve-kernel-5.11.22-6-pve with their headers but non of them appear with the command
Click to expand...
are you using grub or systemd-boot on this server? [0] what does proxmox-boot-tool status say?

JOduMonT said:
Copying and configuring kernels on /dev/disk/by-uuid/E916-C1BC
Click to expand...
what do you get with: ls -al /dev/disk/by-uuid/E916-C1BC /dev/disk/by-uuid/E917-1A91?

could you also post the output from pveversion -v and lsblk -f?

[0]: https://pve.proxmox.com/wiki/Host_Bootloader
 
Hey thanks for your quick respond ;)

systemd-boot
root@pve:~# proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. System currently booted with uefi E916-C1BC is configured with: uefi (versions: 5.13.19-1-pve, 5.13.19-2-pve) E917-1A91 is configured with: uefi (versions: 5.13.19-1-pve, 5.13.19-2-pve)

ls -al /dev/disk/by-uuid/E916-C1BC /dev/disk/by-uuid/E917-1A91
- which are under a zfs raid on SSD (sd[a,b]2)

pveversion -v
Code: 
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-8 (running version: 7.1-8/5b267f33)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-6-pve: 5.11.22-11
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3

lsblk -f
Code: 
NAME        FSTYPE            FSVER LABEL                 UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                                                          
├─sda1                                                                                                      
├─sda2      vfat              FAT32                       E916-C1BC                                          
└─sda3      zfs_member        5000  rpool                 3548219370305769142                                
sdb                                                                                                          
├─sdb1                                                                                                      
├─sdb2      vfat              FAT32                       E917-1A91                                          
└─sdb3      zfs_member        5000  rpool                 3548219370305769142                                
sdc                                                                                                          
├─sdc1      linux_raid_member 1.2   unassigned-hostname:2 d50ebd65-6384-7c8c-ed06-00db29c62000              
└─sdc9                                                                                                      
sdd
sdd                                                                                                          
├─sdd1      linux_raid_member 1.2   unassigned-hostname:2 d50ebd65-6384-7c8c-ed06-00db29c62000              
└─sdd9                                                                                                      
zd0                                                                                                          
zd16                                                                                                        
zd32                                                                                                        
├─zd32p1                                                                                                    
└─zd32p2    BitLocker         2                                                                              
zd48                                                                                                        
└─zd48p1    crypto_LUKS       1                           486a0071-66ca-4baa-b8b7-f822f810a5c6              
zd64                                                                                                        
zd80                                                                                                        
├─zd80p1    vfat              FAT32                       AAE9-49DF  
zd64                                                                                                        
zd80                                                                                                        
├─zd80p1    vfat              FAT32                       AAE9-49DF                                          
├─zd80p2                                                                                                    
├─zd80p3    ntfs                                          AE8AF73C8AF6FF9F                                  
└─zd80p4    ntfs                                          146E6FC96E6FA26A                                  
zd96                                                                                                        
├─zd96p1    vfat              FAT32                       1877-CDF1                                          
├─zd96p2                                                                                                    
├─zd96p3    BitLocker         2                                                                              
└─zd96p4    ntfs                                          4EF4B095F4B080AF  
zd112                                                                                                        
└─zd112p1   ext4              1.0                         7382c9cb-36f8-489c-b851-08c1dea15aa3              
zd128                                                                                                        
zd144                                                                                                        
zd160                                                                                                        
zd176                                                                                                        
nvme0n1                                                                                                      
├─nvme0n1p1 zfs_member        5000  nvme                  8444506637979312376                                
└─nvme0n1p9

and maybe before you ask

Code: 
pve-headers-5.11.22-6-pve/stable,now 5.11.22-11 amd64 [installed]
pve-headers-5.11.22-7-pve/stable,now 5.11.22-12 amd64 [installed]
pve-i18n/stable,now 2.6-2 all [installed]
pve-kernel-5.11.22-6-pve/stable,now 5.11.22-11 amd64 [installed]
pve-kernel-5.11.22-7-pve/stable,now 5.11.22-12 amd64 [installed]
pve-kernel-5.13/stable,now 7.1-5 all [installed]
pve-kernel-5.13.19-1-pve/stable,now 5.13.19-3 amd64 [installed]
pve-kernel-5.13.19-2-pve/stable,now 5.13.19-4 amd64 [installed,automatic]

so yes, the kernel I expect are installed ;)
 
Last edited:
thank you for the outputs :)

could you mount the EFI partitions manually and check if those kernels are really there?
just run find on the mountpoint, and then please post the output here
 
oguz said:
if those kernels are really there?
Click to expand...
yes there are:
Code: 
root@pve:~# ls /boot/
config-5.11.22-6-pve  grub                      pve                       vmlinuz-5.11.22-6-pve
config-5.11.22-7-pve  initrd.img-5.11.22-6-pve  System.map-5.11.22-6-pve  vmlinuz-5.11.22-7-pve
config-5.13.19-1-pve  initrd.img-5.11.22-7-pve  System.map-5.11.22-7-pve  vmlinuz-5.13.19-1-pve
config-5.13.19-2-pve  initrd.img-5.13.19-1-pve  System.map-5.13.19-1-pve  vmlinuz-5.13.19-2-pve
efi                   initrd.img-5.13.19-2-pve  System.map-5.13.19-2-pve

but I tried a reboot, and they don't show up as a choice.
 
Last edited:
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom