theimmortal

I am running a fresh build of Unraid 6.12.0-rc7, but I experienced the same on RC6 and RC5. My CPU consistently fluctuates between 40% and 60% with spikes about every 10 seconds to 90% and 100%. I have narrowed it down to writing data to the array. The second the array is being written to, the shfs process starts using >100% CPU. I tested it by booting into safe mode, starting the array with just my torrent client downloading a single torrent at ~35MBps. I have tried qBittorrent, Deluge, and Transmission with the same results. At the same time, if I try to do any file copying, either local (drive to drive) or over the network it slows to 6-10MBps local 0-3MBps over network and my torrent speeds drop to ~15MBps. Stopping the torrent client completely and performing a transfer gives me decent transfer speeds of >100MBps local, but again with >100% CPU usage on the shfs process. If I stop the array and mount the exact same drives, I get >150MBps transfer rates and no spikes in CPU usage. I have been pulling my hair out trying to figure this out. In the pass couple weeks I have built and destroyed pools, arrays, and even raid0 arrays using both ZFS and BTRFS, and now have a standard Unraid array using XFS. It has been a while since I used Unraid, but I do not remember this problem previously. Does anyone have any ideas? unraid-diagnostics-20230609-1917.zip

I am using 6.12-rc2 and I have a zpool that I cannot import into the GUI because it has a mixed topology. Is there any way to run a script to import the pool on boot BEFORE the array starts?

Once I get this pool imported, I'll be transferring files to a new pool. It's almost 100TB of so it is going to take a bit of time to move everything off, destroy the old pool, create and then add as a second vdev to the new pool and then rebalanced. My goal is to have that all done before upgrading to 6.12.0. The new pool was created using ZFS 2.1.7, so hopefully it will work fine in 6.12.0. Nothing super critical, just something I wanted to understand how to do it so that if/when I run into a situation where I need a tool that I cannot get in the Community Apps I have multiple avenues. One that I can think of is a plugin to change the default shell to fish and manage the config files.

@ich777 You are incredible! Not to seem totally ungrateful, but could you show me how you are building the modules? I unfortunately created this pool from git master last year and it includes a feature flag that still has not made it into the official releases. I want to build a one-off so I can import this pool that is still separate from what gets automatically updated to the rest of the community since it would include "experimental" features that could have unknown adverse effects. I am also just interested in learning more about building packages for unraid and this provides a great opportunity for that.

Sadly, the unraid-kernel-helper plugin seems to have been retired. I checked on the github and I did not see any branches for beta. To be fair, the plugin is up to date. Most distros are shipping 2.1.7, I think 2.1.9 just dropped a couple days ago, and the feature flag I need unfortunately requires the latest git, since it hasn't made it into the releases yet. I do not use that feature, but unfortunately my zpool is too big to destroy and there is no way (that I know of) to downgrade an existing zpool to a previous version.

I have been trying to build a custom version of this module from my git fork but have been unsuccessful. I need to do this because I want to import a zpool that was built on TrueNAS Scale with a newer version of ZFS (with head_errlog feature flag). Is there a build script for this that I can adapt for this purpose? Thank you in advance!

The most recent version is 4.28.281. The version in the docker should update when you create a collection and connect with your zappiti player. If you want to avoid beta releases, do not select that option on your sever webui or in the player settings.

Sorry for the delayed response. Unfortunately, the export from the cloud is not working. It only works with other local servers, so other docker or Windows-based servers. This is a known problem with the cloud that Zappiti is working on a fix for. I have it in the notes that this is broken. As soon as it is fixed, or a workaround is developed, I will update this thread. In the meantime you have to scan everything into a new collection.

Reserved.

Overview: Docker container to install and run Zappiti Server app as a local Cloud to manage your library using your Unraid server. Application: Zappiti Server - https://www.zappiti.com/ Docker Hub: https://hub.docker.com/r/theimmortal/zappiti-server/ GitHub: https://github.com/theimmortal68/zappiti-server-docker/ Documentation: https://zappiti.uservoice.com/knowledgebase/topics/107133-zappiti-server-synology-en Notes: 1. This app is derived from the official Synology docker image, but has been successfully tested on Unraid. 2. The export feature on Zappiti Cloud is currently not working. This is a problem with the Zappiti servers and not the app itself. The Zappiti developers are aware and working on a fix. In the meantime, you will have to create new collections on the local server.

Recently I have been having a problem when adding torrents. Whenever I add new torrents, rtorrent will stop transferring data for about 20 seconds to a minute (ie. Download and Upload Speeds will drop to 0) and if I add several torrents in rapid succession, rtorrent will crash and then hash check all my torrents. When it does this, it will not start transfers again until all the torrents have been rehashed and ruTorrents shows them as Error and the trackers all show Timed Out. This has not been a problem in the past, only since I wiped and rebuilt my server a month ago. I am running Arch Linux and the only difference between how I had it configured before and now is that before I was using a BTRFS Raid-0 filesystem and now I am running rtorrent on a single drive with XFS filesystem. Have you seen this before?

I pulled the latest image and it is working now with the correct IP. Thank you!

I updated and the problem persists. I still have to change the IP in the external_vpn_ip.txt file and kill rtorrent to get it to take effect. I don't know if this is related to anything that was changed, but I can no longer run the /root/getvpnextip.sh script. It just sits and never seems to complete (tried multiple times and waited up to 5 minutes). Also, flood is not starting with the docker container. I have to execute the flood.sh script manually to start it. Are there any logs I can supply that can help identify where the problems are?

binhex, I am seeing a problem where my vpn external ip address is not being set. When I look at the command that starts rtorrent, -o ip=xxx.xxx.xxx.xxx is showing my public ip address instead of my vpn external ip. I did some further checking and the vpn_external_ip.txt file has my public ip in it. If I manually run /root/getvpnextip.sh it will change it to my external vpn ip address and then I have to kill rtorrent and allow the scrip to restart it so it will start with the correct ip address. I tried looking at your scripts but I'm not able to see what may cause this. I am using AirVPN as my provider. Any suggestions would be great. Thank you for maintaining such a great Docker container!

I am trying to setup both delugevpn and sabnzbdvpn but I am unable to access the webui of either when the vpn is enabled. As soon as I disable the vpn I can access the webui fine. I checked the logs and there aren't any errors to show why this is not working. Any ideas?