last node update fail - doesn't boot anymore
Ste
133 Posts
March 26, 2025, 5:42 pmQuote from Ste on March 26, 2025, 5:42 pmHello, i was updating my 4 nodes 3.1.0 cluster, the first 3 nodes (monitors) were successful, while the last one terminated with these errors, and now it doesn't boot anymore. What happened ? And is there a way to fix it ? Thanks.
root@petasan04:~# /opt/petasan/scripts/online-updates/update.sh
...
Preparing to unpack .../165-containernetworking-plugins_100%3a1.1.1~1_amd64.deb ...
Unpacking containernetworking-plugins (100:1.1.1~1) over (0.8.3-1~ubuntu18.04~ppa1) ...
Preparing to unpack .../166-libc-ares2_1.15.0-1ubuntu0.5_amd64.deb ...
Unpacking libc-ares2:amd64 (1.15.0-1ubuntu0.5) over (1.15.0-1ubuntu0.1) ...
Errors were encountered while processing:
/tmp/apt-dpkg-install-9YVNTj/064-petasan-firmware_20230320_amd64.deb
/tmp/apt-dpkg-install-9YVNTj/141-linux-firmware_1.187.39_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package lists... Done
Building dependency tree
Reading state information... Done
petasan is already the newest version (3.3.0).
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
linux-image-5.14.21-08-petasan : Depends: petasan-firmware (>= 20230320) but 20200107 is to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
dpkg: error: version '-petasan' has bad syntax: version number is empty
root@petasan04:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
containers-golang containers-image libleveldb1d liblttng-ust-ctl4 liblttng-ust0 linux-headers-5.4.0-117 linux-headers-5.4.0-117-generic linux-image-5.4.0-117-generic
linux-modules-5.4.0-117-generic linux-modules-extra-5.4.0-117-generic
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
petasan-firmware
The following packages will be upgraded:
petasan-firmware
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
243 not fully installed or removed.
Need to get 0 B/269 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up libss2:amd64 (1.45.5-2ubuntu1.2) ...
Setting up libapparmor1:amd64 (2.13.3-7ubuntu5.4) ...
Setting up libcap2:amd64 (1:2.32-1ubuntu0.2) ...
Setting up libip4tc2:amd64 (1.8.4-3ubuntu2.1) ...
Setting up mount (2.34-0.1ubuntu9.6) ...
Setting up systemd (245.4-4ubuntu3.24) ...
(Reading database ... 126318 files and directories currently installed.)
Preparing to unpack .../petasan-firmware_20230320_amd64.deb ...
Unpacking petasan-firmware (20230320) over (20200107) ...
dpkg: error processing archive /var/cache/apt/archives/petasan-firmware_20230320_amd64.deb (--unpack):
trying to overwrite '/lib/firmware/3com/typhoon.bin', which is also in package linux-firmware 1.173.20
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/petasan-firmware_20230320_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@petasan04:~# apt update
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-security InRelease
Hit:4 https://archive.petasan.org/repo_v3 petasan-v3 InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@petasan04:~# apt list --upgradable
Listing... Done
linux-firmware/focal-updates 1.187.39 all [upgradable from: 1.173.20]
petasan-firmware/petasan-v3 20230320 amd64 [upgradable from: 20200107]
podman/petasan-v3 100:3.4.2-5 amd64 [upgradable from: 1.6.2-1~ubuntu18.04~ppa1]
root@petasan04:~# apt install petasan-firmware
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
containers-golang containers-image libleveldb1d liblttng-ust-ctl4 liblttng-ust0 linux-headers-5.4.0-117 linux-headers-5.4.0-117-generic linux-image-5.4.0-117-generic
linux-modules-5.4.0-117-generic linux-modules-extra-5.4.0-117-generic
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
petasan-firmware
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
237 not fully installed or removed.
Need to get 0 B/269 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 126318 files and directories currently installed.)
Preparing to unpack .../petasan-firmware_20230320_amd64.deb ...
Unpacking petasan-firmware (20230320) over (20200107) ...
dpkg: error processing archive /var/cache/apt/archives/petasan-firmware_20230320_amd64.deb (--unpack):
trying to overwrite '/lib/firmware/3com/typhoon.bin', which is also in package linux-firmware 1.173.20
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/petasan-firmware_20230320_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
After a reboot I only get now the grub> prompt. 🙁 Fortunately this is not a monitoring node.
PS: now the working 3 nodes have version 3.3.0, but I did not run the last two commands:
ceph osd require-osd-release quincy
ceph config set mon mon_mds_skip_sanity false
so i have this warning: "all OSDs are running quincy or later but require_osd_release < quincy". What shall i do ?
Hello, i was updating my 4 nodes 3.1.0 cluster, the first 3 nodes (monitors) were successful, while the last one terminated with these errors, and now it doesn't boot anymore. What happened ? And is there a way to fix it ? Thanks.
root@petasan04:~# /opt/petasan/scripts/online-updates/update.sh
...
Preparing to unpack .../165-containernetworking-plugins_100%3a1.1.1~1_amd64.deb ...
Unpacking containernetworking-plugins (100:1.1.1~1) over (0.8.3-1~ubuntu18.04~ppa1) ...
Preparing to unpack .../166-libc-ares2_1.15.0-1ubuntu0.5_amd64.deb ...
Unpacking libc-ares2:amd64 (1.15.0-1ubuntu0.5) over (1.15.0-1ubuntu0.1) ...
Errors were encountered while processing:
/tmp/apt-dpkg-install-9YVNTj/064-petasan-firmware_20230320_amd64.deb
/tmp/apt-dpkg-install-9YVNTj/141-linux-firmware_1.187.39_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package lists... Done
Building dependency tree
Reading state information... Done
petasan is already the newest version (3.3.0).
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
linux-image-5.14.21-08-petasan : Depends: petasan-firmware (>= 20230320) but 20200107 is to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
dpkg: error: version '-petasan' has bad syntax: version number is empty
root@petasan04:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
containers-golang containers-image libleveldb1d liblttng-ust-ctl4 liblttng-ust0 linux-headers-5.4.0-117 linux-headers-5.4.0-117-generic linux-image-5.4.0-117-generic
linux-modules-5.4.0-117-generic linux-modules-extra-5.4.0-117-generic
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
petasan-firmware
The following packages will be upgraded:
petasan-firmware
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
243 not fully installed or removed.
Need to get 0 B/269 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up libss2:amd64 (1.45.5-2ubuntu1.2) ...
Setting up libapparmor1:amd64 (2.13.3-7ubuntu5.4) ...
Setting up libcap2:amd64 (1:2.32-1ubuntu0.2) ...
Setting up libip4tc2:amd64 (1.8.4-3ubuntu2.1) ...
Setting up mount (2.34-0.1ubuntu9.6) ...
Setting up systemd (245.4-4ubuntu3.24) ...
(Reading database ... 126318 files and directories currently installed.)
Preparing to unpack .../petasan-firmware_20230320_amd64.deb ...
Unpacking petasan-firmware (20230320) over (20200107) ...
dpkg: error processing archive /var/cache/apt/archives/petasan-firmware_20230320_amd64.deb (--unpack):
trying to overwrite '/lib/firmware/3com/typhoon.bin', which is also in package linux-firmware 1.173.20
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/petasan-firmware_20230320_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@petasan04:~# apt update
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-security InRelease
Hit:4 https://archive.petasan.org/repo_v3 petasan-v3 InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@petasan04:~# apt list --upgradable
Listing... Done
linux-firmware/focal-updates 1.187.39 all [upgradable from: 1.173.20]
petasan-firmware/petasan-v3 20230320 amd64 [upgradable from: 20200107]
podman/petasan-v3 100:3.4.2-5 amd64 [upgradable from: 1.6.2-1~ubuntu18.04~ppa1]
root@petasan04:~# apt install petasan-firmware
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
containers-golang containers-image libleveldb1d liblttng-ust-ctl4 liblttng-ust0 linux-headers-5.4.0-117 linux-headers-5.4.0-117-generic linux-image-5.4.0-117-generic
linux-modules-5.4.0-117-generic linux-modules-extra-5.4.0-117-generic
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
petasan-firmware
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
237 not fully installed or removed.
Need to get 0 B/269 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 126318 files and directories currently installed.)
Preparing to unpack .../petasan-firmware_20230320_amd64.deb ...
Unpacking petasan-firmware (20230320) over (20200107) ...
dpkg: error processing archive /var/cache/apt/archives/petasan-firmware_20230320_amd64.deb (--unpack):
trying to overwrite '/lib/firmware/3com/typhoon.bin', which is also in package linux-firmware 1.173.20
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/petasan-firmware_20230320_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
After a reboot I only get now the grub> prompt. 🙁 Fortunately this is not a monitoring node.
PS: now the working 3 nodes have version 3.3.0, but I did not run the last two commands:
ceph osd require-osd-release quincy
ceph config set mon mon_mds_skip_sanity false
so i have this warning: "all OSDs are running quincy or later but require_osd_release < quincy". What shall i do ?
Last edited on March 26, 2025, 5:46 pm by Ste · #1
Ste
133 Posts
March 27, 2025, 9:26 amQuote from Ste on March 27, 2025, 9:26 amOk, I managed it ! The main issue was this conflict between linux-firmware and petasan-firmware (and i don't understand why, because on all other nodes it worked fine):
trying to overwrite '/lib/firmware/amd/amd_sev_fam17h_model0xh.sbin', which is also in package petasan-firmware
Forcing installation of these packages did the trick:
sudo dpkg -i --force-overwrite /var/cache/apt/archives/linux-firmware_1.187.39_all.deb
sudo dpkg -i --force-overwrite /var/cache/apt/archives/petasan-firmware_20230320_amd64.deb
Thanks anyway 🙂
Ok, I managed it ! The main issue was this conflict between linux-firmware and petasan-firmware (and i don't understand why, because on all other nodes it worked fine):
trying to overwrite '/lib/firmware/amd/amd_sev_fam17h_model0xh.sbin', which is also in package petasan-firmware
Forcing installation of these packages did the trick:
sudo dpkg -i --force-overwrite /var/cache/apt/archives/linux-firmware_1.187.39_all.deb
sudo dpkg -i --force-overwrite /var/cache/apt/archives/petasan-firmware_20230320_amd64.deb
Thanks anyway 🙂
Last edited on March 27, 2025, 9:26 am by Ste · #2
admin
2,957 Posts
March 27, 2025, 11:31 amQuote from admin on March 27, 2025, 11:31 amit could a non-PetaSAN kernel was installed on that node.
it could a non-PetaSAN kernel was installed on that node.
last node update fail - doesn't boot anymore
Ste
133 Posts
Quote from Ste on March 26, 2025, 5:42 pmHello, i was updating my 4 nodes 3.1.0 cluster, the first 3 nodes (monitors) were successful, while the last one terminated with these errors, and now it doesn't boot anymore. What happened ? And is there a way to fix it ? Thanks.
root@petasan04:~# /opt/petasan/scripts/online-updates/update.sh
...
Preparing to unpack .../165-containernetworking-plugins_100%3a1.1.1~1_amd64.deb ...
Unpacking containernetworking-plugins (100:1.1.1~1) over (0.8.3-1~ubuntu18.04~ppa1) ...
Preparing to unpack .../166-libc-ares2_1.15.0-1ubuntu0.5_amd64.deb ...
Unpacking libc-ares2:amd64 (1.15.0-1ubuntu0.5) over (1.15.0-1ubuntu0.1) ...
Errors were encountered while processing:
/tmp/apt-dpkg-install-9YVNTj/064-petasan-firmware_20230320_amd64.deb
/tmp/apt-dpkg-install-9YVNTj/141-linux-firmware_1.187.39_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package lists... Done
Building dependency tree
Reading state information... Done
petasan is already the newest version (3.3.0).
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
linux-image-5.14.21-08-petasan : Depends: petasan-firmware (>= 20230320) but 20200107 is to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
dpkg: error: version '-petasan' has bad syntax: version number is emptyroot@petasan04:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
containers-golang containers-image libleveldb1d liblttng-ust-ctl4 liblttng-ust0 linux-headers-5.4.0-117 linux-headers-5.4.0-117-generic linux-image-5.4.0-117-generic
linux-modules-5.4.0-117-generic linux-modules-extra-5.4.0-117-generic
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
petasan-firmware
The following packages will be upgraded:
petasan-firmware
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
243 not fully installed or removed.
Need to get 0 B/269 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up libss2:amd64 (1.45.5-2ubuntu1.2) ...
Setting up libapparmor1:amd64 (2.13.3-7ubuntu5.4) ...
Setting up libcap2:amd64 (1:2.32-1ubuntu0.2) ...
Setting up libip4tc2:amd64 (1.8.4-3ubuntu2.1) ...
Setting up mount (2.34-0.1ubuntu9.6) ...
Setting up systemd (245.4-4ubuntu3.24) ...
(Reading database ... 126318 files and directories currently installed.)
Preparing to unpack .../petasan-firmware_20230320_amd64.deb ...
Unpacking petasan-firmware (20230320) over (20200107) ...
dpkg: error processing archive /var/cache/apt/archives/petasan-firmware_20230320_amd64.deb (--unpack):
trying to overwrite '/lib/firmware/3com/typhoon.bin', which is also in package linux-firmware 1.173.20
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/petasan-firmware_20230320_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)root@petasan04:~# apt update
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-security InRelease
Hit:4 https://archive.petasan.org/repo_v3 petasan-v3 InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.root@petasan04:~# apt list --upgradable
Listing... Done
linux-firmware/focal-updates 1.187.39 all [upgradable from: 1.173.20]
petasan-firmware/petasan-v3 20230320 amd64 [upgradable from: 20200107]
podman/petasan-v3 100:3.4.2-5 amd64 [upgradable from: 1.6.2-1~ubuntu18.04~ppa1]root@petasan04:~# apt install petasan-firmware
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
containers-golang containers-image libleveldb1d liblttng-ust-ctl4 liblttng-ust0 linux-headers-5.4.0-117 linux-headers-5.4.0-117-generic linux-image-5.4.0-117-generic
linux-modules-5.4.0-117-generic linux-modules-extra-5.4.0-117-generic
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
petasan-firmware
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
237 not fully installed or removed.
Need to get 0 B/269 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 126318 files and directories currently installed.)
Preparing to unpack .../petasan-firmware_20230320_amd64.deb ...
Unpacking petasan-firmware (20230320) over (20200107) ...
dpkg: error processing archive /var/cache/apt/archives/petasan-firmware_20230320_amd64.deb (--unpack):
trying to overwrite '/lib/firmware/3com/typhoon.bin', which is also in package linux-firmware 1.173.20
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/petasan-firmware_20230320_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)After a reboot I only get now the grub> prompt. 🙁 Fortunately this is not a monitoring node.
PS: now the working 3 nodes have version 3.3.0, but I did not run the last two commands:
ceph osd require-osd-release quincy
ceph config set mon mon_mds_skip_sanity false
so i have this warning: "all OSDs are running quincy or later but require_osd_release < quincy". What shall i do ?
Hello, i was updating my 4 nodes 3.1.0 cluster, the first 3 nodes (monitors) were successful, while the last one terminated with these errors, and now it doesn't boot anymore. What happened ? And is there a way to fix it ? Thanks.
root@petasan04:~# /opt/petasan/scripts/online-updates/update.sh
...
Preparing to unpack .../165-containernetworking-plugins_100%3a1.1.1~1_amd64.deb ...
Unpacking containernetworking-plugins (100:1.1.1~1) over (0.8.3-1~ubuntu18.04~ppa1) ...
Preparing to unpack .../166-libc-ares2_1.15.0-1ubuntu0.5_amd64.deb ...
Unpacking libc-ares2:amd64 (1.15.0-1ubuntu0.5) over (1.15.0-1ubuntu0.1) ...
Errors were encountered while processing:
/tmp/apt-dpkg-install-9YVNTj/064-petasan-firmware_20230320_amd64.deb
/tmp/apt-dpkg-install-9YVNTj/141-linux-firmware_1.187.39_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package lists... Done
Building dependency tree
Reading state information... Done
petasan is already the newest version (3.3.0).
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
linux-image-5.14.21-08-petasan : Depends: petasan-firmware (>= 20230320) but 20200107 is to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
dpkg: error: version '-petasan' has bad syntax: version number is emptyroot@petasan04:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
containers-golang containers-image libleveldb1d liblttng-ust-ctl4 liblttng-ust0 linux-headers-5.4.0-117 linux-headers-5.4.0-117-generic linux-image-5.4.0-117-generic
linux-modules-5.4.0-117-generic linux-modules-extra-5.4.0-117-generic
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
petasan-firmware
The following packages will be upgraded:
petasan-firmware
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
243 not fully installed or removed.
Need to get 0 B/269 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up libss2:amd64 (1.45.5-2ubuntu1.2) ...
Setting up libapparmor1:amd64 (2.13.3-7ubuntu5.4) ...
Setting up libcap2:amd64 (1:2.32-1ubuntu0.2) ...
Setting up libip4tc2:amd64 (1.8.4-3ubuntu2.1) ...
Setting up mount (2.34-0.1ubuntu9.6) ...
Setting up systemd (245.4-4ubuntu3.24) ...
(Reading database ... 126318 files and directories currently installed.)
Preparing to unpack .../petasan-firmware_20230320_amd64.deb ...
Unpacking petasan-firmware (20230320) over (20200107) ...
dpkg: error processing archive /var/cache/apt/archives/petasan-firmware_20230320_amd64.deb (--unpack):
trying to overwrite '/lib/firmware/3com/typhoon.bin', which is also in package linux-firmware 1.173.20
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/petasan-firmware_20230320_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)root@petasan04:~# apt update
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-security InRelease
Hit:4 https://archive.petasan.org/repo_v3 petasan-v3 InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.root@petasan04:~# apt list --upgradable
Listing... Done
linux-firmware/focal-updates 1.187.39 all [upgradable from: 1.173.20]
petasan-firmware/petasan-v3 20230320 amd64 [upgradable from: 20200107]
podman/petasan-v3 100:3.4.2-5 amd64 [upgradable from: 1.6.2-1~ubuntu18.04~ppa1]root@petasan04:~# apt install petasan-firmware
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
containers-golang containers-image libleveldb1d liblttng-ust-ctl4 liblttng-ust0 linux-headers-5.4.0-117 linux-headers-5.4.0-117-generic linux-image-5.4.0-117-generic
linux-modules-5.4.0-117-generic linux-modules-extra-5.4.0-117-generic
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
petasan-firmware
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
237 not fully installed or removed.
Need to get 0 B/269 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 126318 files and directories currently installed.)
Preparing to unpack .../petasan-firmware_20230320_amd64.deb ...
Unpacking petasan-firmware (20230320) over (20200107) ...
dpkg: error processing archive /var/cache/apt/archives/petasan-firmware_20230320_amd64.deb (--unpack):
trying to overwrite '/lib/firmware/3com/typhoon.bin', which is also in package linux-firmware 1.173.20
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/petasan-firmware_20230320_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
After a reboot I only get now the grub> prompt. 🙁 Fortunately this is not a monitoring node.
PS: now the working 3 nodes have version 3.3.0, but I did not run the last two commands:
ceph osd require-osd-release quincy
ceph config set mon mon_mds_skip_sanity false
so i have this warning: "all OSDs are running quincy or later but require_osd_release < quincy". What shall i do ?
Ste
133 Posts
Quote from Ste on March 27, 2025, 9:26 amOk, I managed it ! The main issue was this conflict between linux-firmware and petasan-firmware (and i don't understand why, because on all other nodes it worked fine):
trying to overwrite '/lib/firmware/amd/amd_sev_fam17h_model0xh.sbin', which is also in package petasan-firmware
Forcing installation of these packages did the trick:
sudo dpkg -i --force-overwrite /var/cache/apt/archives/linux-firmware_1.187.39_all.deb
sudo dpkg -i --force-overwrite /var/cache/apt/archives/petasan-firmware_20230320_amd64.debThanks anyway 🙂
Ok, I managed it ! The main issue was this conflict between linux-firmware and petasan-firmware (and i don't understand why, because on all other nodes it worked fine):
trying to overwrite '/lib/firmware/amd/amd_sev_fam17h_model0xh.sbin', which is also in package petasan-firmware
Forcing installation of these packages did the trick:
sudo dpkg -i --force-overwrite /var/cache/apt/archives/linux-firmware_1.187.39_all.deb
sudo dpkg -i --force-overwrite /var/cache/apt/archives/petasan-firmware_20230320_amd64.deb
Thanks anyway 🙂
admin
2,957 Posts
Quote from admin on March 27, 2025, 11:31 amit could a non-PetaSAN kernel was installed on that node.
it could a non-PetaSAN kernel was installed on that node.