• 0 Posts
  • 42 Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle


  • Ebby@lemmy.ssba.comtoSelfhosted@lemmy.worldEntry-Level NAS recommendations?
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    1 month ago

    Bingo. I’ve used Synology for ages and while they dont last forever, I get a lot of use out of them and re-buy them usually with an upgrade in mind.

    But the new hard drive policy broke that cycle. I don’t put up with that. I replaced one with a UGreen NAS last month. It’s too early to tell how I feel about it. Docker is there and containers spin up pretty easily. Rumor has it there is hardware support for video encoding too, though I haven’t gotten around to testing it.


  • Ebby@lemmy.ssba.comtoSelfhosted@lemmy.worldEntry-Level NAS recommendations?
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 month ago

    Bingo. I’ve used Synology for ages and while they dont last forever, I get a lot of use out of them and re-buy them usually with an upgrade in mind.

    But the new hard drive policy broke that cycle. I don’t put up with that. I replaced one with a UGreen NAS last month. It’s too early to tell how I feel about it. Docker is there and containers spin up pretty easily. Rumor has it there is hardware support for video encoding too, though I haven’t gotten around to testing it.


  • Ebby@lemmy.ssba.comtoSelfhosted@lemmy.worldEntry-Level NAS recommendations?
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    1 month ago

    Bingo. I’ve used Synology for ages and while they dont last forever, I get a lot of use out of them and re-buy them usually with an upgrade in mind.

    But the new hard drive policy broke that cycle. I don’t put up with that. I replaced one with a UGreen NAS last month. It’s too early to tell how I feel about it. Docker is there and containers spin up pretty easily. Rumor has it there is hardware support for video encoding too, though I haven’t gotten around to testing it.











  • Personally, I think IPv6 is not a good choice for any service you don’t want associated with a specific device. As I understand it, the prefix delegation comes from the ISP, but often the interface ID is derived from the machine’s MAC address which is a link to specific machine hardware, can reveal information about the host, and possibly deanonymoized across networks.

    I’d stick with IPv4 because NAT gives a tad more anonymity. Just my $0.02 though.





  • Ebby@lemmy.ssba.comtoSelfhosted@lemmy.worldPlex Server Replacement
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    5 months ago

    I just did something sort of like what you are doing and after a few hiccups, it’s working great. My Synology just couldn’t handle transcoding with docker containers running in the background.

    Couple differences from your plan: I chose a N100 over the N150 because it used less power and I wasn’t loading up CPU dependent tasks on the thing. The N150 is about 30% faster if memory serves, but draws more power. Second, do you really need a second m.2 SSD BTRFS volume? Your Synology is perfectly capable of being the file storage. I’d personally spend the money you’d save buying a smaller N150 device on a tasty drive to expand the existing capacity then start a second pool from scratch.

    Finally, I wouldn’t worry about converting media unless you are seriously pinched for space. Every time you do, you lose quality.


  • Ditto to your comment except power usage. I moved my Plex/Jellyfin (and hopefully Immich soon) docker containers to an N100 for the hardware acceleration. TDP is 6 watts on some of these devices and CPU use sits around 2% unless Plex is doing DB optimizations (about 60% for a bit). I haven’t measured consumption or my older server, but I feel moving some CPU intensive services to hardware GPU is saving a few watts.