Barracuda Solution Center
After installing Proxmox with SDR, the /boot directory is almost empty: kernel and related files are missing. How to get the missing files?
This is due to a bug in the AppliPACK. To fix this you have to log in to the command line as root user and follow the steps below:
- Add the following line in the
/etc/fstab
file:
echo "/dev/sda3 /boot ext4 defaults 0 1" >> /etc/fstab
- Unmount
/boot/efi
directory with:
umount /boot/efi
- Mount all file systems again:
mount -a
Proxmox was installed with SDR and after an update the newly installed kernel is not loaded. How can this be fixed?
This is due to a bug in the AppliPACK. To fix this you have to log in to the command line as root user and follow the steps below:
Find out the version of the new kernel. To do this, find the highest version of a vmlinuz file in the
/boot
directory and note it (e.g. 4.15.18-20-pve).Mount partition
/dev/sda3
to temporary location:
mount /dev/sda3 /mnt
- Unmount EFI-Partition:
umount /boot/efi
- Copy the complete contents of
/boot
to/dev/sda3
:
cp -a /boot/* /mnt/
- Unmount partition sda3:
umount /mnt
- Delete contents of
/boot
rm -Rf /boot/*
- Add line to the
/etc/fstab
file:
echo "/dev/sda3 /boot ext4 defaults 0 1" >> /etc/fstab
- Mount all file systems again:
mount -a
- PostInstall the kernel manually. Use the version of the latest kernel instead of KVERSION:
/var/lib/dpkg/info/pve-kernel-KVERSION.postinst configure
- Activate kernel with reboot
reboot