I have been getting these errors non stop in my logs for a while now.  So far everything looks like its working but its related to my non-array disk i use for my Zoneminder install (cameras)

 

May  3 16:34:22 domain  emhttpd: error: share_luks_status, 6173: Operation not supported (95): getxattr: /mnt/user/cctv
May  3 16:34:23 domain  emhttpd: error: share_luks_status, 6173: Operation not supported (95): getxattr: /mnt/user/cctv
May  3 16:34:24 domain  emhttpd: error: share_luks_status, 6173: Operation not supported (95): getxattr: /mnt/user/cctv
May  3 16:34:25 domain  emhttpd: error: share_luks_status, 6173: Operation not supported (95): getxattr: /mnt/user/cctv
May  3 16:34:26 domain  emhttpd: error: share_luks_status, 6173: Operation not supported (95): getxattr: /mnt/user/cctv
May  3 16:34:28 domain  emhttpd: error: share_luks_status, 6173: Operation not supported (95): getxattr: /mnt/user/cctv
May  3 16:34:29 domain  emhttpd: error: share_luks_status, 6173: Operation not supported (95): getxattr: /mnt/user/cctv

 

Note i replaced my server name with "domain".

 

attaching the logs as well.

 

Edited May 5, 20233 yr by tvd1

How is /mnt/disks/cctv mounted? How are you sharing it from /mnt/user? 

Edited May 4, 20233 yr by apandey

See the screenshot.  its showing up as /mnt/disks/cctv

Edited May 4, 20233 yr by tvd1

You have a User Share named ‘cctv’ that has files on disk4 and this is what the error message is referencing.  This is NOT the same as the external drive mounted at /mnt/disks/cctv.   Is this setup intentional?

8 hours ago, itimpi said:

You have a User Share named ‘cctv’ that has files on disk4 and this is what the error message is referencing.  This is NOT the same as the external drive mounted at /mnt/disks/cctv.   Is this setup intentional?

 

Its only intentional as I wanted to keep the data drive for Zoneminder off the array, due to all the constant writes.  I'm assuming I should not have set it up this way? Its running fine but the errors wont stop flooding the logs.

5 minutes ago, tvd1 said:

 

Its only intentional as I wanted to keep the data drive for Zoneminder off the array, due to all the constant writes.  I'm assuming I should not have set it up this way? Its running fine but the errors wont stop flooding the logs.

Do you have something configured to write to /mnt/user/cctv ?   

 

From your comment above I would have expected Zoneminder to be configured to use /mnt/disks/cctv which is the UD drive - is this the case?

No i have it set up like this..

Is /mnt/user/cctv linked to /mnt/disks/cctv in any way? If yes, how? 

8 minutes ago, apandey said:

Is /mnt/user/cctv linked to /mnt/disks/cctv in any way? If yes, how? 

 

That symlink is the problem. /mnt/user needs to be fully managed by unraid, and the errors are because it is encountering a symlink which is not a shfs mount. Trying to get status of that share in expected way is failing

 

If you want this shared, use the unassigned devices share functionality (it won't be listed under shares) or manually configure smb-extras in samba settings

Edited May 4, 20233 yr by apandey

3 hours ago, apandey said:

If you want this shared, use the unassigned devices share functionality (it won't be listed under shares) or manually configure smb-extras in samba settings

 

Okay! So thats a start, and makes sense.. But i'm not clear on how it should be configured.. So I looked at unassigned devices for both the drive and the share and sharing is on:

Or if i do the smb-extras, something like this would suffice?
 

path = /mnt/disks/cctv

comment =

 

1 hour ago, tvd1 said:

So I looked at unassigned devices for both the drive and the share and sharing is on

You will also need to enable sharing under SMB settings found in unassigned devices plugin settings. Usually that is enough and then UD will manage samba config

 

If you need specific instructions post in the dedicated plugin thread

Okay i did that but it had no affect.  I'll have to post over there to see exactly what i should be doing, because i think i've checked everything, short of adding code to smb-extras.

 

Edited May 5, 20233 yr by tvd1

Something external is still using /mnt/user, that needs to be used by Unraid only.

1 hour ago, tvd1 said:

Okay i did that but it had no affect.  I'll have to post over there to see exactly what i should be doing, because i think i've checked everything, short of adding code to smb-extras.

Don't add anything to the smb-extras.conf.  You may create more problems than you solve.  Samba configurations can be very touchy, plus UD manages the UD devices configurations for you.

 

Be sure to post diagnostics the next time you post.