Original_Vecna

Thanks, that's exactly what I'm trying to do. When I do it, I click apply. The page refreshes, and the option is back to No. Again, when I do that, the name and options of my disk in Unassigned Devices resets completely. Automount, share, and the name "frigate" reverts to dev1 and the options are lost. Syslog gives me: 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.

Correct. But in the shares screen, it's listed like this, that's what I was referring to. Which is what they were set to.

That is exactly what I had done originally before changing to cache only. Brought down docker ( had no vms actively running ) the shares already were cache <---Array. So I instituted the mover. Checked the syslog, and nothing was copied over. Changed to cache only. Restarted docker. I ended up moving libvirt.img from /mnt/user/system to /mnt/cache/system and the fix common problems error about system having files still on the array went away. But the NFS share for unassigned drives is still chooched. I was able to force it up temporarily by adding the entry to /etc/exports, but I'd prefer to get it working natively, as exports tends to wipe itself clear of any modifications.

I am currently running 2024.04.22 Attached is the ud_diagnostics Thank You! ud_diagnostics-20240427-163444.zip

In Fix Common Problems I also have: Share system set to cache-only, but files / folders exist on the array You should change the shares settings appropriately or use the dolphin / krusader docker applications to move the offending files accordingly. Note that there are some valid use cases for a set up like this. In particular: THIS More Information I've followed this link: But what this post says to do doesn't exist anymore. "Prefer" is not an option. I am running Unraid 6.12.10 This option no longer exists apparently.

Also have tried rebooting the server.

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.

Got it! Thank you so much!

Ahhh ok. What specifically should I have there? Just as you have? The line I keep adding to my /etc/exports is: /mnt/disks/frigate 192.168.1.187(rw,sync,no_subtree_check)

Sorry, not sure what exactly you mean. I'm supposed to put something here?

I have a frigate server that connects to my unraid server via NFS share to an unassigned 24x7 cctv drive device on unraid. Somehow, my /etc/exports is being reverted back to a status of not including the frigate share. # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. "/mnt/user/fcshare" -fsid=100,async,no_subtree_check 192.168.1.187(rw,secure) This is the base version of /etc/exports. After a reboot, and all the time, this is what it reads. Now, the fcshare was entered by me at SOME point, for a filecloud demo. And it saved persistently. I'm trying to replace it with: /mnt/disks/frigate 192.168.1.187(rw,sync,no_subtree_check) I can add it manually and save, and it will save. And my NFS share will have access to connect. But if I restart the machine, the array, or even RANDOMLY, it reverts back to the fcshare version. Which makes no sense to me. I don't have ANY scripting that reverts the exports file. Though I DID try creating a script that adds the line back on array start. Through googling, it appears as though /etc/exports doesn't persist. Though I did make it happen at SOME point, because I can't seem to get rid of the fcshare export. Can someone point me in the right direction here? It's driving me bonkers.

For anyone who finds this in the future, the fix was incredibly simple, and could have been shared in two seconds. Enter your Unraid IP into the remote server address field. That's it. It goes against all common sense, but that's all it was. Thanks again for the super useful help @itimpi Additional: localhost also works.

Thanks, but I don't have the space to fill up on my flash device.

Ok, I'm ASKING because I don't know how to do this, and that article, which I've gone through, doesn't specify what I'm asking. OR, I'm completely bereft of all mental faculties. Which in this ask, because of your reply, I'm guessing is the likely culprit. Could you PLEASE be more specific? I'm extremely frustrated at this point, dealing with major outages for over a week now on my own, and just need the answer. The portion about remote server is exactly for that. A remote server. So why would I assume A) I need to fill that out, and B) WHAT I need to fill out if the server isn't remote, and is actually local? I don't understand why Unraid needs remote server info for a local syslog server.

Server is an intel dell R710, the only thing that has changed recently was an upgrade to a single port Realtek 8215 from the on board 4 port 1G nic. One of those crashes could have certainly been due to the card, but I've since found the Realtek 8215 drivers on the community app store ( didn't know I needed to install drivers specifically in unraid and rebooted ). Thank You @itimpi for the tip. So...these settings can often times get confusing. I don't have a remote server, and I don't want it written to the flash drive. I've created a share on the cache drive that I want the logs written to. Common sense says selecting that share in the "Local Syslog Folder" would mean your syslog is now being written to that share. Is it possible to have it behave this way?

These are my current setting for the syslog server: Doesn't appear to do anything. Syslog itself appears to be working fine, I can logger <MSG> and it displays in syslog. Apr 12 17:24:32 Unraid Server root: Test message for syslog But it's not writing to the directory on the cache drive I specified.

Hey @JorgeB, thanks for replying! So I do have syslog server enabled, and it was pointed to my media share. I checked that directory, and there isn't anything in the syslog there. I've since created a share on the cache drive called syslog, and attached the syslog server to it. In the off chance this doesn't fix this issue, is there anything I can do to test the functionality of the syslog server? Cause it doesn't appear to be doing anything.

R710. Been running for years with no issues. Recently installed duplicacy and am working to configure backups to a separate Unraid connected via tailscale with an NFS share. I was able to get a couple backups completed, but my main Unraid server keeps going off the network, when I plug in an external monitor to the server, I get no video. The only way to get it back up and running, is cold booting the server, which as you can imagine is unacceptable. Can anyone tell me how I can figure out what is going on here? Today when it locked up, no backups were running, I was remoted into the server trying to get the NFS share to mount again, an poof, offline and crashed. Need to get this sorted ASAP. Unraid Pro running 6.12.6

Yes. Which is again, why I'm here posting. I believe I already said I checked online and couldn't find anything of use. That little blerb did nothing to help, the "procedure" on that page does not work.

I'm trying to configure two unraid servers to connect remotely for duplicity backups from my main server, to the client server. I'd like use the built in VPN manager, but try as I might, am unable to get them to connect to one another. Is there a guide to getting this connection working? I've searched online, and tried everything.

Will do.

From everything I can find online, Firmware on 82599 network controller is ROM based and generally speaking not upgradable.

So...? Is there any more information I can provide to get this fixed?

I've found this, but these are drivers: https://www.intel.com/content/www/us/en/download/14302/intel-network-adapter-driver-for-pcie-intel-10-gigabit-ethernet-network-connections-under-linux.html There is nothing Unraid specific, and I can't compile my own drivers on Unraid using the ixgbe-5.19.6.tar.gz package.

There is none that I can find. This is a common card folks are using with Unraid, given the number of posts here. Is there truly no solution to this issue? If there is a firmware update, there should be documentation on where to find it, and how to apply it, no?