[SOLVED] omv-release-upgrade not work because promox key not available

  • Y try to upgrade a promox OMV, and have this error:






    resume:



    Code
    Reading package lists... Done
    W: GPG error: http://download.proxmox.com/debian/pve bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1140AF8F639E0C39
    E: The repository 'http://download.proxmox.com/debian/pve bookworm 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.
  • i ditched proxmox because it is fundamentally incompatible with the rest of the debian ecosystem

    in other words it caused me alot of problems.

    including performance.


    only zfs on proxmox works better than vanilla debian kernel.


    plus they upgraded zfs to 2.2.2 that fixed the corruption bug

    • Official Post

    people, stay away from proxmox

    Having run proxmox for a decade without any major issues, this is very broad statement without any reason why.

    have this error:

    run the fix6to7upgrade script:

    sudo wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/fix6to7upgrade | sudo bash

    i ditched proxmox because it is fundamentally incompatible with the rest of the debian ecosystem

    What? You don't know Linux or Debian very well. The proxmox kernel is based on Ubuntu (which is based on Debian) and is still the Linux kernel which works very well with the Debian "ecosystem". proxmox has always used the Debian userland meaning it works well. Please stop posting this inaccurate statements.

    only zfs on proxmox works better than vanilla debian kernel.

    I run the proxmox kernel on all of my amd64 OMV systems. If it was as bad as you say, I wouldn't have written the kernel plugin.

    omv 8.5.11-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.4 | compose 8.2.2 | cterm 8.0.4 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.3.0 | backup 8.1 | kernel 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • i am finishing setting up a raid5 mdadm array. initial benchmarking shows vanilla debian openmediavault kernel as a bit faster. i will post after i finalize on which filesystem i will use. btw did you try mounting an f2fs using proxmox? besides proxmox is not a fan of linux raid

  • Having run proxmox for a decade without any major issues, this is very broad statement without any reason why.

    run the fix6to7upgrade script:

    sudo wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/fix6to7upgrade | sudo bash

    Ok, this solve my problem:


    Code
    root@cnas:~# dpkg -l | grep openme
    ii  openmediavault                  7.0-14                              all          openmediavault - The open network attached storage solution
    ii  openmediavault-cputemp          7.0                                 all          cpu temperature plugin for openmediavault
    ii  openmediavault-kernel           7.0.2                               all          kernel package
    ii  openmediavault-keyring          1.0.2-2                             all          GnuPG archive keys of the openmediavault archive
    ii  openmediavault-omvextrasorg     7.0                                 all          OMV-Extras.org Package Repositories for OpenMediaVault
    ii  openmediavault-resetperms       7.0                                 all          Reset Permissions
    root@cnas:~#

    but at this point , I can't login on OMV WebGUi.



    This post resolve the login problem: RE: [SOLVED] Upgrade 6->7 Can't login


    so now all is working.


    I change to solved the thread.



    Thanks a lot.

  • raulfg3

    Added the Label resolved
  • raulfg3

    Changed the title of the thread from “omv-release-upgrade not work because promox key not available” to “[SOLVED] omv-release-upgrade not work because promox key not available”.
    • Official Post

    besides proxmox is not a fan of linux raid

    The proxmox interface doesn't support it but in context of the proxmox kernel supporting raid, there is no difference since it is enabled in the kernel.

    initial benchmarking shows vanilla debian openmediavault kernel as a bit faster.

    What versions of each kernel?


    in any case there should be an "openmediavault kernel" tuned especially for openmediavault so people can customize, etc. who will be kind enough to start it up?

    Why? I don't see much benefit if the kernel still had to support all of the hardware that it supports now. I compiled kernels for over a decade when I ran Gentoo. I can't see any reason to do this with a NAS. The reason to use the proxmox kernel is that zfs is compiled in but that is about the only customization I can see being needed. And don't forget that majority of OMV users are using arm-based SBCs. These kernels already are optimized for the board they run on when using Armbian.

    omv 8.5.11-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.4 | compose 8.2.2 | cterm 8.0.4 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.3.0 | backup 8.1 | kernel 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    16k page size would be great for a nas

    For your NAS. The use case that people use OMV for is so diverse that you can't make that assumption.

    omv 8.5.11-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.4 | compose 8.2.2 | cterm 8.0.4 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.3.0 | backup 8.1 | kernel 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • now that i got rid of proxmox i will look into compiling my own 16K page kernel if its possible and doesn't break everything or have to resort into building a system like linux from scratch recompiling everything and so on

    • Official Post

    now that i got rid of proxmox i will look into compiling my own 16K page kernel if its possible and doesn't break everything or have to resort into building a system like linux from scratch recompiling everything and so on

    I'm not sure why you think you need a 16k page size. Maybe if you had hundreds of servers with 25 or 100 gig networking where 3% performance increase makes a difference. But compiling a kernel shouldn't break anything. Going from debian with a custom kernel to LFS is a BIG jump. I spent years doing that and it won't help a NAS enough to justify the time.

    omv 8.5.11-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.4 | compose 8.2.2 | cterm 8.0.4 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.3.0 | backup 8.1 | kernel 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • now i am setting up things and i am experimenting. from what i read 16k pages is the trend nowdays f2fs implemented 16k blocks~pages on linux 6.7 xfs supports pages up to 65K if i am not mistaken. i had big problems with proxmox kernel and f2fs. in any case proxmox hates mdadm raid and proxmox people certainly think f2fs is only a toy for mobile phones. i run a rai5 array of four ssds for years without an issue. unfortunatelly currently kernel 6.6 it seems f2fs is somewhat slower than xfs is a bit faster. its apity because f2fs works great with ssds

    • Official Post

    proxmox people certainly think f2fs is only a toy for mobile phones.

    Samsung designed it for nand flash. It has issues with loss of power which is normally not an issue with battery powered devices. Not sure why you would use it for a NAS. It is a relatively young filesystem and most NAS desire stability. I have never seen F2FS used in the enterprise.

    its apity because f2fs works great with ssds

    As does ext4, btrfs, xfs, zfs, and any other native Linux filesystem.

    omv 8.5.11-1 synchrony | 7.0 proxmox kernel

    plugins:

    omvextrasorg 8.0.3 | kvm 8.3.4 | compose 8.2.2 | cterm 8.0.4 | borgbackup 8.2.1 | tempmon 8.0.5 |

    mergerfs 8.0.2 | scripts 8.0.6 | writecache 8.3.0 | backup 8.1 | kernel 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • i used in on a raid5 ssd array for years. now i switched to xfs that seems very fast so far. still i am a fan of f2fs but in recent kernels it has gotten slower and slower. still i am investingating. today i installed on my experimental openmediavault box official debian kernel 6.1 source and recompiled the kernel. its too early but i will test some modifications and page size after the new year

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!