CouncilOfFriends

joined 1 year ago
[–] CouncilOfFriends@slrpnk.net 32 points 7 months ago (1 children)

With a PA message that there is a free meal in the aisle for whoever wants it

[–] CouncilOfFriends@slrpnk.net 2 points 7 months ago

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.

[–] CouncilOfFriends@slrpnk.net 12 points 7 months ago

The only reason I liked using their remote app was being able to do Bluetooth listening. Now the app no longer runs on my phone, and after reinstalling and rebooting I deleted that and am back to using the Chromecast. Time to cut the internet to the TV so I don't get an update with this ad feature

[–] CouncilOfFriends@slrpnk.net 2 points 8 months ago

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.

[–] CouncilOfFriends@slrpnk.net 7 points 8 months ago (3 children)

This is correct. As the article says employees are using their phones as hotspots so it's not as if it's a Faraday cage. Their IT guy should do a Wi-Fi site survey and install a few AC Pros.

[–] CouncilOfFriends@slrpnk.net 1 points 9 months ago* (last edited 9 months ago)

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.

[–] CouncilOfFriends@slrpnk.net 7 points 9 months ago* (last edited 9 months ago) (2 children)

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.

view more: ‹ prev next ›