Problem with SMB - Mounting SMB on Windows & Mac

1. offizieller Beitrag

    I have had help from Soma regarding OMV 6 upgrade and the problems it caused. Amazing what he has helped me with getting OMV 6 clean and running well but I cant seem to get the pooled drives to mount. The files in the folders on OMV can be seen in Filezilla but when I try on Mac or Windows machines the folders dont mount and give a permissions error. I also check Snapraid as I was trying to reset permissions or sort permissions and get 500 error.


    I have attached Screenshots of what I am getting

    Thank in advance for any help

  • DNUKaen

    Hat das Label OMV 6.x hinzugefügt.
    • Offizieller Beitrag
    Zitat von DNUKaen

    The files in the folders on OMV can be seen in Filezilla but when I try on Mac or Windows machines the folders dont mount and give a permissions error.

    Stupid question: Did you create shared folders and add them to a suitable service like smb or nfs? Did you give privileges to the used user to have access to them?

    Zitat von macom

    Stupid question: Did you create shared folders and add them to a suitable service like smb or nfs? Did you give privileges to the used user to have access to them?

    All of this has been done but the Mac or PC sees the OMV on the Network but wen you try to access the folders it doesnt allow and says to either contact administrator or a permissions problem but they are all set correctly with the help from SOMA - who is amazing by the way - He tried SAMBA and NFS but cant get to access the folders on the server without it being kicked back


    I was thinking is it an IP address problem or OMV firewall but it was working fine on OMV5 before the upgrade to 6 just wondering what permission or connection is incorrect and not allowing access to the folders


    Any ideas would be great

    To whom may help:

    TL;DR

    After some struggle, and a borked upgrade to OMV6, the OS was cleaned (thank you ryecoaaron ).


    The issues started with the Shares due to a failed upgrade from OMV5s plugins UnionFS and MergerFolders to the new OMV6 mergerfs plugin.

    After recreating a new POOL and fixing the paths on Storage && SMB, the files/folders weren't available anymore although the shares are still seen on Windows Explorer && Mac Finder.

    The folders (from the Shares) on the disks had a mix of OWNER:GROUP.

    1st - The folders were chowned recursively to USER ID 1000:GROUP ID 100 which has ACL/Permissions setted on the STORAGE->SHARED to RWX

    2nd - The disks were all verified in to confirm the folders that were needed on the POOL, were named with the same name and existed on the same level
    For eg: /srv/dev-disk-xxxxxxxxxxx/FOLDER1/FOLDER2 matches /srv/dev-disk-yyyyyyyyyy/FOLDER1/FOLDER2, and so on.

    FOLDER1 is owned by root:users and FOLDER2 is by ID1000:users
    FOLDER2 is one of the SHARED FOLDER that should be available on SMB.

    3rd - The SMB SHARES were verified and they are with the same settings as on OMV5 although don't know if are correct since they have ACL enabled and Permissions disabled.


    After failing,

    A NFS SHARE was created with settings insecure, rw, subtree_check and with access to LAN clients 10.229.1.0/24 (OMV IP is 10.229.1.180 ) and the service enabled.

    FSTAB shows the exported share.


    On the Windows PC, run the command mount -o anon \\10.229.1.180\export\Media N: and it came out successfully.

    Run mount and there's nothing stating that it was mounted.

    On the Explorer, it keeps clashing with the "No permission to access this share".


    Same on Mac.


    If someone can shed a light, it would be great.

    Soma & DNUKaen Did the default share options values of create mask & directory mask change when going from OMV5 to OMV6?


    For SMB shares, the output of the following command as root at OMV6 CLi would be useful:


    Code
    testparm -s


    For any full folder path ( /srv/... ) referenced by testparm, list the output of these commands substituting the actual path details:


    Code
    namei --owners --modes /srv/....

getfacl /srv/.../folder1  

getfacl /srv/.../folder2


    As a double check post the output of these two commands, substituting the real account name of user accessing shares:


    Code
    id username

