[SOLVED] Error in kernel udate (5.3.18-3 to 5.4.65-1) due to failed fsck on EFI partition

H

HrvojeS

New Member
Jan 16, 2020
6
0
1
57
Hello,

I've ran an update this morning (pve-no-subscription channel) and got some upgrade errors in logs. Not sure where to start troubleshooting as I don't think reboot is wise at this point. I wouldn't like to reinstall if not needed. Any help would be greatly appreciated.

Code: 
Starting system upgrade: apt-get dist-upgrade
...
The following NEW packages will be installed:
  libfuse3-3 libproxmox-backup-qemu0 libqrencode4 libyaml-0-2
  libyaml-libyaml-perl proxmox-archive-keyring proxmox-backup-client
  pve-kernel-5.4 pve-kernel-5.4.65-1-pve qrencode
The following packages will be upgraded:
  apt apt-utils base-files bind9-host ca-certificates corosync dbus dnsutils
  fuse ifupdown2 iputils-ping libapt-inst2.0 libapt-pkg5.0 libbind9-161
  libcfg7 libcmap4 libcorosync-common4 libcpg4 libcups2 libdbus-1-3
  libdns-export1104 libdns1104 libfreetype6 libfuse2 libgnutls30 libgnutlsxx28
  libirs161 libisc-export1100 libisc1100 libisccc161 libisccfg163 libjson-c3
  libknet1 libldap-2.4-2 libldap-common liblwres161 libnss-systemd libnss3
  libnvpair1linux libpam-systemd libpango-1.0-0 libpangocairo-1.0-0
  libpangoft2-1.0-0 libperl5.28 libproxmox-acme-perl libpve-access-control
  libpve-cluster-api-perl libpve-cluster-perl libpve-common-perl
  libpve-guest-common-perl libpve-http-server-perl libpve-storage-perl
  libpython3.7 libpython3.7-minimal libpython3.7-stdlib libquorum5 libsystemd0
  libudev1 libunwind8 libuutil1linux libvotequorum8 libx11-6 libx11-data
  libx11-xcb1 libzfs2linux libzpool2linux linux-libc-dev lxc-pve lxcfs
  nfs-common nmap nmap-common perl perl-base perl-modules-5.28 postfix
  proxmox-ve proxmox-widget-toolkit pve-cluster pve-container pve-docs
  pve-edk2-firmware pve-firewall pve-firmware pve-ha-manager pve-i18n
  pve-kernel-helper pve-manager pve-qemu-kvm pve-xtermjs python3.7
  python3.7-minimal qemu-server spl systemd systemd-sysv tzdata udev vncterm
  zfs-initramfs zfs-zed zfsutils-linux
102 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
Need to get 198 MB of archives.
After this operation, 324 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://download.proxmox.com/debian/pve buster/pve-no-subscription amd64 libcorosync-common4 amd64 3.0.4-pve1 [7244 B]
...
Get:112 http://download.proxmox.com/debian/pve buster/pve-no-subscription amd64 zfs-zed amd64 0.8.4-pve2 [65.4 kB]                                                          
Fetched 198 MB in 30s (6604 kB/s)                                                                                                                                           
Reading changelogs... Done
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 57045 files and directories currently installed.)
Preparing to unpack .../base-files_10.3+deb10u6_amd64.deb ...
Unpacking base-files (10.3+deb10u6) over (10.3+deb10u3) ...
Setting up base-files (10.3+deb10u6) ...
Installing new version of config file /etc/debian_version ...
...
Unpacking zfs-zed (0.8.4-pve2) over (0.8.3-pve1) ...
Setting up perl-modules-5.28 (5.28.1-6+deb10u1) ...
Setting up pve-kernel-5.4.65-1-pve (5.4.65-1) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.4.65-1-pve /boot/vmlinuz-5.4.65-1-pve
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.4.65-1-pve /boot/vmlinuz-5.4.65-1-pve
update-initramfs: Generating /boot/initrd.img-5.4.65-1-pve
run-parts: executing /etc/kernel/postinst.d/pve-auto-removal 5.4.65-1-pve /boot/vmlinuz-5.4.65-1-pve
run-parts: executing /etc/kernel/postinst.d/zz-pve-efiboot 5.4.65-1-pve /boot/vmlinuz-5.4.65-1-pve
Re-executing '/etc/kernel/postinst.d/zz-pve-efiboot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/3682-D892
        Copying kernel and creating boot-entry for 5.3.18-3-pve
        Copying kernel and creating boot-entry for 5.4.65-1-pve
        Removing old version 5.3.13-1-pve
