scubanarc

Members
  • Posts

    29
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

scubanarc's Achievements

Noob

Noob (1/14)

2

Reputation

1

Community Answers

  1. I had this exact same issue, and I think I found the problem and the fix. In my case, this was happening on files that had embedded movie posters as a stream. It was usually stream #3 (after subs). These streams seem to force a filter command on ffmpeg, but unmanic is requesting a streamcopy, so you get the error above. The simplest solution is to add the plugin called "Strip all image streams from file" in your stack, above the encode. As soon as I did that all of my encodes worked fine.
  2. To anyone considering installing this, a fair warning. I have talked to the mods at irc.irchighway.net and they told me that this docker WILL get your IP address banned on their channel. They told me that the script abuses the search bot, causing the banhammer to react.
  3. Try running the following on your client: nfsstat -c Does it say "nfs v4"?
  4. Are you sure that your client is using NFSv4 and not v3?
  5. Tried it, runs great, thanks! Great idea to make a template out of it... I've search the CA a few times and have been surprised it wasn't there already. Amazingly, the performance appears identical in Docker compared to bare-metal.
  6. I want to run the following command: iperf3 -s And keep it running as a service, after every reboot. Basically I need an iperf service always running for various machines to hit, and the Unraid server is the best choice. In SystemD I'd just create a unit file and enable it. In slackware I probably have a service file in /etc/rc.d. In Unraid... I'm not sure since /etc is not persistent. What's the best way to run a persistent, custom service in Unraid. Running it in a VM incurs a bit of overhead and makes the readings unreliable. This needs to run directly on Unraid.
  7. I went ahead and upgraded from 6.9 to 6.10 yesterday and crossed my fingers that the NFS mounts would not break. Great news... nothing broke! Literally nothing NFS related broke at all. It was wonderful. If anyone else is in this predicament and holding back upgrading to 6.10 because of the change from NFSv3 to NFSv4, I just wanted to share that for me it was a seamless experience. It appears that Unraid does not export a root filesystem, so there is no pseudofilesystem to think about. I feel like this is fine in an Unraid environment where your exports are all already stored under /mnt/user/ anyways, and you're really not supposed to manage your /etc/exports file manually. Thank you @dlandon for your helpful replies.
  8. So this means no bind mounts, correct? Also, it looks like Unraid is not using any sort of root filesystem, either, because I do not see fsid=0 anywhere. I think that answers my questions. Thanks.
  9. NFSv4 uses a very different concept of exporting paths. You have to export a root filesystem and then export paths relative to that root filesystem. This article explains it well: https://ertw.com/blog/2007/06/24/migrating-from-nfs3-to-nfs4/ How does Unraid handle this? Does Unraid export all of /mnt/users as the NFS4 root and then export shares from there? If so, then my clients will have to map to just "/sharename" instead of "/mnt/user/sharename". This really needs to be addressed in the 6.10 release notes.
  10. I'm in the same boat. I have multiple UnRaid licenses and the only reply that I've gotten from them is "Upgrade to 6.10.x to fix stale file handles", but when I ask for details about how they fall silent. Hey Limetech, can you please document how to convert from NFSv3 over to NFSv4? At least address the issue of whether Unraid handles the pseudofilesystem in exports or not. If Unraid does not handle the pseudofilesystem, then what exactly do I need to do?
  11. Still wondering if UnRaid takes care of the pseudofilesystem or if we have to manage it by hand? How exactly does UnRaid support NFSv4?
  12. Or does UnRaid take care of the pseudofilesystem for you, and you just use the GUI to say "Export" and that is all? We really need some more documentation on this before I jump in.
  13. NFS4 uses a new pseudofilesystem concept. It is not a straightforward migration path from NFS3 to NFS4. You most likely need to create a "root" nfs folder and share that as the pseudofilesystem root, then "bind mount" all of your desired exports into that folder. I have not made the leap because I'm afraid of the down-time. Has anyone else made the upgrade from NFS3 to NFS4 on UnRaid? If so, how did it go?
  14. Interestingly that doesn't mention that change from NFSv3 to NFSv4. That's such a major change that you'd think it would be included in the release notes. All my web searches about NFSv4 are not productive. Any other information you can share? NFS is a major part of my workflow, so I want to read everything I can before taking the plunge.