OMV 6.4.4-1 (Shaitan) update impossible due to public key not available & repositories not signed

ryecoaaron · Nov 12th 2023

Quote from Tido-

The solution is not as written by Mods to go to 64bit, but to fix the broken link.

We tell people to use arm64 because most people use docker and armhf is slowly being deprecated. And your solution starts to mix debian armhf packages with raspbian armhf packages. This could cause issues (and has) when the same package is updated in one repo. Raspberry Pi OS arm64 is pure Debian packages and doesn't have this risk. Your solution does satisfy the apt issues but is not the correct solution in my opinion.

Tido- · Nov 19th 2023

Quote from ryecoaaron

And your solution starts to mix debian armhf packages with raspbian armhf packages.

I didn't know that.

The only time I can see RPi in my apt-key list is here. If this serves security-updates too, your right, I might face some troubles.

Code

/etc/apt/trusted.gpg.d/raspberrypi-archive-stable.gpg
-----------------------------------------------------
pub   rsa2048 2012-06-17 [SC]
      CF8A 1AF5 02A2 AA2D 763B  AE7E 82B1 2992 7FA3 303E
uid           [ unknown] Raspberry Pi Archive Signing Key
sub   rsa2048 2012-06-17 [E]

So, if they serv security-updates, another solution could be to remove the Debian entry.

Why 32bit:

I installed Raspbian, followed by OMV and HomeAssistant. 32bit for 1 Gigabyte RAM seemed an obvious choice to me - as 64bit comes in this case with an overhead. I don't know how much the difference would be.

However, many RPi2 still need 32bit and these can run containers too.

chente · Nov 19th 2023

Quote from Tido-

I don't know how much the difference would be.

You won't notice it on a day-to-day basis.

Quote from Tido-

However, many RPi2 still need 32bit and these can run containers too.

There are still 32-bit containers, but they are gradually disappearing. Furthermore, many of the ones that exist are no longer updated, that is a security risk. If your hardware can run 64 bits, as is the case with the Raspberry Pi3, there is no point in doing anything else.

ryecoaaron · Nov 19th 2023

Quote from Tido-

32bit for 1 Gigabyte RAM seemed an obvious choice to me - as 64bit comes in this case with an overhead. I don't know how much the difference would be.

64bit uses a bit more ram but 64 bit is a bit faster. But it won't matter soon when 64bit is the only option for docker. 32 bit arm images are already going away.

oaked_pine · Jan 23rd 2026

Quote from chente

If it still doesn't work you can try installing the keys manually.

wget http://packages.openmediavault.org/public/pool/main/o/openmediavault-keyring/openmediavault-keyring_1.0.2-2_all.deb
sudo dpkg -i openmediavault-keyring_1.0.2-2_all.deb
sudo apt-get update

Holy macaroni and cheese! I've had a similar "GPG error: http://packages.openmediavault.org/public shaitan InRelease" public key not available error that i've been trying to solve for months. probably should've made my own post but was trying to devour the dozens of threads here and on reddit and elsewhere before posting....anyway after a zillion different attempts, your code above to install the keys manually eliminated all key error messages. my OMV6 is finally error free for the first time in like 10 months...on to OMV 7 upgrade!

Thank you for being so helpful on this forum! Soma, ryecoaaron too! Thank you!

OMV 6.4.4-1 (Shaitan) update impossible due to public key not available & repositories not signed

Participate now!

Tags