rm: cannot remove '/var/tmp/espmounts/3682-D892/EFI/proxmox/5.3.13-1-pve/initrd.img-5.3.13-1-pve': Read-only file system
run-parts: /etc/kernel/postinst.d/zz-pve-efiboot exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/pve-kernel-5.4.65-1-pve.postinst line 19.
dpkg: error processing package pve-kernel-5.4.65-1-pve (--configure):
 installed pve-kernel-5.4.65-1-pve package post-installation script subprocess returned error exit status 2
Setting up vncterm (1.6-2) ...
...
Setting up libdns-export1104 (1:9.11.5.P4+dfsg-5.1+deb10u2) ...
dpkg: dependency problems prevent configuration of pve-kernel-5.4:
 pve-kernel-5.4 depends on pve-kernel-5.4.65-1-pve; however:
  Package pve-kernel-5.4.65-1-pve is not configured yet.

dpkg: error processing package pve-kernel-5.4 (--configure):
 dependency problems - leaving unconfigured
Setting up iputils-ping (3:20180629-2+deb10u1) ...
...
Setting up fuse (2.9.9-1+deb10u1) ...
update-initramfs: deferring update (trigger activated)
Setting up libvotequorum8:amd64 (3.0.4-pve1) ...
...
Setting up nmap (7.70+dfsg1-6+deb10u1) ...
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on pve-kernel-5.4; however:
  Package pve-kernel-5.4 is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Setting up perl (5.28.1-6+deb10u1) ...
...
Running hook script 'zz-pve-efiboot'..
Re-executing '/etc/kernel/postinst.d/zz-pve-efiboot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/3682-D892
        Copying kernel and creating boot-entry for 5.3.18-3-pve
cp: preserving times for '/var/tmp/espmounts/3682-D892/EFI/proxmox/5.3.18-3-pve/vmlinuz-5.3.18-3-pve': Read-only file system
run-parts: /etc/initramfs/post-update.d//pve-efiboot-sync exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for rsyslog (8.1901.0-1) ...
Processing triggers for ca-certificates (20200601~deb10u1) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for pve-ha-manager (3.1-1) ...
Errors were encountered while processing:
 pve-kernel-5.4.65-1-pve
 pve-kernel-5.4
 proxmox-ve
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Your System is up-to-date

Seems you installed a kernel update - Please consider rebooting
this node to activate the new kernel.

Re-running update after above I got the following:

Code: 
apt-get update
Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
Hit:2 http://ftp.ca.debian.org/debian buster InRelease                                                                      
Hit:3 http://ftp.ca.debian.org/debian buster-updates InRelease                                                              
Hit:4 http://download.proxmox.com/debian/pve buster InRelease             
Get:5 http://security.debian.org buster/updates/main amd64 Packages [248 kB]
Get:6 http://security.debian.org buster/updates/main Translation-en [135 kB]
Fetched 449 kB in 4s (107 kB/s)                               
Reading package lists... Done
root@sv2:~# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  pve-kernel-5.3.13-1-pve
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up initramfs-tools (0.133+deb10u1) ...
update-initramfs: deferring update (trigger activated)
Setting up pve-kernel-5.4.65-1-pve (5.4.65-1) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.4.65-1-pve /boot/vmlinuz-5.4.65-1-pve
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.4.65-1-pve /boot/vmlinuz-5.4.65-1-pve
update-initramfs: Generating /boot/initrd.img-5.4.65-1-pve
run-parts: executing /etc/kernel/postinst.d/pve-auto-removal 5.4.65-1-pve /boot/vmlinuz-5.4.65-1-pve
run-parts: executing /etc/kernel/postinst.d/zz-pve-efiboot 5.4.65-1-pve /boot/vmlinuz-5.4.65-1-pve
Re-executing '/etc/kernel/postinst.d/zz-pve-efiboot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/3682-D892
    Copying kernel and creating boot-entry for 5.3.18-3-pve
