Large 20TB+ NTFS volume allocation unit & compression

Use the fsutil command:

fsutil fsinfo ntfsinfo [drive letter]

You'll have to run this command with administrator privileges.

First of all, LVM configuration and RAID settings should be two independent decisions. Use RAID to set up redundancy and tweak performance, use LVM to build the volumes you need from the logical disks that RAID controller provides.

RAID0 should not appear in your vocabulary. It is only acceptable as a way to build fast storage for data that nobody cares about if it blows up. The need for it is largely alleviated by the speed of SSDs (enterprise-class SSD can do 10+ times more IOPS than the fastest SAS hard disk, so there's no longer need to spread the load over multiple spindles), and, should you ever need it, you can also achieve the same result with LVM striping, where you have much more flexibility.

RAID1 or RAID10 doesn't make much sense with SSDs, again, because they are much faster than regular disks, you don't need to waste 50% of your space in exchange for performance.

RAID5, therefore, is the most appropriate solution. You lose a bit of space (1/6th or 1/4th), but gain redundancy and peace of mind.

As for LVM, it's up to you do decide how to use the space you get after creating your RAID groups. You should use LVM as a rule, even in its simplest configuration of mapping one PV to one VG to one LV, just in case you need to make changes in the future. Besides, fdisk is so 20th century! In your specific case, since most likely it'll be single RAID group spanning all disks in the server, you won't be joining multiple PVs in a VG, so striping or concatenating don't figure in your setup, but in the future, if you move to larger external arrays (and I have the feeling that eventually you will), you'll have those capabilities at your disposal, with minimal changes to your existing configuration.