OMV needs port 53. You can do this:
Perfect, thanks a lot I’ll try that.
OMV needs port 53. You can do this:
Perfect, thanks a lot I’ll try that.
I didn't even know iOS File manager supported smb. I will have to try it later.
Ok yes this is working without any problem.
Does no one on this forum has this problem?
OK thanks for your help guys, i will than do a new clean install of 64 bit OMV.
Hi all,
When i try to copy or move a local file from my iPad to the OMV System (Pi4, OMV6) im getting Error 100093 on my iPad. According to some thread on the internet, enabling Time Machine support will solve this.
I tried it and it works but then i have a problem with my Mac, described in detail here. So are there any other solutions for this? Any additional settings for smb.conf?
Display MoreJust 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
Ok thanks. So i think there is no chance to solve the error without a new install right?
Yea a clean install any drives other than OS drive should be fine. just remount them and make new shares.
Ok perfect thanks.
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?
Display MoreAccording to the output of dpkg -l | grep keyring, you are not.
On a pure 64Bit, you would also have the debian keyring:
CodeDisplay Morepi@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
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:
PostRE: 500 Server Internal Error after applying pending configuration changes OMV6The 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)
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
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.
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)
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.
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?
Hm ok, I need to google then and see if I can find something. Yes im using Samba.
Thank you very for you great help! Really appreciated.
Hm that's so strange. Yes I will try it from Win machine in the next days.
#======================= Global Settings =======================
[global]
workgroup = WORKGROUP
server string = %h server
dns proxy = no
log level = 0
log file = /var/log/samba/log.%m
max log size = 1000
logging = syslog
panic action = /usr/share/samba/panic-action %d
encrypt passwords = true
passdb backend = tdbsam
obey pam restrictions = no
unix password sync = no
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
pam password change = yes
socket options = TCP_NODELAY IPTOS_LOWDELAY
guest account = nobody
load printers = no
disable spoolss = yes
printing = bsd
printcap name = /dev/null
unix extensions = yes
wide links = no
create mask = 0777
directory mask = 0777
use sendfile = yes
aio read size = 16384
aio write size = 16384
time server = no
wins support = no
multicast dns register = no
# Special configuration for Apple's Time Machine
fruit:aapl = yes
# Extra options
min receivefile size = 16384
write cache size = 524288
getwd cache = yes
socket options = TCP_NODELAY IPTOS_LOWDELAY
Display More
[Daten_Gemeinsam]
path = /srv/dev-disk-by-label-Daten/Daten_Gemeinsam/
guest ok = no
guest only = no
read only = no
browseable = yes
inherit acls = no
inherit permissions = no
ea support = no
store dos attributes = no
vfs objects = fruit streams_xattr
printable = no
create mask = 0664
force create mode = 0664
directory mask = 0775
force directory mode = 0775
hide special files = yes
follow symlinks = yes
hide dot files = yes
valid users = "Sarah","Max","Admin"
invalid users =
read list =
write list = "Sarah","Max","Admin"
Display More