cp: preserving times for '/var/tmp/espmounts/3682-D892/EFI/proxmox/5.3.18-3-pve/vmlinuz-5.3.18-3-pve': Read-only file system
run-parts: /etc/kernel/postinst.d/zz-pve-efiboot exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/pve-kernel-5.4.65-1-pve.postinst line 19.
dpkg: error processing package pve-kernel-5.4.65-1-pve (--configure):
 installed pve-kernel-5.4.65-1-pve package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of pve-kernel-5.4:
 pve-kernel-5.4 depends on pve-kernel-5.4.65-1-pve; however:
  Package pve-kernel-5.4.65-1-pve is not configured yet.

dpkg: error processing package pve-kernel-5.4 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on pve-kernel-5.4; however:
  Package pve-kernel-5.4 is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.4.65-1-pve
Running hook script 'zz-pve-efiboot'..
Re-executing '/etc/kernel/postinst.d/zz-pve-efiboot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/3682-D892
    Copying kernel and creating boot-entry for 5.3.18-3-pve
cp: preserving times for '/var/tmp/espmounts/3682-D892/EFI/proxmox/5.3.18-3-pve/vmlinuz-5.3.18-3-pve': Read-only file system
run-parts: /etc/initramfs/post-update.d//pve-efiboot-sync exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 pve-kernel-5.4.65-1-pve
 pve-kernel-5.4
 proxmox-ve
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Thank you in advance.
 
I should add some context to "read-only" filesystem above:

Code: 
/dev/disk/by-uuid/3682-D892

3682-D892 -> ../../nvme0n1p2

Disk model: INTEL SSDPEKKW010T7                 
Disklabel type: gpt
Device          Start        End    Sectors   Size Type
nvme0n1p1          34       2047       2014  1007K BIOS boot
nvme0n1p2        2048    1050623    1048576   512M EFI System
nvme0n1p3     1050624  104857600  103806977  49.5G Solaris /usr & Apple ZFS
nvme0n1p4   104859648 1953525134 1848665487 881.5G Solaris /usr & Apple ZFS
nvme0n1p5  1953525760 2000409230   46883471  22.4G Solaris /usr & Apple ZFS

Only partitions 3-5 are used for ZFS. Partition nvme0n1p2 doesn't seem to be mounted right now, so it is probably mounted by update process. Not sure why it's mounted in read-only mode.

Starting to look at logs...

