I recently had a local issue where I could barely reach B2 as well. It turned out that one of their endpoints was on a DNS blocklist I use. Once I manually unblocked that everything started to work again. Not saying you’re having the same issue but it could be a lot of things between you and B2, careful triage is needed to find the root cause.
Power going out depends a lot on where you live. I can’t remember the last time I lost power at home (in NL), probably a decade ago? And it only lasted 30 minutes I think. Depending on how common it is and how long it tends to last it could be worth it to invest in a UPS or even a generator.
Internet going out is more common over here, which is easily mitigated with multiple uplinks and some kind of dynamic DNS if you feel that’s worth it.
Some people really enjoy living in walled gardens I guess. But when I see people like GamersNexus who were considering a large order of Bambu printers are now ticked off by this they really should’ve known better.
I’m surprised that people are surprised by this. Bambu has clearly telegraphed what kind of assholes they are in the past when they locked down their firmware and local APIs, so this was just expected behaviour IMHO.
Built my own server to be completely silent since it lives in my living room. Based on an Intel i3-12100 with some NVMe and 5x SATA SSD’s, and running tons of containers. Does about 18W most of the time and it could have been lower with a different motherboard.
All the UniFi stuff (gateway, switches, APs) uses just under 50W though, so there’s little sense in spending more money on the server to shave off a few watts.
Servers are terrible for homelab use. They’re unwieldy, consume way too much power and as you’ve found they’re very noisy. My vote goes to selling the thing and getting a mini PC, an (old) laptop or building something quiet and frugal yourself. In the last case you might be able to reuse some parts you already have. But if cost is important almost nothing beats second hand mini PC’s in value for money.
Hmmm, Fresh looks interesting, didn’t know about that one!
SnapRAID offers an additional benefit over real RAID-like systems: it functions as a short-term backup. If you sync it daily like I do, that means that if you accidentally delete a bunch of files (old enough to have been synced, I.e. older than one day in my case) you can restore them from the SnapRAID parity.
The reverse is also true of course: if you lose a disk you also lose today’s changes to that data. So it’s most suited to large collections of rarely changing stuff like photos and videos and music IMHO.
Official Podman Quadlet files? Me likey!
I’ve been using IPv6 for more than 20 years, and I can’t say that about nuclear fusion.
Depends. There are a few things I update by hand, but as long as you have proper backups it’s generally safer to run the latest versions of things automatically if you don’t mind the possibility of breakage (which is very rare in my experience). This is in the context of self-hosting of course, not a business environment.
Yeah only for :latest containers, that’s true. It automatically runs a daily service to check whether there are newer images available. You can turn it off per container if you don’t want it.
One of the nice things about it is that I have containers running under several different users (for security reasons) so that saves me a lot of effort switching to all these users all the time.
Podman automatically updates my containers for me.
A recommendation for Moonrise Kingdom based on Mickey 17? The genres might match, but those are totally different movies.
I use mergerfs (and snapraid because I do care about my data and want parity) on ext4 formatted disks. This is a much better way to use your disks if you’re mostly just storing media. RAID is for mitigation of downtime after drive failure, not for joining a bunch of (differently sized?) disks into one pool if downtime isn’t really a problem.
The point is signaling to other people that it’s not worth their time. I sort by new so I often see these slop posts as well, but other readers very quickly downvote it into oblivion so if a post is older than say 15 minutes I generally will know not to read it even if it sounds interesting at first glance. A mod will come by later to actually delete it if that’s warranted, but until then downvotes suffice.
Relevant video: https://youtu.be/4X9ww6FtUhE?si=R5TCNF0lTho9kHWp
Tl;dw is that sure, the US could withhold software updates and sure, NL could do their own software thing, but there is a whole intelligence software thing too that makes it harder. And ultimately if the US stops supplying new parts the existing planes are quickly dead in the water anyway. So it’s a short-term solution at best.
I think unattended-upgrades only runs once a day by default, and the repository index could have changed since then. Different results on different machines can be because unattended-upgrades didn’t run at the same time, or from the same mirror (and mirrors take a while to propagate changes). Generally speaking you should always run an apt update directly before installing new packages.
Arch in the front, Debian in the back(end). I run Arch on my laptop and Debian on my homeserver. I’ve ran Debian on laptops before and if stable is getting older hardware support can be a struggle, much better on a rolling distro like Arch. And having all the newest toys on your desktop is very very nice. While on my homeserver I mostly want stability, everything else runs in (podman) containers anyway.
Cachy is a distro I would consider, because it’ll theoretically give you slightly better battery life due to the optimised compiles, although I’m not sure you’ll ever really notice. Manjaro has a reputation of breaking far more often than Arch does, so that one’s a no for me.
One of the main advantages of Optane doesn’t easily show in a benchmark: it doesn’t have to do any cleanup. Normal SSD’s cheat all the time by caching writes in DRAM and an SLC portion of the NAND. Usually that works fine and you won’t notice, but if you keep writing then at some point performance will plummet dramatically. Also, the SSD’s need a breather every now and then to rewrite that cached data to it’s final place, during which time performance is also worse.
Optane doesn’t need any of that. You can write to it at max speed 24/7 and it’ll just take it and keep going, at ridiculously low latency. Perfect for handling large non-stop data streams, or workloads that need a guaranteed low latency (both for reading and writing). It’s a real shame the concept failed, the tech was fantastic.