this post was submitted on 11 Nov 2025
12 points (100.0% liked)

Linux

59502 readers
422 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
 

This is my first real dive into hosting a server beyond a few Docker containers in my NAS. I've been learning a lot over the past 5 days, first thing I learned is that Proxmox isn't for me:

https://sh.itjust.works/post/49441546 https://sh.itjust.works/post/49272492 https://sh.itjust.works/post/49264890

So now I'm running headless Ubuntu and having a much better time! I migrated all of my Docker stuff to my new server, keeping my media on the NAS. I originally set up an NFS share (NAS->Server) so my Jellyfin container could snag the data. This worked at first, quickly crumbled without warning, and HWA may or may not be working.

Enter the Jellyfin issue: transcoded playback (and direct, doesn't matter) either give "fatal player error" or **extremely **slow, stuttery playback (basically unusable). Many Discord exchanges later, I added an SMB share (same source folder, same destination folder) to troubleshoot to no avail, and Jellyfin-specific problems have been ruled out.

After about 12hrs of 'sudo nano /etc/fstab' and 'dd if=/path/to/nfs_mount/testfile of=/dev/null bs=1M count=4096 status=progress', I've found some weird results from transferring the same 65GB file between different drives:

NAS's HDD (designated media drive) to NAS's SSD = 160MB/s NAS's SSD to Ubuntu's SSD = 160MB/s NAS's HDD to Ubuntu's SSD = .5MB/s

Both machines are cat7a ethernet straight to the router. I built the cables myself, tested them many times (including yesterday), and my reader says all cables involved are perfectly fine. I've rebooted them probably a fifty times by now.

NAS (Synology DS923+): -32GB RAM -Seagate EXOS X24 -Samsung SSD 990 EVO

Ubuntu: -Intel i5-13500 -Crucial DDR5-4800 2x32GB -WD SN850X NVMe

If you were tasked with troubleshooting a slow mount bind between these two machines, what would you do to improve the transfer speeds? Please note that I cannot SSH into the NAS, I just opened a ticket with Synology about it.

Here's the current /etc/fstab after extensive Q&A from different online communities

NFS mount: 192.168.0.4:/volume1/data /mnt/hermes nfs4 rw,nosuid,relatime,vers=4.1,rsize=13>

SMB mount: //192.168.0.4/data /mnt/hermes cifs username=_____,password=_______,vers=3.>

you are viewing a single comment's thread
view the rest of the comments
[–] just_another_person@lemmy.world 2 points 1 day ago (1 children)

This is incredibly confusing and formatted oddly, so let me get some clarification:

  1. What protocol are you using to mount the NAS to the Ubuntu machine?
  2. What did you use to transfer this slow file over the network? The disk transfer rate would be much faster than the network in any case, so 160MB/s may just be the network max.
  3. Have you tried other files and methods to transfer, like SSH, Rsync...etc? Try those and post the speeds.
  1. NFS4 at first, I've also tried SMB. I don't care which one I end up with, as long as it works efficiently and consistently
  2. A few things, but my memory is blurry. I definitely used the cli in the post, but I started by trying 'cp' then 'rsync'
  3. I have to test speeds, but the real issue here is how this performance is impacting my containers' performance