• 2 Posts
  • 304 Comments
Joined 8 months ago
cake
Cake day: June 9th, 2024

help-circle

  • Buy multiple drives, setup some sort of raid, setup some sort of backup. Then set up a 2nd backup.

    Done.

    All drives from all manufacturers are going to fail at more or less the same rate (see: backblaze’s stats) and trying to buy a specific thing to avoid the death which is coming for all drives is, mostly, futile: at the absolute best you might see a single specific model to avoid, but that doesn’t mean entire product lines are bad.

    I’m using some WD red drives which are pushing 8 years old, and some Seagate exos drives which are pushing 4, and so far no issues on any of the 7 drives.


  • Make sure, if you use hardware RAID, you know what happens if your controller dies.

    Is the data in a format you can access it easily? Do you need a specific raid controller to be able to read it in the future? How are you going to get a new controller if you need it?

    That’s a big reason why people nudge you to software raid: if you’re using md and doing a mirror, then that’ll work on any damn drive controller on earth that linux can talk to, and you don’t need to worry about how you’re getting your data back if a controller dies on you.




  • As with all things email, they probably really wanted to make sure that the mails were delivered and thus were using a commercial MTA to ensure that.

    I’d wager, even at 20 or 30 or 40k a year, that’s way less than it’d cost to host infra and have at least two if not three engineers available 24/7 to maintain critical infra.

    Looking at my mail, over the years I’ve gotten a couple hundred email from them around certificates and expirations (and other things), and if you assume there’s a couple million sites using these certs, I could easily see how you’d end up in a situation where this could scale in cost very very slowly, until it’s suddenly a major drain.


  • Very very little. It’s a billion tiny little bits of text, and if you have image caching enabled, then all those thumbnails.

    My personal instance doesn’t cache images since I’m the only one using it (which means a cached image does nobody any good), and i use somewhere less than 20gb a month, though I don’t have entirely specific numbers, just before-lemmy and after-lemmy aggregates.




  • So while not entirely related, I have a question.

    I’ve got a Windows 10 box hooked to my TV and you’re right, it’s great.

    Until you end up with fonts so small they’re unreadable, even with a 300% scaling on the 4k TV because it seems like every third random gaming piece of software just fucking ignore scaling.

    You ever find a working solution to that?

    My ass is old, and trying to do couch gaming from a PC means it’s a 50/50 chance I’m either squinting and giving myself a headache or having to walk over to the tv to read whatever stupid shit some game has decided to use 8pt font for.





  • I don’t disagree, but if it’s a case where the janky file problem ONLY appears in Jellyfin but not Plex, then, well, jank or not, that’s still Jellyfin doing something weird.

    No reason why Jellyfin would decide the French audio track should be played every 3rd episode, or that it should just pick a random subtitle track when Plex isn’t doing it on exactly the same files.


  • If you share access with your media to anyone you’d consider even remotely non-technical, do not drop Jellyfin in their laps.

    The clients aren’t nearly as good as plex, they’re not as universally supported as plex, and the whole thing just has the needs-another-year-or-two-of-polish vibes.

    And before the pitchfork crowd shows up, I’m using Jellyfin exclusively, but I also don’t have people using it who can’t figure out why half the episodes in a tv season pick a different language, or why the subtitles are somtimes english, and sometimes german, or why some videos occasionally don’t have proper audio (l and r are swapped) and how to take care of all of those things.

    I’d also agree your thought that docker is the right approach to go: you don’t need docker swarm, or kubernetes, or whatever other nonsense for your personal plex install, unless you want to learn those technologies.

    Install a base debian via netinstall, install docker, install plex, done.


  • Timely post.

    I was about to make one because iDrive has decided to double their prices, probably because they could.

    $30/tb/year to $50/tb/year is a pretty big jump, but they were also way under the market price so capitalism gonna capital and they’re “optimizing” or someshit.

    I’ve love to be able to push my stuff to some other provider for closer to that $30, but uh, yeah, no freaking clue who since $60/tb/year seems to be the more average price.

    Alternately, a storage option that’s not S3-based would also probably be acceptable. Backups are ~300gb, give or take, and the stuff that does need S3-style storage I can stuff in Cloudflare’s free tier.





  • The chances of both failing is very rare.

    If they’re sequential off the manufacturing line and there’s a fault, they’re more likely to fail around the same time and in the same manner, since you put the surviving drive under a LOT of stress when you start a rebuild after replacing the dead drive.

    Like, that’s the most likely scenario to lose multiple drives and thus the whole array.

    I’ve seen far too many arrays that were built out of a box of drives lose one or two, and during rebuild lose another few and nuke the whole array, so uh, the thought they probably won’t both fail is maybe true, but I wouldn’t wager my data on that assumption.

    (If you care about your data, backups, test the backups, and then even more backups.)