A Reddit Refugee. Zero ragrets.

Engineer, permanent pirate, lover of all things mechanical and on wheels

moved here from lemmy.one because there are no active admins on that instance.

  • 0 Posts
  • 12 Comments
Joined 2 years ago
cake
Cake day: December 22nd, 2023

help-circle
  • Whatever is cheapest. When youre first starting out basically any hardware will do, it just needs to boot Linux. As you progress and find more stuff to put on the servers, you’ll discover what you’re real hardware needs are.

    When I first started, it was a hand me down single core AMD Sempron machine (socket 754!) that I later upgraded to an Athlon64 and 4gb of DDR. I managed to bodge that poor thing into running a Minecraft 1.5.2 server.

    Personally I would stick with the i3 machine since I am assuming it’s an office PC that can be had for cheaper than a Pi 5 (which is quite inflated in price IMO). x86 still retains better software support vs ARM and they are significantly easier to attach large cheap storage to via SATA. Power cost will be greater but I doubt an office i3 pulls more than 70w wall power at full load.





  • lemmy.dbzer0.com - Anarchists who hate tankies and any rules except their own, which are different and therefore better

    I mean. The only real rules we have mostly surround don’t be a dick and the bare minimum to manage a public forum. If you can’t really pass that test then you weren’t welcome in the first place.

    Lemmy is what you make of it. You have to put effort into tuning your subscribed communities, blocklists, etc. There is no algorithm to filter the chaff for you. I see very little inter-instance drama these days because I’ve filtered it out.






  • A. Run a batch transcode with Handbrake and make all your stored files compatible with your end players.
    It sounds like the more recent things you are downloading are in a codec that is not compatible with your playback devices. E.g, older torrents are frequently an H.264 stream in an MP4 container, which practically every device can play now. Many modern releases are being distributed in H.265 or AV1, as they have significant size and quality benefits, but many older devices don’t support them natively. so it is forcing Jellyfin to live transcode to h.264. Find out what older titles play without any buffer or playback lag/high CPU usage and check what codec those files are in. That is what you’ll need to batch encode everything over to.

    B. Sounds like you are still relying on CPU transcoding which is absolute dog. What mini pc specs do you have? If it’s an AMD or Intel CPU/APU then it should have hardware encode/decode included in it’s integrated GPU. When using hardware transcoding the CPU load is generally minimal for 1 to 2 streams. See the Jellyfin docs on hardware acceleration here.


  • My default goto with any stability issue is to first force a new drive self test

    smartctl -l selftest /dev/nvme0  
    
    

    And then I would also run a complete extended memory test (memtest86) to ensure bad ram isn’t doing something dumb like corrupting the part of the kernel that handles disk IO. The number of times I’ve had unsolvable issues that traced to an unstable stick of memory is… Surprisingly high.

    If the memtest passes try fsck’ing nvme0, if there are corrupted blocks yeah it’s possible the SSD is dying but the controller isn’t reporting it.