Code: 
Nov 12 18:04:47 sv2 kernel: [4516939.767624] printk: systemd: 52 output lines suppressed due to ratelimiting
Nov 12 18:11:22 sv2 kernel: [4517334.631277] FAT-fs (nvme0n1p2): error, invalid access to FAT (entry 0x090e7f08)
Nov 12 18:11:22 sv2 kernel: [4517334.640868] FAT-fs (nvme0n1p2): Filesystem has been set read-only
Nov 12 18:12:34 sv2 kernel: [4517407.046563] kauditd_printk_skb: 2 callbacks suppressed
Nov 12 18:12:34 sv2 kernel: [4517407.046592] audit: type=1400 audit(1605222754.654:199): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/bin/lxc-start" pid=9988 comm="apparmor_parser"
Nov 12 18:12:37 sv2 kernel: [4517409.562984] audit: type=1400 audit(1605222757.167:200): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="lxc-container-default" pid=10080 comm="apparmor_parser"
Nov 12 18:12:37 sv2 kernel: [4517409.586298] audit: type=1400 audit(1605222757.171:201): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="lxc-container-default-cgns" pid=10080 comm="apparmor_parser"
Nov 12 18:12:37 sv2 kernel: [4517409.611736] audit: type=1400 audit(1605222757.175:202): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="lxc-container-default-with-mounting" pid=10080 comm="apparmor_parser"
Nov 12 18:12:37 sv2 kernel: [4517409.629926] audit: type=1400 audit(1605222757.179:203): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="lxc-container-default-with-nesting" pid=10080 comm="apparmor_parser"
Nov 12 18:12:45 sv2 kernel: [4517417.374786] audit: type=1400 audit(1605222764.981:204): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/bin/lxc-start" pid=15352 comm="apparmor_parser"
Nov 12 18:12:45 sv2 kernel: [4517417.487330] audit: type=1400 audit(1605222765.093:205): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="lxc-container-default" pid=15426 comm="apparmor_parser"
Nov 12 18:12:45 sv2 kernel: [4517417.510974] audit: type=1400 audit(1605222765.093:206): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="lxc-container-default-cgns" pid=15426 comm="apparmor_parser"
Nov 12 18:12:45 sv2 kernel: [4517417.531436] audit: type=1400 audit(1605222765.093:207): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="lxc-container-default-with-mounting" pid=15426 comm="apparmor_parser"
Nov 12 18:12:45 sv2 kernel: [4517417.556302] audit: type=1400 audit(1605222765.093:208): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="lxc-container-default-with-nesting" pid=15426 comm="apparmor_parser"
Nov 12 18:12:46 sv2 kernel: [4517418.825477] new mount options do not match the existing superblock, will be ignored
Nov 12 18:17:49 sv2 kernel: [4517721.756207] FAT-fs (nvme0n1p2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Nov 12 18:17:49 sv2 kernel: [4517721.796432] FAT-fs (nvme0n1p2): error, fat_free_clusters: deleting FAT entry beyond EOF
Nov 12 18:17:49 sv2 kernel: [4517721.807202] FAT-fs (nvme0n1p2): Filesystem has been set read-only
Nov 13 09:23:13 sv2 kernel: [4572044.989320] FAT-fs (nvme0n1p2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Nov 13 09:23:13 sv2 kernel: [4572045.020708] FAT-fs (nvme0n1p2): error, fat_free_clusters: deleting FAT entry beyond EOF
Nov 13 09:23:13 sv2 kernel: [4572045.033059] FAT-fs (nvme0n1p2): Filesystem has been set read-only
Nov 13 09:25:15 sv2 kernel: [4572167.534933] FAT-fs (nvme0n1p2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Nov 13 09:25:15 sv2 kernel: [4572167.564458] FAT-fs (nvme0n1p2): error, fat_free_clusters: deleting FAT entry beyond EOF
Nov 13 09:25:15 sv2 kernel: [4572167.576859] FAT-fs (nvme0n1p2): Filesystem has been set read-only

Code: 
fsck /dev/disk/by-uuid/3682-D892
fsck from util-linux 2.33.1
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
FATs differ but appear to be intact. Use which FAT ?
1) Use first FAT
2) Use second FAT
? 1
Cluster 12286 out of range (89676075 > 130813). Setting to EOF.
Cluster 12287 out of range (41721404 > 130813). Setting to EOF.
...
...
Cluster 51836 out of range (45421594 > 130813). Setting to EOF.
Cluster 51837 out of range (204791253 > 130813). Setting to EOF.
/EFI/proxmox/5.3.18-3-pve/vmlinuz-5.3.18-3-pve
  Contains a free cluster (85115). Assuming EOF.
/EFI/proxmox/5.3.18-3-pve/vmlinuz-5.3.18-3-pve
  File size is 11630976 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/EFI/proxmox/5.3.18-3-pve/initrd.img-5.3.18-3-pve
  Contains a free cluster (87955). Assuming EOF.
/EFI/proxmox/5.3.18-3-pve/initrd.img-5.3.18-3-pve
  File size is 41617836 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/loader/entries/proxmox-5.3.18-3-pve.conf
  Contains a free cluster (98116). Assuming EOF.
/loader/entries/proxmox-5.3.18-3-pve.conf
  File size is 219 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
Reclaimed 36991 unused clusters (151515136 bytes).
Free cluster summary wrong (92142 vs. really 120613)
1) Correct
2) Don't correct
? 1
Perform changes ? (y/n) y
/dev/nvme0n1p2: 20 files, 10199/130812 clusters

I then mounted /dev/disk/by-uuid/3682-D892 to /tmp/test to double check.

