Posts by Hema2301

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

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

    Code
    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.

    Code
    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

    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

    Code
    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

    Code
    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.


    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?

    Code
    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.

    Thanks to you all especially seanwo for this solution, searched for this months now. I solved it now as suggested by adding vfs objects = to the extra options and it works great.

    But sadly i have another problem now. When i try to move files from the files app of my iPad to the NAS i get Error 100093. According to some thread on the internet, enabling Time Machine support will solve this.

    https://superuser.com/question…dia-vault-and-ios-devices
    I tried it and it works but then i have the same problem with my mac again. So are there any other solutions for this? Any additional settings for smb.conf?

    Hi all,

    I described my occasional problem here. It turns out that the problem occurs as soon as a folder is created from my Mac. The Mac creates additional ACLs. Im not using ACLs on my current setup. When I create a folder from e.g. Windows this problem does not occur. Does anyone know what could be the reason for this?

    Hi, so I created a folder now using Win. That's what I got:

    Code
    drwxrwsr-x 2 Max  users 4.0K Apr  8 13:07 .
    drwxrws--- 7 root users 4.0K Apr  8 13:07 ..

    So it seems there are something with Mac which will cause this issue!

    I set up the share with Administrators read/write, group read/write.

    Created a folder now with my Mac and with user Max and that's what I get.

    Code
    drwxr-xr-x+ 2 Max  users 4.0K Apr  4 17:25 .
    drwxrws---  6 root users 4.0K Apr  4 17:25 ..