If you don’t need realtime parity, I’ve had no issues on my media server running mismatched drives pooled via MergerFS with SnapRAID doing scheduled parity.

I bought an $800 half stack guitar amplifier in 2009 and rarely play with the volume above 1, let alone play shows with it. But it looks neat.

Weird that I see this while listening to a podcast about wild pigs on the Auckland Islands. Googling made me realize NZ isn’t north of Australia like I’d remembered

When I stare and blink my eyes I see Joe Pesci, maybe from how I was raised.

The AI lied to me, as I booted a Fedora/Gnome VM and couldn’t find that option. My only other guess would be maybe an extension like this was installed and forgotten about because I tend to do that

deleted by creator

deleted by creator

Correct, it’s not obvious when first diving in but the main use for RAID is increasing performance and availability by allowing up to a specific number of drive failures. For that to work, ideally in an enterprise you’d have a primary and secondary controller to mitigate that point of failure which is not typical for most homelabs and makes backup even more important.

Anyone who has read a single NTSB accident report will understand what an insane idea this is.

When I moved into my otherwise shitty apartment, having Google Fiber was the selling point. Paying Comcast a monthly fee for unlimited bandwidth is something I vow never again to do.

After using some grandfathered T-Mobile family plan for over a decade I moved us to Tello. Still the same towers, but with our usage it’s half the price.

One note which may not apply to you, I installed my Proxmox to boot from 2 256G SSDs as a basic RAID 1 mirror and only have the bare minimum data in VM storage to reduce size of backups. Backup retention on the boot drives is limited because a cron job on the VM handles copying backups to the MergerFS pool for longer term storage.

Moving docker’s data directory to the ‘slow’ drives was a helpful decision, this post covers the old/wrong ways to do that and the way which worked (data-root). Docker data doesn’t take up a huge amount of space, but it saved me some work recently when I found my media server had been down for a while and couldn’t remember when it worked last to identify a working backup. I spun up a fresh Debian image and ran through the steps to reinstall the stack, and point to the same Docker data path. Running the same Docker compose command got most services working with the old metadata, though others i renamed/removed the service’s path and reconfigured.

My docker-compose and its revisions are the extent of a backup I need for a piracy box as my internet is quick enough to recreate my library within a couple days if needed.

Tried OpenMediaVault but found vanilla Debian on Proxmox is the easiest to troubleshoot. This guide helped me set it up. MergerFS works great with mismatched sizes of drives, and doing parity on media server content is a good use for SnapRAID.

deleted by creator

Stranded Deep scratched an itch for me, the limited options available made it easier to focus on a podcast versus other games which have an overwhelming number of crafting items and quests.

Put a sepia filter on it if you want to get creative.^…orhide^adickbutt

deleted by creator

And then convert that to hexadecimal, making it 1DA06

Bragging about how bad their gas mileage seems like the redneck’s version of inserting vacation and cruise stories into conversations

In OP’s case it sounds like the VPN service is the whole reason they’re using it. Not that I would recommend it, as their corporate IT likely has a policy against exactly this sort of thing