Array Configuration & Shares

Overview
Lusankya's array uses UnRAID's single-parity protection model — this is not traditional RAID 6. One dedicated parity drive protects against a single data-disk failure; there is no second parity drive in this configuration. (
mdNumDisks=8 → 1 parity + 7 data disks.)
Correction worth flagging: earlier references to this as an "8-bay RAID 6" setup are inaccurate to how UnRAID actually protects data. Each data disk is independently formatted XFS — UnRAID computes parity across disks rather than striping like classic RAID. Functionally it tolerates one failed disk (or two, only if a second parity drive is added), but the mechanism and recovery process differ meaningfully from hardware RAID 6.
Array Layout
Role
Device
Filesystem
Parity
sdg
— (parity, no FS)
disk1–disk6
sdh–sdm
XFS
disk7
sdn
XFS
Cache pool
sde + sdf
BTRFS, RAID1 (2× 256GB SSD)
Cache Pool
Profile: BTRFS RAID1, 2 devices (mirrored) — 
Timetec 35PN2280SATA-256GB × 2
Hosts 
docker, 
appdata, and 
system shares exclusively (
shareUseCache="only")
Docker image: 
/mnt/cache/docker/docker.img, 20GB, native backing FS
Custom Docker networks defined: 
eth1 eth3 eth4
Shares
Share
Cache Use
Disks
appdata
Cache only
cache pool
docker
Cache only
cache pool
system
Cache only
cache pool
Data
No (array direct)
disk1, disk2, disk6, disk7
Photos
No (array direct)
disk1, disk2, disk5, disk6, disk7
Multimedia
No (array direct)
disk1–disk7 (all)
All three array shares export NFS as 
private security with an explicit host allow rule for 
192.168.1.85 (Centerpoint) only.
USB Backup Targets (Unassigned Devices)
These are not array members — they're Unassigned Devices plugin-managed USB drives, matching the rclone backup scripts already documented for this host:
Mount
Drive
Raw Capacity
Used
/mnt/disks/Expansion24
ST24000DM001
24TB
13TB / 22TB usable (58%)
/mnt/disks/Expansion26
ST26000DM000
26TB
19TB / 24TB usable (80%)
Notes / Gotchas
appdata/
docker/
system are cache-only — if the cache pool fills or both SSDs fail simultaneously, Docker and VM services go down hard since Mover has nothing to fall back to for those shares.
Array capacity is getting tight: disk1–disk5 are sitting at 87–94% utilized. disk7 (the newest member, WD Red 5TB) is the slack — only 30% used. Worth planning a rebalance or disk7 expansion before disk1–disk5 fill completely.
Last Updated
2026-06-23