Issue with upgrading pve-firmware

[fabio.rodo]

Hi there,

I'm quite new here, so apologies in advance if I missed providing any necessary details.

I have a mini PC running Proxmox (with one VM and a few LXC containers).

I've been experiencing issues with updates. Specifically, the upgrade process via the UI always results in a host reboot.

After several attempts, I managed to upgrade all packages except for pve-firmware. Whenever I try to update it, the host reboots unexpectedly.

Additionally, when I try to install a new LXC container (e.g., KUMA UPTIME), I encounter the following error:

[ERROR] in line 164: exit code 0: while executing command apt-get install -y figlet &> /dev/null

Could someone point me in the right direction to resolve these issues?

Thanks in advance!

 

[UdoB]

[ERROR] in line 164: exit code 0: while executing command apt-get install -y figlet &> /dev/null

You have installed packages that do not belong to a standard PVE installation. That's usually a bad idea, especially for beginners. Did you use external scripts for this?

the upgrade process via the UI always results in a host reboot.

Please start by giving us some information, like the copy-n-pasted output of some commands, run on a PVE host:

PVE System information:

• pveversion -v
• head -n -0 /etc/apt/sources.list /etc/apt/sources.list.d/* # all repositories
• apt update && apt -d -y full-upgrade # update package list and download (not:install) packages

Oh, and please put each command in a separate [CODE]...[/CODE]-block for better readability.

 

[fabio.rodo]

You have installed packages that do not belong to a standard PVE installation. That's usually a bad idea, especially for beginners. Did you use external scripts for this?



Please start by giving us some information, like the copy-n-pasted output of some commands, run on a PVE host:

PVE System information:

• pveversion -v
• head -n -0 /etc/apt/sources.list /etc/apt/sources.list.d/* # all repositories
• apt update && apt -d -y full-upgrade # update package list and download (not:install) packages

Oh, and please put each command in a separate [CODE]...[/CODE]-block for better readability.

first of all thank you for your answer. I installed the lxc via Proxmox VE Helper-Scripts as all the others.

here is the output of the commands:

Linux proxmox 6.8.12-5-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-5 (2024-12-03T10:26Z) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Dec 20 22:28:55 CET 2024 on pts/0
root@proxmox:~# pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-5-pve)
pve-manager: 8.3.2 (running version: 8.3.2/3e76eec21c4a14a7)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-5
proxmox-kernel-6.8.12-5-pve-signed: 6.8.12-5
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.2-1
proxmox-backup-file-restore: 3.3.2-2
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.3
pve-cluster: 8.0.10
pve-container: 5.2.3
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: not correctly installed
pve-ha-manager: 4.0.6
pve-i18n: 3.3.2
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.3
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1

root@proxmox:~# head -n -0 /etc/apt/sources.list /etc/apt/sources.list.d/*
==> /etc/apt/sources.list <==
deb http://deb.debian.org/debian bookworm main contrib
deb http://deb.debian.org/debian bookworm-updates main contrib
deb http://security.debian.org/debian-security bookworm-security main contrib

==> /etc/apt/sources.list.d/ceph.list <==
# deb https://enterprise.proxmox.com/debian/ceph-quincy bookworm enterprise
# deb http://download.proxmox.com/debian/ceph-quincy bookworm no-subscription
# deb https://enterprise.proxmox.com/debian/ceph-reef bookworm enterprise
# deb http://download.proxmox.com/debian/ceph-reef bookworm no-subscription

==> /etc/apt/sources.list.d/pve-enterprise.list <==
# deb https://enterprise.proxmox.com/debian/pve bookworm pve-enterprise

==> /etc/apt/sources.list.d/pve-install-repo.list <==
deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription

==> /etc/apt/sources.list.d/pvetest-for-beta.list <==
# deb http://download.proxmox.com/debian/pve bookworm pvetest

root@proxmox:~# apt update && apt -d -y full-upgrade
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Hit:4 http://download.proxmox.com/debian/pve bookworm InRelease
Fetched 55.4 kB in 0s (144 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

 

[UdoB]

Okay, thanks for the information. The sources.lists look sane. Now do what the last command recommends, run:

apt list --upgradable   # just because curiosity
dpkg --configure -a

(And post the output.)

We did not change anything yet, so you probably get the same strange error again - but let's make small steps.

Do you have space on "/" to install packages? What gives mount, df -h and lsblk -f?

 

[fabio.rodo]

Here is all the info you requested! Once again thanks for your support!

root@proxmox:~# apt list --upgradable
Listing... Done
pve-firmware/stable 3.14-2 all [upgradable from: 3.11-1]
N: There are 13 additional versions. Please use the '-a' switch to see them.

root@proxmox:~# dpkg --configure -a
root@proxmox:~#

root@proxmox:~# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=16265812k,nr_inodes=4066453,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=3259072k,mode=755,inode64)
/dev/mapper/pve-root on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=9009)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
ramfs on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-tmpfiles-setup-dev.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-sysctl.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
/dev/nvme0n1p2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
ramfs on /run/credentials/systemd-tmpfiles-setup.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
192.168.1.85:/mnt/HD/HD_a2/media on /mnt/lxc_shares/nas_rwx type nfs (rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.85,mountvers=3,mountport=46085,mountproto=udp,local_lock=none,addr=192.168.1.85)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=3259068k,nr_inodes=814767,mode=700,inode64)

root@proxmox:~# df -h
Filesystem                        Size  Used Avail Use% Mounted on
udev                               16G     0   16G   0% /dev
tmpfs                             3.2G  3.0M  3.2G   1% /run
/dev/mapper/pve-root               94G   12G   78G  13% /
tmpfs                              16G   37M   16G   1% /dev/shm
tmpfs                             5.0M     0  5.0M   0% /run/lock
efivarfs                          192K  120K   68K  64% /sys/firmware/efi/efivars
/dev/nvme0n1p2                   1022M   12M 1011M   2% /boot/efi
192.168.1.85:/mnt/HD/HD_a2/media  7.3T  3.9T  3.4T  54% /mnt/lxc_shares/nas_rwx
/dev/fuse                         128M   36K  128M   1% /etc/pve
tmpfs                             3.2G     0  3.2G   0% /run/user/0

root@proxmox:~# lsblk -f
NAME                         FSTYPE      FSVER    LABEL UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1                                                                                                       
├─nvme0n1p1                                                                                                   
├─nvme0n1p2                  vfat        FAT32          E4BF-0F5A                              1010.3M     1% /boot/efi
└─nvme0n1p3                  LVM2_member LVM2 001       8hBWje-YmZB-sXYr-lXxt-PSoR-Ysy1-RwzVxI               
  ├─pve-swap                 swap        1              8f0f211d-538c-4d44-96c9-a7410564b7d6                  [SWAP]
  ├─pve-root                 ext4        1.0            466f0ae4-fbcb-44cc-81f2-31ff18412fb8     77.6G    12% /
  ├─pve-data_tmeta                                                                                           
  │ └─pve-data-tpool                                                                                         
  │   ├─pve-data                                                                                             
  │   ├─pve-vm--101--disk--0                                                                                 
  │   ├─pve-vm--101--disk--1                                                                                 
  │   ├─pve-vm--105--disk--0 ext4        1.0            20fbb008-3f4c-49e4-a322-b011b47c035a                 
  │   ├─pve-vm--104--disk--0 ext4        1.0            2c008b8e-6ce4-43b0-b3c4-5077063b247a                 
  │   ├─pve-vm--103--disk--0 ext4        1.0            d0df8c44-8828-4569-8a46-a34129ff919d                 
  │   ├─pve-vm--106--disk--0 ext4        1.0            4d089a29-2a40-4384-a708-7d6e8a76dbd9                 
  │   ├─pve-vm--107--disk--0 ext4        1.0            72a16193-583c-414d-9d58-4bab7d9e72a9                 
  │   ├─pve-vm--108--disk--0 ext4        1.0            3990de77-c82b-4bc7-b171-e6caa0d63d0f                 
  │   ├─pve-vm--109--disk--0 ext4        1.0            7ccd616a-9574-4ba7-87d5-762b196e4994                 
  │   ├─pve-vm--110--disk--0 ext4        1.0            0af0223e-6144-4d89-88fc-0a7df1b93b77                 
  │   └─pve-vm--111--disk--0 ext4        1.0            21778897-3003-4030-9b50-51fe38d3271e                 
  └─pve-data_tdata                                                                                           
    └─pve-data-tpool                                                                                         
      ├─pve-data                                                                                             
      ├─pve-vm--101--disk--0                                                                                 
      ├─pve-vm--101--disk--1                                                                                 
      ├─pve-vm--105--disk--0 ext4        1.0            20fbb008-3f4c-49e4-a322-b011b47c035a                 
      ├─pve-vm--104--disk--0 ext4        1.0            2c008b8e-6ce4-43b0-b3c4-5077063b247a                 
      ├─pve-vm--103--disk--0 ext4        1.0            d0df8c44-8828-4569-8a46-a34129ff919d                 
      ├─pve-vm--106--disk--0 ext4        1.0            4d089a29-2a40-4384-a708-7d6e8a76dbd9                 
      ├─pve-vm--107--disk--0 ext4        1.0            72a16193-583c-414d-9d58-4bab7d9e72a9                 
      ├─pve-vm--108--disk--0 ext4        1.0            3990de77-c82b-4bc7-b171-e6caa0d63d0f                 
      ├─pve-vm--109--disk--0 ext4        1.0            7ccd616a-9574-4ba7-87d5-762b196e4994                 
      ├─pve-vm--110--disk--0 ext4        1.0            0af0223e-6144-4d89-88fc-0a7df1b93b77                 
      └─pve-vm--111--disk--0 ext4        1.0            21778897-3003-4030-9b50-51fe38d3271e

 

[UdoB]

Okay, no obvious problem recognizable and no error given - and also "--configure -a" did not fail.

After all those passive check we finally arrive to the actual upgrade command:

apt full-upgrade

This should be the equivalent to the Web-Gui button labeled "_Upgrade". Sorry for the slow progress, but I always do start debugging at the basics.

---

Your initial post contained "[ERROR] in line 164: exit code 0: while executing command apt-get install -y figlet &> /dev/null". Can you reproduce that? Using which exact steps?

Was that on the host or already inside the container? If it is inside the Container then we are looking at the wrong place because I misunderstood that...

Unfortunately I do not have much experience using containers as I use VMs for 99% of my services.

Does that container exist now? Or does the creation fail? Can you show the configuration of the container? Use pct config <your-container-id> for this. Can you enter the container from your root@host shell via pct enter <your-container-id>? (Though I am not sure what to do there regarding Kuma.)

 

[fabio.rodo]

I always get this:

Linux proxmox 6.8.12-5-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-5 (2024-12-03T10:26Z) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Dec 21 13:20:53 CET 2024 on pts/0
root@proxmox:~# apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  pve-firmware
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/154 MB of archives.
After this operation, 88.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Reading changelogs... Done
dpkg: warning: files list file for package 'pve-firmware' missing; assuming package has no files currently installed
(Reading database ... 43383 files and directories currently installed.)
Preparing to unpack .../pve-firmware_3.14-2_all.deb ...
Unpacking pve-firmware (3.14-2) over (3.11-1) ...

Progress: [ 20%] [###########################.............................................................................................................]

get stuck there and reboot. Or at least I think. What I know is that all the lxc and VM stop and restart.

Your initial post contained "[ERROR] in line 164: exit code 0: while executing command apt-get install -y figlet &> /dev/null". Can you reproduce that? Using which exact steps?

Yes every time I launch the install script for kuma

Was that on the host or already inside the container? If it is inside the Container then we are looking at the wrong place because I misunderstood that...

no. it's in the host

Does that container exist now? Or does the creation fail? Can you show the configuration of the container? Use pct config <your-container-id> for this. Can you enter the container from your root@host shell via pct enter <your-container-id>? (Though I am not sure what to do there regarding Kuma.)

no the process get stuck and the lxc is not installed

this is the install script (I get the same with other script too)

#!/usr/bin/env bash

# Copyright (c) 2021-2024 tteck
# Author: tteck (tteckster)
# License: MIT
# https://github.com/community-scripts/ProxmoxVE/raw/main/LICENSE

source /dev/stdin <<< "$FUNCTIONS_FILE_PATH"
color
verb_ip6
catch_errors
setting_up_container
network_check
update_os

msg_info "Installing Dependencies"
$STD apt-get install -y curl
$STD apt-get install -y sudo
$STD apt-get install -y mc
$STD apt-get install -y git
$STD apt-get install -y ca-certificates
$STD apt-get install -y gnupg
msg_ok "Installed Dependencies"

msg_info "Setting up Node.js Repository"
mkdir -p /etc/apt/keyrings
curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg
echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x nodistro main" >/etc/apt/sources.list.d/nodesource.list
msg_ok "Set up Node.js Repository"

msg_info "Installing Node.js"
$STD apt-get update
$STD apt-get install -y nodejs
msg_ok "Installed Node.js"

msg_info "Installing Uptime Kuma"
$STD git clone https://github.com/louislam/uptime-kuma.git
mv uptime-kuma /opt/uptime-kuma
cd /opt/uptime-kuma
$STD npm run setup
msg_ok "Installed Uptime Kuma"

msg_info "Creating Service"
service_path="/etc/systemd/system/uptime-kuma.service"
echo "[Unit]
Description=uptime-kuma

[Service]
Type=simple
Restart=always
User=root
WorkingDirectory=/opt/uptime-kuma
ExecStart=/usr/bin/npm start

[Install]
WantedBy=multi-user.target" >$service_path
$STD systemctl enable --now uptime-kuma.service
msg_ok "Created Service"

motd_ssh
customize

msg_info "Cleaning up"
$STD apt-get -y autoremove
$STD apt-get -y autoclean
msg_ok "Cleaned"

 

[UdoB]

This part: "Unpacking pve-firmware (3.14-2) over (3.11-1) ..." is running on the host. I do not know why it kills your system. To get this problem out of the way you may put the known-good version "on hold" with something like this: apt-mark hold pve-firmware. This is permanent, so you need to "unhold" it in some weeks or months.

The script itself I can not judge, sorry. I do not use this type of helper. But... you know that the author ("tteck") - very sadly - is gone? You may find newer and actively supported scripts though.

 

[ivanlinares]

Hi everybody, I'm getting the same error when I try to update Omada Software Controller issuing the update command in LXC console, thank you in advance.

[ERROR] in line 164: exit code 0: while executing command apt-get install -y figlet &> /dev/null