So today I changed shares: appdata domains syslog system from cache<--Array to cache only to speed things up. Prior to making that change, I brought down docker. Issued the mover, made the change, brought docker back up. Everything came up fine. Except the unassigned device that I have a CCTV drive not in the array that I use for my frigate server ( not running on unraid ) The unassigned device lost its name, it is now dev1, where it used to be frigate. When I go into the settings, share, and automount are turned off. I turn them on, add the name BACK, and hit apply. Task completed, I click done. Now. I got to the unassigned devices setting under settings, and under NFS settings, Enabled NFS export is set to NO. I set it to YES, and click apply. Page refreshes, and its set to No. Looking at the syslog, I get this when I set the option to Yes: Apr 27 11:24:41 server1 unassigned.devices: Set Disk Name on 'ST6000VX009-2ZR186_ZVY00GYH (sdf)' to 'frigate' Apr 27 11:24:51 server1 ool www[4265]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'nfs_settings' Apr 27 11:24:52 server1 unassigned.devices: Updating share settings... Apr 27 11:24:52 server1 unassigned.devices: Share settings updated. Apr 27 11:25:35 server1 unassigned.devices: Set Disk Name on 'ST6000VX009-2ZR186_ZVY00GYH (sdf)' to 'frigate' Apr 27 11:25:39 server1 unassigned.devices: Mounting partition 'sdf1' at mountpoint '/mnt/disks/frigate'... Apr 27 11:25:39 server1 unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/sdf1' '/mnt/disks/frigate' Apr 27 11:25:40 server1 kernel: XFS (sdf1): Mounting V5 Filesystem Apr 27 11:25:40 server1 kernel: XFS (sdf1): Ending clean mount Apr 27 11:25:40 server1 unassigned.devices: Successfully mounted '/dev/sdf1' on '/mnt/disks/frigate'. Apr 27 11:25:40 server1 unassigned.devices: Adding SMB share 'frigate'. Apr 27 11:25:40 server1 unassigned.devices: Warning: Unassigned Devices are not set to be shared with NFS. Apr 27 11:25:54 server1 ool www[10136]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'nfs_settings' Apr 27 11:25:54 server1 unassigned.devices: Updating share settings... Apr 27 11:25:54 server1 unassigned.devices: Share settings updated. When I go back to main, under unassigned devices, the drive that WAS labeled Frigate, is now again DEV1, and the share and automount options are UNCHECKED. I've tried setting the shares back to cache<---Array. Running the mover, and nothing is fixing it. It's completely messed up. How do I get the system shares running on cache only, and get my NFS share back? It's incredibly important.

I see the issue and will have a fix later today.

NFS share on Unassigned device broken after share modification

Followers

Start new topic
Reply to this topic

First page
Prev
1
2
Next

Solved by dlandon

May 7, 20242 yr

Go to solution

May 8, 20242 yr

25 minutes ago, Original_Vecna said:

Needed to add:
192.168.1.79(rw,sec=sys,insecure_locks,sync,no_root_squash)

Added the NFS share direct in my docker container, removing the extra mounting of nfs share in the linux system, and handling it direct in docker-compose.

Works PERFECT now! Thanks again!

Excellent. Glad you got it sorted.

Quote

First page
Prev
1
2
Next

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Share on Bluesky
Share on X
Share on Facebook
{lang="reddit_text"

Followers

Go to topic listing

NFS share on Unassigned device broken after share modification

Featured Replies

Solved by dlandon

Join the conversation

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)