Have you had luck getting this to work with permissions other than 777?
Beiträge von sonofwatt
-
-
As a test, I created a new share, for a new folder on a specific drive, not the mergerfs volume.
I added that share as an SMB share with the settings listed in the OMV-extras link. (guests allowed)
I even tried adding my laptop's ip, then the entire subnet to the Hosts Allow list.
I still can't access it.
I also created another test share for an existing folder with files, and ran Reset Permissions on it.
No luck.
NFS works fine on other systems, it's just the SMB shares that don't work.
To clarify, at this point I'm not even trying to restrict SMB shares, I just want guest access working.
-
That was the original goal. When I tried to restrict SMB access to user permissions I lost all access. NFS still works.
Right now I'm just trying to get guest access working again.
For my "testshare" I've used Reset Permissions to set the folder to Everyone.
-
What version of windows are you running? If it's older, you may need yo specify a min and max samba version. You may also have an encrypted credential issue or ntlm issue.
I'm on Windows 11, but previously had the same issues on Win 10. I've also tested this on a fresh Windows VM.
Under SMB/CIFS > Settings > Advanced Settings I entered in
client min protocol = NT1
server min protocol = NT1
client max protocol = SMB3
server max protocol = SMB3
client plaintext auth = yes
ntlm auth = yes
I'm still seeing the same Network Error message.
-
In the past I would map a drive to the shares. That should ask for user name. Put the ip of the OMV server then a \ then the user name on OMV. That tells it to authenticate to OMV.
That is what I'm trying to do. Something seems to be wrong with SMB, my file permissions or OMV. Right now even if I set a given share to guest, and use reset perms, I can't access it via windows.
-
Do you know how to change the user/group that windows is trying to connect with? This behaviour is from trying to connect, but not being given the option to enter a user and pass to connect. It just says Windows cannot access ...
Is there a way to reset all file/folder permissions back to default en masse?
At this point if I could just get SMB working with guest access, that would be ok.
-
Looking at the Diagnostics > Services > SMB/CIFS I can see that my PC is trying to connect, but I'm not able to get through.
Is it normal for the Username and Group to be nobody/nogroup? -
If you used WinSCP to set perms, my advice is do not do that.
Oh, ok thanks for the tip. I didn't know that there was an issue with WinSCP.
Do not try to edit /etc/samb/smb.conf directly it's owned by OMV system.
I haven't made changes to it directly. Thanks for the testparm info, that's that info I was looking for by viewing smb.conf.
explain what "restrictions" you are trying to use, what account(s) and/or group(s) you may have added to OMV and what share type you wish to use.
I have simplified things while trying to sort out the issues. I have only 1 account called docker. It's in use with a NFS share for a LCX running some containers that need access to config files and data on the SnapRAID array under OMV.
From Windows, I'm trying to access a single SMB share. Ideally access would be restricted to user credentials. However right now I have it set to Guests Allowed and Browseable.
Using OMV's Reset perms, I have the following output.
Clearing ACLs ...Changing owner to root:users ...
Change directory permissions to 2777 ...
Change file permissions to 666 ...
END OF LINE
█
When I try to access the SMB share, I get the error "You do not have permission to access \\OMV6\testshare..."
Ideally I would have multiple shares, some that are guest accessible, and others that are restricted to certain users or groups. But for a first step, I just want to get this one guest share working.
-
I can't get SMB shares to work properly. I've tried following the tutorials specific to OMV but haven't had luck.
My NFS share to another Linux host works fine.This OMV6 install is in Proxmox as a VM, not an LCX.
I also had the shares working for a while without any restrictions, that was the only way I could get them to work. Then when trying to turn on access restrictions, they all failed. I've reverted the settings back to how they were, but no luck. Either way, having them wide open isn't a long term option here, but as a first step if I can get this working at all, I'll be happy.
ZitatAlles anzeigen# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
#======================= 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
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
map to guest = Bad User
use sendfile = yes
aio read size = 1
aio write size = 1
time server = no
wins support = yes
disable netbios = yes
multicast dns register = no
# Special configuration for Apple's Time Machine
fruit:aapl = yes
fruit:copyfile = yes
fruit:nfs_aces = no
# Extra options
access based share enum = yes
#======================= Share Definitions =======================
[testshare]
path = /srv/dev-disk-by-uuid-d13fa166-9023-4b9c-b3b6-0c1ef13b9947/Media/testshare/
guest ok = yes
guest only = no
read only = no
browseable = yes
inherit acls = no
inherit permissions = no
ea support = no
store dos attributes = no
vfs objects =
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
read list =
write list =
The only thing that seems to stand out to me is the line map to guest = Bad User
-
I've been working away at restoring this system. I decided to make the jump to proxmox and now have an OMV6 install running as a VM.
I've also created a TurnKey Linux CT in Proxmox to run docker and portainer.
When trying to restore the /docker/ folder and contents, I'm running into issues. 1st time the copied data was 3x larger on disk than the uncompressed files on Windows. 2nd time, I ran into errors with the windows file copier. 3rd attempt I tried using Teracopy, but it ran into 1000's of errors. It seems like all the files that caused errors are .symlink and .alias. Any ideas?
I also tried to mount the dd archive as a loop device or something like that, but I got errors about "can't read superblock" or something similar. But maybe that's because this dd archive isn't a full disk. What's the best way for me to extract this archive from within Linux? I can't seem to mount it, and extracting it in Windows seems to cause issues with the file types mentioned above. -
sharerootfs was missing. Once I installed that plugin, the issue is resolved.
Thank you! -
What is the output of: dpkg -l | grep openme
root@OMV6:~# dpkg -l | grep openme
ii openmediavault 6.0.37-1 all openmediavault - The open network attached storage solution
ii openmediavault-clamav 6.0-9 all openmediavault ClamAV plugin
ii openmediavault-compose 6.0.4 all OpenMediaVault compose plugin
ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
ii openmediavault-mergerfs 6.2 all mergerfs plugin for openmediavault.
ii openmediavault-omvextrasorg 6.1.1 all OMV-Extras.org Package Repositories for OpenMediaVault
ii openmediavault-resetperms 6.0.2 all Reset Permissions
ii openmediavault-snapraid 6.0.4 all snapraid plugin for OpenMediaVault.
-
I've moved my physical OMV server to virtual. The previous install was OMV5, the new is s OMV6. It's a fresh install on Proxmox as a VM. SAS controller is passed through to the VM.
I recreated the snapraid array in OMV6 and started a sync. There was an error about ignoring a special socket file, but the pre-hash started working away. I ended up having to cancel the hash. Before I restarted, I wanted to add an exclusion rule to the snapraid config for that socket file. When I click on the Browse Directory icon in the Rules>Create screen, I get the following error.
500 - Internal Server ErrorFailed to execute XPath query '//system/fstab/mntent[uuid='79684322-3eac-11ea-a974-63a080abab18']'.
Running blkid doesn't show a device with that uuid.
-
post the output of ls -al <path to backup>
The last time I tried the boot the system after a restart it was pretty borked. I can try that and let you know.
I was wondering if I could tell from the dd.gz archive? I extracted the .dd archive out and looking inside, it seems to just be a full directory listing of the boot drive. Does a "ddfull" also have partition info? -
dd or ddfull? It makes a difference.
I don't remember. Is there a way to tell from the archive itself?
use systemrescue to restore dd/ddfull
From system-rescue.org?
I tried to run omv-release-upgrade but the system now boots into recovery mode so it doesn't seem to be possible.
What about if I just install OMV6 overtop of the existing v5 install? Will that overwrite settings or settings and data? I have my docker directory on the boot drive still, I never got around to figuring out how to relocate it. -
Then using the apttool plugin to install it should still satisfy that requirement.
Oh, I didn't know about that plugin. Thank you!
Not sure what you are doing with QSV but I think the binaries you are using need to be compiled with QSV support. I honestly don't remember reading about anyone using qsv.
QSV is pretty great. It's efficient, comparisons have said it can be better than NVENC, and in my case, included in my CPU.
I would restore your system from backup. It is a mess.
I have my backup, but not sure how to use it. I used the built-in OMV backup tool to create a DD archive. I think it's a full image of the boot disk.
I've read the suggestion of using the clonezilla live disk to run the DD commands. Does that make sense?
-
Zitat
dpkg -l openmediavault
rc openmediavault 5.6.26-1
ZitatOMV does not determine any of the drivers that are installed by default. Debian does. OMV is just a package installed on Debian.
I don't think a plugin is needed to install a package - sudo apt-get install intel-media-va-driver or install the apttool plugin and add it.
Yeah fair. For someone like me Debian is almost invisible though. The OMV GUI, is the only thing I want to interact with, if I can help it. OMV is kind of a pre-packaged suite of features all grouped in a nice GUI, it's great.
I've spent hours trying to get QSV working, without luck. It would be awesome if this was added at some point. I've tried so many different ways of adding the drivers. Either there's some dependency I don't have, or it installs fine, but still won't show up as a render device. I'm nearly at the point of buying an Nvidia card and calling it a day.5.6.26 was the last 5.x version - http://packages.openmediavault…ol/main/o/openmediavault/
Oh where did you find that? I went to this page and clicked the link to the installation images archive.
https://www.openmediavault.org/?page_id=77ZitatWhat is the output of: dpkg -l | grep openme
dpkg -l | grep openme
rH omvextras-unionbackend 5.0.2 all union filesystems backend plugin for openmediavault
rc openmediavault 5.6.26-1 all openmediavault - The open network attached storage solution
rc openmediavault-backup 5.2.4 all backup plugin for OpenMediaVault.
rc openmediavault-clamav 5.0.13-1 all openmediavault ClamAV plugin
rH openmediavault-diskstats 5.1.1-2 all openmediavault disk monitoring plugin
rc openmediavault-fail2ban 5.0.5 all OpenMediaVault Fail2ban plugin
ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
rH openmediavault-locate 3.5 all locate plugin for OpenMediaVault.
rH openmediavault-omvextrasorg 5.6.6 all OMV-Extras.org Package Repositories for OpenMediaVault
rH openmediavault-resetperms 5.0 all Reset Permissions
rc openmediavault-sharerootfs 5.0.2-1 all openmediavault share root filesystem plugin
rH openmediavault-snapraid 5.0.8 all snapraid plugin for OpenMediaVault.
rc openmediavault-snmp 5.0.3-1 all openmediavault SNMP (Simple Network Management Protocol) plugin
rH openmediavault-symlinks 5.0 all OpenMediaVault symlinks plugin
rH openmediavault-unionfilesystems 5.1.4 all Union filesystems plugin for OpenMediaVault.
-
This page says you can upgrade from to 6 if you're on 5.6.18. But looking in the release archive, it looks like v5 ended with 5.6.13? The majority of the system is still working, network shares, all my docker containers, etc. I thought omv-firstaid might list the current version so I tried to run that, but it said command not found.
-
Ahhh, Buster vs Bullseye. Never tinker while tired.
I have backups, but I've been wanting to check out v6 so think I'll go that route. Anything I need to watch out for with the upgrade to 6 given the right mess I made of this v5 install? With the web GUI down, I'm not sure how to tell which version of OMV I'm on. I'd assume the latest version of 5. When I run uname -a it says Linux 5.10.0-0.bpo.12-amd64 #1 SMP Debian 5.10.103-1~bpo10+1 (2022-03-08) x86_64 GNU/Linux. Does that mean I'm on v5.10?
I'm getting new errors today. Below is one email.
ZitatAlles anzeigen/etc/cron.daily/openmediavault-check_locked_users:
/etc/cron.daily/openmediavault-check_locked_users: 25: .: Can't open /usr/share/openmediavault/scripts/helper-functions
run-parts: /etc/cron.daily/openmediavault-check_locked_users exited with return code 127
/etc/cron.daily/openmediavault-flush-mailq:
/etc/cron.daily/openmediavault-flush-mailq: 31: .: Can't open /usr/share/openmediavault/scripts/helper-functions
run-parts: /etc/cron.daily/openmediavault-flush-mailq exited with return code 127
/etc/cron.daily/openmediavault-pending_config_changes:
/etc/cron.daily/openmediavault-pending_config_changes: 25: .: Can't open /usr/share/openmediavault/scripts/helper-functions
run-parts: /etc/cron.daily/openmediavault-pending_config_changes exited with return code 127
It's frustrating that the QSV drivers don't come pre-installed on OMV. I sure the dev's have their reasons. I wonder if a plugin package could be a good fit for adding the QSV support?
-
I ran into an interesting issue today. The Update Management list is huge. Tried to select all and install, but got this following error.
ZitatAlles anzeigenThe following packages have unmet dependencies:
libldb2 : Breaks: libldb1 (< 2:2~) but 2:1.5.1+really1.4.6-3+deb10u1 is to be installed
libpolkit-backend-1-0 : Depends: libpolkit-gobject-1-0 (= 0.105-25+deb10u1) but 0.105-31+deb11u1 is to be installed
libpython-stdlib : Depends: libpython2-stdlib (= 2.7.16-1) but 2.7.18-3 is to be installed
libpython2.7-stdlib : Depends: libpython2.7-minimal (= 2.7.18-8) but 2.7.16-2+deb10u1 is to be installed
Breaks: libpython-stdlib (< 2.7.18) but 2.7.16-1 is to be installed
Breaks: python (< 2.7.18)
Breaks: python-minimal (< 2.7.18) but 2.7.16-1 is to be installed
php-common : Breaks: php7.3-common but 7.3.31-1~deb10u1 is to be installed
python : Depends: python2 (= 2.7.16-1) but 2.7.18-3 is to be installed
python-samba : Depends: samba-libs (= 2:4.9.5+dfsg-5+deb10u3) but 2:4.13.13+dfsg-1~deb11u3 is to be installed
python-tdb : Depends: libtdb1 (= 1.3.16-2+b1) but 1.4.3-1+b1 is to be installed
python2 : PreDepends: python2-minimal (= 2.7.18-3) but 2.7.16-1 is to be installed
python2.7 : Depends: python2.7-minimal (= 2.7.18-8) but 2.7.16-2+deb10u1 is to be installed
Breaks: libpython-stdlib (< 2.7.18) but 2.7.16-1 is to be installed
Breaks: python (< 2.7.18)
Breaks: python-minimal (< 2.7.18) but 2.7.16-1 is to be installed
python3-yaml : Breaks: libpython-stdlib (< 2.7.18) but 2.7.16-1 is to be installed
Breaks: python (< 2.7.18)
Breaks: python-minimal (< 2.7.18) but 2.7.16-1 is to be installed
E: Unable to correct problems, you have held broken packages.
<<< *************************************
This is just a snippet. Here are the full logs. https://pastebin.com/qFnbCgMN https://pastebin.com/k3b6zQmx
Yesterday I added an entry deb http://ftp.de.debian.org/debian bullseye main non-free to /etc/apt/sources.list.d/. After that I installed intel-media-va-driver. During that install it asked me to replace /etc/ssh/sshd_config with an updated version from the package maintainer, which I did. Side note, I still can't get HWA with QSV.
Assuming this new issue is related, but not sure how, or how to fix it.
