Sorry for confusion, I was describing why we put the warning up not to run both, because SoftRAID can do something bad, as it does not see the changes made by Disk Utility.

Thanks again! I was a bit confused by the sentence in your first reply,

Posted by: @softraid-support

you can create volumes / delete / alter volumes in Disk Utility and the changes are not reflected in SoftRAID. So the advice is not to run both at the same time.

 

But I will first create a DMG and see how that works.

No, the Monitor is 100% independent to Disk Utility. It does not "manage" any volumes, so there is nothing to conflict.

Do NOT try to create a volume on a SoftRAID volume. Just DMG files.

In the next year, we hope to add better APFS volume management (creating volumes inside APFS containers - its complex) and hopefully be transparent to Disk utility. that depends on a few macOS factors, whether Disk utility will be able to also manage SoftRAID APFS containers.

SoftRAID Monitor is active (with default prefs), but not the SoftRAID app. Will that be a problem?

How about creating a volume in Disk Utility instead of a disk image? I would create the volume on the ThunderBlade.

What happens is you can create volumes / delete / alter volumes in Disk Utility and the changes are not reflected in SoftRAID. So the advice is not to run both at the same time.

As long as SoftRAID app is not running, using Disk utility to create DMG files is no problem at all. and they can be saved onto any volume.

Have been advised not to use Disk Utility on the ThunderBlade due to potential conflicts with SoftRAID.

Suggestions? Guidance? ThunderBlade has "Ignore permissions" enabled (which I presume was done by SoftRAID at formatting).