Updating to 2.8.0 failed on Proxmox (drm-515-kmod, failed)
-
I am using pfsense on proxmox. OVMF/UEFI Bios. The upgrade to 2.8.0 failed. See the last line of the log.
Then I tried to install 2.8.0 from scratch. What a mess. Had to use the installer version instead as no images are available. It asked me a lot of redundant questions (as after starting the instance, network assignment had to be done again). I expected the installer to ask for my last backup file but it can't do that. So I had to run the botched update vm instance in parallel to a new one with cloned MAC Addresses and a lot of blood and sweat. The updater needs a working internet connection and I did not want to remove the old VM instance until the new one was running because I would have lost all DHCP leases and internet connection and would have been unable to use the virtual console through proxmox.
I think this installer is really a very very bad idea, as it can result into deadlock situations where the requirement of physical presence at the firewall has a much higher probability to occur. An iso builder would have been a much better idea. I will wait a few months until I start updating other instances...
Another problem was that after the update, it wanted to install the wireguard and other packages which also failed as it was using a DNS forward through a wireguard tunnel. Another reason why essential packages should be bundled into the iso and not live downloaded from the internet.>>> Updating repositories metadata... pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: . done pfSense-core repository update completed. 4 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: ..... done Processing entries: .......... done pfSense repository update completed. 541 packages processed. All repositories are up to date. >>> Locking package pkg...done. >>> Removing vital flag from php82...done. >>> Unlocking package pkg...done. >>> Downloading upgrade packages... Updating pfSense-core repository catalogue... Fetching meta.conf: Fetching packagesite.pkg: pfSense-core repository is up to date. Updating pfSense repository catalogue... Fetching meta.conf: Fetching packagesite.pkg: pfSense repository is up to date. All repositories are up to date. Checking for upgrades (147 candidates): .......... done Processing candidates (147 candidates): .......... done The following 259 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: [...] New packages to be INSTALLED: [...] Installed packages to be UPGRADED: [...] Installed packages to be REINSTALLED: [...] Number of packages to be removed: 49 Number of packages to be installed: 63 Number of packages to be upgraded: 122 Number of packages to be reinstalled: 25 The operation will free 12 MiB. 446 MiB to be downloaded. [...] Installed packages to be REINSTALLED: [...] Number of packages to be removed: 49 Number of packages to be installed: 63 Number of packages to be upgraded: 122 Number of packages to be reinstalled: 25 The operation will free 12 MiB. >>> Downloading pkg... No packages are required to be fetched. Integrity check was successful. >>> Downloading drm... The following packages will be fetched: New packages to be FETCHED: drm-515-kmod: 5.15.160.1500029_2 (4 MiB: 100.00% of the 4 MiB to download) Number of packages to be fetched: 1 The process will require 4 MiB more space. 4 MiB to be downloaded. Failed -
@nop Oh and I forgot to say that I was unable to run the online installer in OVMF (UEFI) mode whereas I was able to do install the 2.7.2 iso in that mode. And I still have the botched pfsense Image as VM instance on disc plus a backup file that could be restored and the upgrade tried again where in order to recreate this "failed" error.
-
Hmm, I use Proxmox and have some VMs running UEFI. I haven't seen a problem.
What issue do you see trying to run the installer?
