I’ve opened it in libre office and can rebuild your error. It’s the toggle field Raid5/Raid6 that is imported incorrect. That controls cell “C13”. In MS Excel it toggles between 1 (=Raid5) and 2 (=Raid6). Libre Office makes a true/false story out of it. Just use “1” for Raid 5 and “2” for Raid 6 in cell C13. Then it should work fine.
The sheet originally was designed to clear the discussion wheather a Raid or a non-raid is best. The answer is given: It depends on the daily ingress.
This is inaccurate, and likely based on a bad articles that miscalculate probability of raid failure during rebuild. This topic pops us every so often on every single storage forum, including here. linking to avoid retyping
I don’t think the math there is flawed - but what it really does is show that how most systems treat RAID5 style redundancy is flawed. RAID5 nukes the entire array because of one URE on a second device during a rebuild; raidz not only will still continue, it will flag the specific files that it couldn’t recover.
I run an array striped across multiple raidz vdevs (for purposes other than Storj) and I’ve encountered “URE during a rebuild” at least twice already, losing just a small amount of data each time instead of having to restore the array from scratch.