

You can cycle the smaller drives to cold backup, that’s not a waste. You do have backups, which RAID is not, right?
You can cycle the smaller drives to cold backup, that’s not a waste. You do have backups, which RAID is not, right?
Sure, works fine for inference with tensor parallelism, USB4 / thunderbolt 4/5 is a better (40Gbit+ and already there) bet than ethernet (see distributed-llama). Trash for training / fine tuning, that needs higher inter GPU speed, or better a bigger GPU VRAM.
Seems like data integrity is your highest priority, and you’re doing pretty well, the next step is keeping a copy offsite. It’s the 3-2-1 backup strategy, 3 copies, 2 media (used to mean CDs etc but now think offline drives) 1 offsite (in case of fire, meteor strike etc), so look to that, stash a copy at a friends or something.
In your case I’d look at getting some online storage to fill the offsite role while you’re overseas (paid probably, but a year of 1 or 2 Tb is quite reasonable) leaving you with no pressure on the selfhosting side, just tailscale in, muck around and have fun, and if something breaks, no harm done, data safe.
I’ve done it for what seems like forever and I’d still be worried about leaving a system out of physical control for any extended period of time, at the very least having someone to reboot it if connectivity or power fails will be invaluable, but talking them through a broken update is another thing entirely, and you shouldn’t make that a critical necessity, too much stress.
The old adage is never use v x.0 of anything, which I’d expect to go double for data integrity. Is there any particular reason ZFS gets a pass here (speaking as someone who really wants this feature). TrueNAS isn’t merging it for a couple of months yet, I believe.
Yup (although minutes seems long and depending on usage weekly might be fine). You can also combine it with updates which require going down anyway.
Basically, you want to shut down the database before backing up. Otherwise, your backup might be mid-transaction, i.e. broken. If it’s docker you can just docker-compose down it, backup, and then docker-compose up, or equivalent.
Solid. My backup is a T440p, and behind that a X230, fucking bulletproof.
Been happy with FreshRSS for years now (TTRSS before that). One thing that really improves it is RSS-Bridge which turns a lot of non RSS sites into feeds (and a lot of truncated feeds into full ones). It’s also a list of what hackerly types will put effort into getting a feed from, so self-curating in its way. Enjoy…
The more people, the better the platform. It’s that easy.
Hard disagree, quality matters as much or perhaps more than quantity. A billion Nazi network is still Nazi, see Xitter for instance.
Yeah, keyword list would be awesome.
I have a personal bunch of communities as is allowed and occasionally jump to main when I run out of content. Usually see something I regret, often Trumpian, amusing but depressing. Maccas window Trump etc. Will code for relief if it’s not too (ironically) political.
Great to hear!
Not sure, but it is still active with like 80 contributors. It’s much the same as the original with a couple of extra features and more languages, so transition should be minimally painful, maybe even export - import level. I’ve been using it for years as I saw the original wasn’t very active, but they’re pretty much (essential) feature complete and stable, which is good. Apparently, google thinks that’s bad.
Not sure, but it is still active with like 80 contributors. It’s much the same as the original with a couple of extra features and more languages, so transition should be minimally painful, maybe even export - import level. I’ve been using it for years as I saw the original wasn’t very active, but they’re pretty much (essential) feature complete and stable, which is good. Apparently, google thinks that’s bad.
Syncthing-Fork (F-Droid)
Syncthing-Fork (F-Droid)
As noted elsewhere Syncthing-Fork is still going strong, and a drop-in replacement, it’s on F-Droid.
Absitively, use case here IMO is set and forget autoupdate to stay current and SELinux (which actually reduces surface)
For a media server speed matters little (5400rpm is plenty), if you’ve only got one drive, warranty is king. Thing is you shouldn’t only have one drive, drives will fail, and warranty doesn’t get your data back, so you plan for it. At the very least, you should look at getting an offline backup as soon as possible, now you don’t care if your drive fails and can get the cheapest ones. Ideally, you also set up a RAID5 (or Unraid, or mergerfs+SnapRAID) on your server, now you just get a replacement drive and rebuild. Remember RAID is not a backup, it doesn’t protect against accidental deletions for example, so you still want the offline backup.
Also, don’t sleep on manufacturer recertified drives, as long as you have a backup they’re significantly more cost-effective.
TLDR: set yourself up so that a drive failing is not a problem.
I was here to say the same as pezhore, separating storage and compute is almost as important as separating church and state. Muck around, break things, have fun, all the while your data is safe (don’t forget offline backups though). The MS-01 is a fine looking box, but any old NUC / SFF will do for your purposes (modern AMD cpu or a graphics card if you need / want plex transcode).
Edit to add, old laptops are great compute nodes (maybe moreso from my ex corporate thinkpad laptop bias, but still)…
Not sure I’d use either, but may I suggest both, with a clear caveat that one or both may disappear or change ? Throw stuff at the wall, see what sticks…