scubanarc

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.

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.

Try running the following on your client: nfsstat -c Does it say "nfs v4"?

Are you sure that your client is using NFSv4 and not v3?

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.

bump

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.

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.

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.

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.

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?

Still wondering if UnRaid takes care of the pseudofilesystem or if we have to manage it by hand? How exactly does UnRaid support NFSv4?

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.

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?

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.

Awesome, great to know. Any major things to be concerned about with changing from 6.9 to 6.10, especially considering the NFS version change? I'd hate to lose all my mappings.

attached hal-diagnostics-20220826-0840.zip

I get stale file handles all the time on my user shares. Especially when I've done a long operation, or walked away for a long time. I come back, do an ls, and get the following: ls: cannot open directory '.': Stale file handle The easiest fix is to "cd .." and then cd back into the directory and all is well. This problem only exists on my unraid servers. None of my other servers do this. I know that this was a problem back in 2012 and that it was fixed. It appears to be a problem again now.

Don't we all! I think that you should focus on hardware. Unraid is a very stable operating system. If you are crashing every few days then there is (more than likely) something wrong with your hardware. I'd start with memtest86+ for a few days. This is never an easy problem to solve. If that passes, then try running with very few HDD (or, if possible, no HDD) for a few days and see if you are stable. There's usually something.

I rebooted in safe mode and it helped, the root permissions stayed 755. Then I rebooted back to normal mode and the root permissions broke to 775 again. I'm running the following plugins: Community Applications Intel GPU TOP Nerd Tools ProFTPd 1.3.6 (Plugin Version: 2020.03.10.1) Unraid.net User Scripts zabbix_agent Nerd Tools (Nerd Pack) enabled packages: - ncurses-terminfo-6.1.20191130-x86_64-1.txz - tmux-3.1.0-x86_64-1.txz User scripts: - Just a simple delete script, does this: #!/bin/bash find /mnt/user/camera/ -mtime +44 -type f -exec rm {} \; find /mnt/user/camera/ -empty -type d -delete Anything look suspicious?

Unraid 6.9.1 I'm not 100% what is going on here, but it seems that when I reboot I lose the ability to SSH with a keyfile. This is not about passwordless keyfiles, but about all keyfiles. I understand the /root/.ssh symlink and I know how to login with keyfiles. However, after a reboot they do not work anymore, and the error in /var/log/syslog is: Authentication refused: bad ownership or modes for directory / If I run "ls /" then I can see that the / filesystem is 775 (group has write). The solution for me is: chmod 755 / (group does not have write) Then my SSH keys work again. Is this normal Unraid behavior or do I have something doing this to me?

I installed the 'Intel GPU TOP' pluggin and it went fine. Then I rebooted, chose GUI mode, and after a bit of normal looking boot scroll I got the blinking cursor. It's not frozen, I can still SSH in to it, but the GUI never lights up. Any other suggestions?

No I have not done that, and I wasn't aware that I needed to. Thank you very much for the suggestion, I will try it and let you all know.

I still have no progress on this. I've tried everything I can think of. Why I try to boot GUI mode, no matter what all I can get is a blinking cursor on a black screen. The only video card I have is the onboard intel in the CPU.

I think that I'm in a similar boat as you, except I don't have a video card added, I'm just trying to boot the onboard. I have 2 suggestions for you (although neither worked for me): 1 - Disable UEFI and see if it works (in other words, do a traditional BIOS boot): 2 - Try the nomodeset trick: