Jump to content

Original_Vecna

Members
 View Profile  See their activity

  • Posts

    63

  • Joined

  • Last visited

 Content Type 

Posts posted by Original_Vecna

    NFS share on Unassigned device broken after share modification

    in General Support

    Posted

    At this point I don't think it has anything to do with you...I just don't know why all of a sudden this is happening. 

    If I run: dd if=/dev/zero of=/mnt/frigate_nfs/testfile bs=1M count=100 on the frigate server, it writes just fine, and if I spam it, unraid UD writes increment like they should.

    So the UD nfs share IS working...it's like Frigate forgot what to do. I've rebooted the server, verified the share is mounted properly, can touch and otherwise right to the share...

     

    Real noodle scratcher.

    NFS share on Unassigned device broken after share modification

    in General Support

    Posted · Edited by Original_Vecna

    @dlandon

    Hate to be a pain, but every since I got the new UD, and was abled to enable the NFS share for my UD, I'm having REALLY poor connection issues to it. My frigate server just isn't writing to it. The drive goes to sleep, Home assistant feeds are hit or miss, just really bad. I could previously sit on the Main Unraid page and watch the writes climb every sec with writes from my 10 cctv cameras. Now? It barely increments.

     

    This wasn't happening when I was juggling mounting previously. The service was excellent, it was the reliability that I occasionally had issues with. ( Dropping connection )

    NFS share on Unassigned device broken after share modification

    in General Support

    Posted

    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.

     

    NFS share on Unassigned device broken after share modification

    in General Support

    Posted

    4 hours ago, itimpi said:

    You should refer to the current documentation that covers that here.

     

    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.

    NFS share on Unassigned device broken after share modification

    in General Support

    Posted

    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.

    NFS share on Unassigned device broken after share modification

    in General Support

    Posted

    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.

    NFS share keeps disconnecting

    in General Support

    Posted

    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.

    Unraid server keeps becoming completely unresponsive, cold boot only way to get it back online.

    in General Support

    Posted · Edited by Original_Vecna
    Additional info

    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.

    Unraid server keeps becoming completely unresponsive, cold boot only way to get it back online.

    in General Support

    Posted · Edited by Original_Vecna

    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.

    Unraid server keeps becoming completely unresponsive, cold boot only way to get it back online.

    in General Support

    Posted

    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?

×
×
  • Create New...