@pcgrubb127 Welcome the the Rockstor community forum.
Re:
Yes, single is not a good choice (except in very specific instances); however the parity raid levels of btrfs raid 5 and 6 are only a little better given their non production status in btrfs currently.
See our Redundancy Profiles doc section for a fairly current overview:
https://rockstor.com/docs/interface/storage/pools-btrfs.html#redundancyprofiles
What you may be seeing here is our upstream’s (openSUSE’s) decision to make the parity raids (5 & 6) read only by default. We do not second guess this decision given they are the experts in this matter. I’m then surmising that you have an in-flight conversion that ended up being unmountable in rw. It may be you can add a custom mount option of ro to retrieve your existing data. All depends on if you were populating at the time or your problem pool is the source of truth.
However the work-around that we suggest, when folks insist on parity raid use, is indicated in the above doc reference in the note below the profiles explanation: essentially installing a newer upstream kernel (also prepared by openSUSE). This way we have folks use a newer kernel - with the hope that this will increase the chance of a stable experience re the parity btrfs raid levels. And because parity raid is not disabled there by default. Not ideal but it is the situation we find ourselves in re btrfs and its parity raid levels. If you take this route, via the doc linked HowTo, linked here for context:
https://rockstor.com/docs/howtos/stable_kernel_backport.html#stable-kernel-backport
be sure you understand what that howto states - and to follow through on all the elements there - appropriate to your openSUSE version. And note that the howto also updates the user-land btrfs - again supplied as a back-port by the openSUSE folks.
Alternatively you could not use the parity raid levels of 5 & 6.
If you are using a more recent Rockstor version - likely if you have recently downloaded the installer. Then you could also entertain a mixed raid setup where data is stored in btrfs-raid 5 or 6, but metadata is in say btrfs-raid1c3/4. But again, this still requires the stable kernel backport.
We introduced mixed raid capability within the Web-UI at version 4.5.9-1 onwards:
So this is available now in both our stable channel (4.6.1-0 latest):
and our latest testing channel (5.0.3-0):
However the latest testing releases is still a little on the young side - with many parts still in flux (read being updated).
What version are you currently running incidentally? And what is the openSUSE base version. the latter should be Leap 15.4 as that is our current target until we make a few more developments in testing. Thereafter we will be moving to 15.5 as a preferred base.
Hope that helps.