pdbedit -L | grep username






    I'm working in and out of office and not online with DNUKaen ATMbut can, at least post here some info I grabbed before the tried changes:


    Zitat von Krisbee

    Did the default share options values of create mask & directory mask change when going from OMV5 to OMV6?

    This is what was before on the SMB Shares:

    omv-showkey services  SMB


    omv-salt deploy run samba


    Later, I can run the same and see the differences.

    Thank you for any input, ;)

    Soma, I do not know if this is relevant or not but I run windows in "virtual box" inside Linux Mint using "bridged adapter" network settings. I used to use MSI B450-A-Pro_MAX motherboard build in Realtek network port and had a lot of problems with accessing OMV (NAS) samba shares from said "virtual box" as well as with my pfsense based custom router. Also Windows 11 would have a sporadic proble with updates. Couple of months ago I got dual port Intel 82576 NIC and disabled motherboard net interface. Since then I have no issues with connecting to OMV Samba shares, windows updates. My point is that it could be a Realtek chip based problem. Those Realtec chip based NICS are kind of "flake". From what you describe, IMHO, you are doing everything right, as always, I might add. The only variable I can see is NIC.

    Linux Mint (Edge) EndeavourOS Arch Linux

    OMV7 NAS, bond0 LACP, Fractal Design Define R5 Case, Kodi "Omega", FreeBSD pfSense Plus firewall/router

    Hi


    I agree Soma is an amazing person.


    Just to add the server is a HP Proliant Microserver Gen 8 and was working fine with OMV 5 installed. Yes as I have found out with Somas help the OS and folders were in a bad way but it was all working before the Updage to OMV 6 which seemed to cut connections to the server


    The server is seen by both the PC I have Plex Media Server on & Mac that I access the server on to add and delete files. It’s wen u try to access the folders

    andrzejls Counter evidence about realtek network adapters. On my ageing sandybridge m/board it's a RLT8211E chip. No problems with networking when running vms or lxc in virt-manager or vbox.. As far as vbox is concerned, picking the right virtual nic type and setting promiscuous mode can make a difference, or did in the past. It all depends what realtek chip is on your m/broad, your RTL 8111H seems to be a potential problem one. It might have worked better if you had installed r8168-dkms.



    I await output re: current state of OMV6 on machine in question.

    Zitat von Krisbee

    andrzejls Counter evidence about realtek network adapters. On my ageing sandybridge m/board it's a RLT8211E chip. No problems with networking when running vms or lxc in virt-manager or vbox.. As far as vbox is concerned, picking the right virtual nic type and setting promiscuous mode can make a difference, or did in the past. It all depends what realtek chip is on your m/broad, your RTL 8111H seems to be a potential problem one. It might have worked better if you had installed r8168-dkms.



    I await output re: current state of OMV6 on machine in question.

    Well, that might be true regarding Realtek chips for most part. My problem with Realtek began when I started "IDS/IPS" Snort in pfsense router. Same issue was if I tried Suricata "IDS/IPS". With Realtek chips (known issue in pfsense professional world) Snort would fail updates due to MDS checksum error. Changing to Intel based chip NIC fixed the issue.

    Linux Mint (Edge) EndeavourOS Arch Linux

    OMV7 NAS, bond0 LACP, Fractal Design Define R5 Case, Kodi "Omega", FreeBSD pfSense Plus firewall/router

    So I have a Mac Studio which is M1 Max chip but as I say it was fine with OMV 5 but the Upgrade to OMV 6 has caused no end of problems lol Just find it strange that an upgrade would do this to all connections but its obviously connecting as it shows the OMV shared folders but permissions arent allowing access to the folder data for some reason

    DNUKaen I'm pretty sure Soma would have checked your settings. As I understand it you can see the shared folders in Windows but can't access them because of a permissions error. I understand you want it working ASAP, but I would rather wait for feedback/output from those commands I posted before making further comment. Getting that data is really the only way to be sure what the current state of your folder/share settings are.


    I have no experience of MAC OS, but you'll find a few forum post re: problems with SMB shares in various versions of MAC over the last few months. I think it would be easier to concentrate on Windows first.

    Zitat von Krisbee

    DNUKaen I'm pretty sure Soma would have checked your settings. As I understand it you can see the shared folders in Windows but can't access them because of a permissions error. I understand you want it working ASAP, but I would rather wait for feedback/output from those commands I posted before making further comment. Getting that data is really the only way to be sure what the current state of your folder/share settings are.


    I have no experience of MAC OS, but you'll find a few forum post re: problems with SMB shares in various versions of MAC over the last few months. I think it would be easier to concentrate on Windows first.

    Oh don’t worry I’m not touching a thing until I hear from Soma. My knowledge isn’t gd at all regarding server and OS stuff. But Soma has enlightened me.


    One thing is correct though I’m never doing an upgrade or touching this server again if I get access


    A question - wud I have encountered similar problems if I had just don’t a fresh install?

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden