So I've fumbled my way through installing OMV and letting it fully update itself, installed the MD plug-in, and after a certain amount of swearing, created a 5-drive RAID6 plus a couple of shared folders. I also created my standard 'me' ID. I can access the shared folders from my PC so it looks like I got things largely right. What I need to do now is to copy data from my Asustor NAS to OMV but I can't see how to mount one of the Asustor's shared folders as a CIFS folder. If I try to mount an OMV share as a CIFS folder on the Asustor I get "Unable to mount CIFS folder due to insufficient access permissions or incorrect password. (Ref. 5001)". I'm logging on as admin with my standard password so some suggestions as to what I've missed would be welcome.
How to define CIFS folder on OMV for Asustor NAS folder and access rights problem going from Asustor to OMV.
-
- OMV 7.x
- resolved
- Snapshot
-
ryecoaaron
Approved the thread. -
I would try doing it the other way around. Install the openmediavault-remotemount plugin and mount the remote resource on the OMV NAS. Commercial systems tend to be very unfriendly to other systems.
When mounting that remote resource, keep two things in mind.
1. Make sure you're using the appropriate permissions.
2. While you have that mount active in OMV, make sure the remote resource is available; otherwise, you'll receive errors that may be difficult to interpret.
Welcome to the forum.
-
-
Ah, thank you. Another plug-in needed and installed. I've created a CIFS folder under Remote Mount, added it to Shared Folders and SMB/CIFS / Shares then finally added it to File Browser. I then open the File Browser GUI only to be told "It feels lonely here...". If I select one of the local shared folders then it shows in the File Browser GUI. Permissions should be okay as I'm using the same password for admin throughout my servers.
Edit the shared folder and in the relative path field simply write a slash /
-
chente
Added the Label resolved -
However I now learn that File Browser can only handle one shared folder at a time which, for me, negates its usefulness.
That's a restriction imposed by this plugin. You can configure your storage so that shared folders reside in a single shared folder and configure the single folder in the plugin.
If you can't create that folder structure and need Filebrowser with all its features, you can install Filebrowser in Docker and stop using the plugin.
-
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!