I tested that and I get full speeds. Upwards of 40-60mbps compared with the 1mbps I get when downloading to the NFS share
I tested that and I get full speeds. Upwards of 40-60mbps compared with the 1mbps I get when downloading to the NFS share
OK so I have done some additional testing:
So I believe I have ruled out memory issues, NIC issues, datapool issues, and switch issues.
The problem is I don’t know exactly when this started.
I did change out the motherboard on TrueNAS, and just installed the existing NVMe drives into the new motherboard and booted off of them. I did not install a new TrueNAS OS and restore a backup. Could this be an issue?
Shortly after the motherboard change, I upgraded to Electric Eel.
The pool is a mirrored pair of 14TB drives. Pool is 56% full. SMART tests all pass, but the last scrub took over a week which was odd.
Good points. I will finish the memtest thats running if only to have something ruled out. After it finishes I will try attaching the NFS share to the new qbt lxc and see if i get the same slow download speeds.
One other thing I changed recently is the motherboard on the NAS. The new one is DDR5 and I didnt have another machine that takes ddr5 to run the new ram through men test, and I didnt want any downtime so I didnt do it. I just powered down the NAS and started memtest. Do you think a bad stick of ram could be the culprit? At this point in just trying to rule things out
The qbittorrent docker container runs on an LXC. The LXC has 4 cores and 8 GB memory.
The Jellyfin LXC has 4 core, and the Arr stack w/ qbittorrent LXC also has 4 cores. The containers are running in bridge mode.
confirmed all speed limits are off
Hey pal super helpful follow up questions! Here is where I am:
- did you run speed tests over protonvpn and is this a paid plan?
Have not run speed tests, but yes it is a paid plan
- have you tested what your Ubuntu download speed is without VPN or gluetun in the way?
Yes I have tried bypassing gluetun with qbittorrent, and no change to the download speed.
- have you looked at the peer and tracker info to see what’s going on there?
No I have not. What info could I gather here? Same file being downloaded in both qbittorrent instances I’ve tried.
- have you tried another torrent client to rule out config issues with qbittorrent?
No but if you read my post, I did try a second instance of qbittorrent that does not use my NAS.
- do you have QoS rules on your router?
None.
- what is the NFS server, and how are you mounting it?
TrueNAS is serving the NFS, and the LXCs are mounting it via fstab entry.
From your title it’s also hard to understand if you’re trying to stream an unfinished torrent or not.
Sorry I was not clear. I am NOT trying to play media that is unfinished downloaded. I am trying to play files I already have, and they are impacted by other files being downloaded on qbittorrent.
edit: formatting
Have you looked at Readarr?
Thanks for the magic earth rec! Is it FOSS?
I think this is really great! I personally run a cluster at home and another offsite for backups. Would be really great to manage them under a single UI.
Its been awhile since I’ve run Nextcloud but when I did on a pi the interface was slow and the instance itself was unreliable.
Currently my NAS runs TrueNAS and pretty much just serves files. I guess I could run a Nextcloud container on TrueNAS, but I’m thinking I may get better performance with it running on a more robust machine.
Yea proxmox on one machine and a separate machine running truenas and serving NFS
I believe you can host your data if you prefer
Check out Helper Scripts. These make getting LXCs up and running super easy. This was built by a community member who recently passed away and he turned it over to the community before his passing. Its a great project!
I haven’t gotten the update yet. Is this a slow rollout?
Yes I’m pretty sure I’ve got it narrowed down to issues with NFS shares from TrueNAS. What I can’t figure out is how to fix it. I may do a backup, reinstall truenas, import backup, and see of that fixes it. I’m thinking potentially its an issue from reusing my old installation with the new motherboard, processor, and corresponding hardware.