apt-get update errors missing public keys

Hi,

i recently upgraded from OMV5 to 6. After the upgrade i get the following error with apt-get update

Can you please guide me in the right direction?

W: GPG error: http://security.debian.org/debian-security bullseye-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 112695A0E562B32A NO_PUBKEY 54404762BBB6E853
E: The repository 'http://security.debian.org/debian-security bullseye-security InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://httpredir.debian.org/debian bullseye-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131
E: The repository 'http://httpredir.debian.org/debian bullseye-backports InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Quote from BlueCoffee

Try sudo apt-get clean and sudo apt-get update

Also is this a 32bit Pi?

Tried that but same error again. I’m running OMV on a Pi4 (64Bit)

Quote from votdev

What platform are you using? AMD64, ARM? OMV ISO, Raspi OS?

What is the output of dpkg -l | grep keyring and dpkg -l | grep openmediavault

Im using ARM (Pi4).

dpkg -l | grep keyring

ii  openmediavault-keyring          1.0.2-2                                  all          GnuPG archive keys of the openmediavault archive
ii  raspbian-archive-keyring        20120528.2                               all          GnuPG archive keys of the raspbian archive

dpkg -l | grep openmediavault

ii  openmediavault                  6.5.6-1                                  all          openmediavault - The open network attached storage solution
ii  openmediavault-clamav           6.0.5-1                                  all          openmediavault ClamAV plugin
ii  openmediavault-flashmemory      6.2                                      all          folder2ram plugin for openmediavault
ii  openmediavault-keyring          1.0.2-2                                  all          GnuPG archive keys of the openmediavault archive
ii  openmediavault-omvextrasorg     6.3.1                                    all          OMV-Extras.org Package Repositories for OpenMediaVault
ii  openmediavault-resetperms       6.0.3                                    all          Reset Permissions
ii  openmediavault-rsnapshot        6.0.2                                    all          OpenMediaVault rsnapshot backup plugin.

Quote from Soma

According to the output of dpkg -l | grep keyring, you are not.

On a pure 64Bit, you would also have the debian keyring:

Code

pi@panela:~ $ dpkg -l | grep keyring
ii  debian-archive-keyring    2021.1.1+deb11u1       all          GnuPG archive keys of the Debian archive
ii  openmediavault-keyring        1.0.2-2            all          GnuPG archive keys of the openmediavault archive
ii  raspberrypi-archive-keyring   2021.1.1+rpt1      all          GnuPG archive keys of the Raspberry Pi OS archive


pi@panela:~ $ uname -m
aarch64

pi@panela:~ $ dpkg --print-architecture
arm64

pi@panela:~ $ getconf LONG_BIT
64

Display More

Post the outputs of:

dpkg --print-architecture

getconf LONG_BIT

uname -a

See this thread from this post and see if you can solve the issue:

Post

RE: 500 Server Internal Error after applying pending configuration changes OMV6

The pub key issue has been fixed in openmediavault 6.5.6. Install the latest version (which is right now 6.5.6) the following way:

(Code, 4 lines)

votdev

Aug 8th 2023

Display More

Here is the output, sorry you are right its not 64Bit.

dpkg --print-architecture
armhf
getconf LONG_BIT
32
uname -a
Linux pinas 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux

I did all what is mentioned in the thread, but get the same errors.

Err:7 http://security.debian.org/debian-security bullseye-security InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 112695A0E562B32A NO_PUBKEY 54404762BBB6E853
Err:8 http://httpredir.debian.org/debian bullseye-backports InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131

Quote from votdev

As mentioned very often in the forum, consider an upgrade to 64bit because the 32bit image causes too much troubles.

Ok probably ill try that. So i need to install new right? Can i mount my current drives after a new install without problems?

Quote from BlueCoffee

Yea a clean install any drives other than OS drive should be fine. just remount them and make new shares.

Ok perfect thanks.

Quote from Soma

Just follow the guide for RPis and use the RaspiOS Lite 64Bit.

After OMV is up and running, power down and attach the drives.

OMV will recognizes them.

All it takes is to make the shares and point them to the existing paths

Display More

Ok thanks. So i think there is no chance to solve the error without a new install right?

OK thanks for your help guys, i will than do a new clean install of 64 bit OMV.