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

help-circle
  • Ebby@lemmy.ssba.comtoSelfhosted@lemmy.worldHoliday Upgrade Disasters
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    25 days ago

    I had an Ubuntu system ate itself Christmas Eve at 1am. I think an update pooched some folder permissions and wiped the firewall settings.

    It started with “Huh, the network drives won’t mount”, progressed to containers failing to start with “hardware not found” GPU-related errors -oh yeah, I still have to check that and make sure it is working- and yadda yadda… 13 hours later I got services back up and running.

    Oof, today I slept in until 10. Ahhhhh…




  • 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.worldPlex Server Replacement
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    7 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.





  • I tried to update my lemmy instance and it all went so horribly wrong. DB never came up, errors everywhere, searching implied I updated to a dev branch sometime in the past (not a dev, don’t think I did) and it’ll be console and DB queries for a fix.

    Ran out of time and overwhelmed, I restored backups and buried my head in the sand. Nope, not now. Future, yes, but oh not now.


  • Same here. I don’t like some of the recent decisions, but I remember the time I looked at the value and thought “yeah, this is working, valuable, and I can get behind it”, and bought the lifetime pass.

    And I used the hell out of it! I don’t regret supporting the developers at all.

    But features like plugins disappear, rolled to in-house teams. They work better, but cost more to maintain.

    It’s ambitious, and gives developers plenty of work, but I feel the new redesign bit more than they can chew and overran budgets. They may be trying to balance budgets.