Code: 
.
./EFI
./EFI/proxmox
./EFI/proxmox/5.4.65-1-pve
./EFI/proxmox/5.4.65-1-pve/vmlinuz-5.4.65-1-pve
./EFI/proxmox/5.4.65-1-pve/initrd.img-5.4.65-1-pve
./EFI/proxmox/5.3.13-1-pve
./EFI/proxmox/5.3.13-1-pve/initrd.img-5.3.13-1-pve
./EFI/proxmox/5.3.18-3-pve
./EFI/proxmox/5.3.18-3-pve/vmlinuz-5.3.18-3-pve
./EFI/proxmox/5.3.18-3-pve/initrd.img-5.3.18-3-pve
./EFI/systemd
./EFI/systemd/systemd-bootx64.efi
./EFI/BOOT
./EFI/BOOT/BOOTX64.EFI
./loader
./loader/entries
./loader/entries/proxmox-5.4.65-1-pve.conf
./loader/entries/proxmox-5.3.13-1-pve.conf
./loader/entries/proxmox-5.3.18-3-pve.conf
./loader/loader.conf

Re-ran upgrade and think I should be good to go...

Code: 
The following package was automatically installed and is no longer required:
  pve-kernel-5.3.13-1-pve
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up initramfs-tools (0.133+deb10u1) ...
update-initramfs: deferring update (trigger activated)
Setting up pve-kernel-5.4.65-1-pve (5.4.65-1) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.4.65-1-pve /boot/vmlinuz-5.4.65-1-pve
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.4.65-1-pve /boot/vmlinuz-5.4.65-1-pve
update-initramfs: Generating /boot/initrd.img-5.4.65-1-pve
run-parts: executing /etc/kernel/postinst.d/pve-auto-removal 5.4.65-1-pve /boot/vmlinuz-5.4.65-1-pve
run-parts: executing /etc/kernel/postinst.d/zz-pve-efiboot 5.4.65-1-pve /boot/vmlinuz-5.4.65-1-pve
Re-executing '/etc/kernel/postinst.d/zz-pve-efiboot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/3682-D892
    Copying kernel and creating boot-entry for 5.3.18-3-pve
    Copying kernel and creating boot-entry for 5.4.65-1-pve
    Removing old version 5.3.13-1-pve
Copying and configuring kernels on /dev/disk/by-uuid/3683-454A
    Copying kernel and creating boot-entry for 5.3.18-3-pve
    Copying kernel and creating boot-entry for 5.4.65-1-pve
    Removing old version 5.3.13-1-pve
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 5.4.65-1-pve /boot/vmlinuz-5.4.65-1-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.65-1-pve
Found initrd image: /boot/initrd.img-5.4.65-1-pve
Found linux image: /boot/vmlinuz-5.3.18-3-pve
Found initrd image: /boot/initrd.img-5.3.18-3-pve
Found linux image: /boot/vmlinuz-5.3.13-1-pve
Found initrd image: /boot/initrd.img-5.3.13-1-pve
Found linux image: /boot/vmlinuz-5.3.10-1-pve
Found initrd image: /boot/initrd.img-5.3.10-1-pve
Found memtest86+ image: /ROOT/pve-1@/boot/memtest86+.bin
Found memtest86+ multiboot image: /ROOT/pve-1@/boot/memtest86+_multiboot.bin
Adding boot menu entry for EFI firmware configuration
done
Setting up pve-kernel-5.4 (6.2-7) ...
Setting up proxmox-ve (6.2-2) ...
Removing obsolete conffile /etc/apt/trusted.gpg.d/proxmox-ve-release-5.x.gpg ...
Removing obsolete conffile /etc/apt/trusted.gpg.d/proxmox-ve-release-6.x.gpg ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.4.65-1-pve
Running hook script 'zz-pve-efiboot'..
Re-executing '/etc/kernel/postinst.d/zz-pve-efiboot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/3682-D892
    Copying kernel and creating boot-entry for 5.3.18-3-pve
    Copying kernel and creating boot-entry for 5.4.65-1-pve
Copying and configuring kernels on /dev/disk/by-uuid/3683-454A
    Copying kernel and creating boot-entry for 5.3.18-3-pve
    Copying kernel and creating boot-entry for 5.4.65-1-pve

Will restart/update as soon as I verify all the backups are okay...

Update:
Restarted without a hitch.
 
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