It’s not at all gamified or fancy, but I find the official documentation to be excellent - a step well above the norm these days.

Bonus: Downloadable as an epub or pdf, creative commons license, and regularly updated.

Well, I’ve found some of the answer.

/volume1 is a single LV on a single VG - no surprise there. There are two PVs comprising it, each of which is a RAID5 group across an extended partition on the disks.

pv0 is /dev/sd[abcd]5 and pv1 is /dev/sd[abcd]6

Now what I find most interesting right now is that SHR supposedly required btrfs to operate - and yet, /volume01 is an ext4 filesystem.

Part of me would like to convert to btrfs, but I’d need a spare 10TB of storage just to back up to, before starting down that odyssey.

More digging, more questions.

I love KeepassXC, but I use Keepass2android on my phone. Do you know how it compares to KeepassDX?

Again?

Not very clever or rare, but extremely useful. On my persistent Unix/Linux boxes, I “git branch /etc” as soon as it comes up. Then all of my admin config gets committed whenever it’s changed.