Do you mean newer kernel/tools than this beta?
df is still working correctly for me:
Filesystem Size Used Avail Use% Mounted on
/dev/sdf1 1.4T 3.6M 930G 1% /mnt/cache
And now the newer btrfs tools in beta29 also support raid5/6:
btrfs fi usage -T /mnt/cache
Overall:
Device size: 1.36TiB
Device allocated: 17.06GiB
Device unallocated: 1.35TiB
Device missing: 0.00B
Used: 288.00KiB
Free (estimated): 930.15GiB (min: 700.11GiB)
Data ratio: 1.50
Metadata ratio: 2.00
Global reserve: 3.25MiB (used: 0.00B)
Multiple profiles: no
df reports the correct used and free space for every possible combination (AFAIK) except raid1 with an odd number of devices, but that's a btrfs bug and should be fixed in the near future.
There was no parity.
That's not the problem, problem is that Unraid rejects the disk after a reboot, and worse than that partition is invalid and disk can't be mounted again, it's easy to reproduce if you do the steps I outlined above.
You can use the invalid slot command if you have a spare disk of the same size or larger, I can post the instructions for that.
If you can't do it in the GUI disable array auto-start by editing disk.cfg on your flash drive (config/disk.cfg) and changing startArray="yes" to "no".
By using the new config with the "trust parity" option, this assuming nothing changed on the array since you added the new parity, still:
because of mounting the array without it, even if no data was changed.
You shouldn't have done that, it's not possible to successfully sync parity with a failing disk, and now old parity won't be 100% in sync, but it's still your best bet, do a new config with it, check parity is already valid, then do the parity swap.
How to reproduce:
-have a non-rotational device assigned to the array with the old partition scheme.
-wipe it manually or using the new erase function.
-start array and re-format with new alignment.
-reboot (or make any other array change) and will get a "wrong" device, since Unraid is still expecting the old size.
-you'll need to do a new config to re-accept the device but it will be unmountable, so any data copied since will be lost.