Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
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
Bad RAM wouldn't present like this. You'd more than likely never get past boot with a DDR5 board having caught it with POST tests, or you'd have thrown a kernel exception by now.
I saw you mentioned that a new LXC container didn't have the traffic problem, so this is definitely something with config somehow.
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.
Try a test download without NFS and see what happens.
I tested that and I get full speeds. Upwards of 40-60mbps compared with the 1mbps I get when downloading to the NFS share
Problem solved then. You know where the bottleneck is.
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.
Just don't use NFS for large files. It's not good for that.
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.