During certify Softraid stops, needs to be quit and restart Softraid then resume.  

Has this bug been fixed for Mojave in Softraid 6, or 7 and will it work OK with Mojave?  

Thanks in advance...

I was able to to create the volume.

The terminal command does not show driver version.

Last login: Wed Apr 12 14:27:18 on console

2017-215-iMac:~ 21.5imac$ kextstat -b com.softraid.driver.SoftRAID

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>

2017-215-iMac:~ 21.5imac$

I tried in 6.3 and 7.5 each with their updated driver version.

I never had the option of adding OWC or anyone to the security pane.

Thx

I tried plugging the RAID thunderbolt cable in WHILE the mac was running and it immediately rebooted itself and did the same hang up at the same place in the progress bar. Power button shut down and unplugging the thunderbolt cable allowed a normal reboot. 

I have no idea what to do. I can't get the mac to recognize the RAID by rebooting or plugging in while the mac is on. I am having a really hard time believing there is a bad drive since everything was running so flawlessly and the exact moment I bumped the cable and the drive disappeared was the moment this issue started. 

Any help would be greatly appreciated!!! Thank you.

When I tried adding the new drive back into the JBOD set, I noticed that the volume wouldn't mount. Looking at the AppleRAID details, it appears it added the new drive as a slice but never fully removed the previous entry. So, even though I only have three physical drives, the volume thinks I should have four and that one of them is missing or damaged:

• slice 0: 2TB full
• slice 1: 2TB almost full
• slice 2: zombie slice reported as missing/damaged but doesn't really exist
• slice 3: 2TB completely empty new drive

I have tried physically removing various combinations nVME blades, changing the order they are installed on the Sonnet card, etc. but nothing has allowed the volume to mount so far. Trying to remove any slice via diskutil fails with an error stating that the File System is not Re-sizable.

The most frustrating thing is that all my drives are healthy and I know all my data is there. I haven't added or removed any files from the volume. The ONLY problem is that the JBOD is somehow convinced that there is an extra slice that it can't see. If I knew of a way to make it forget that the extra slice ever existed, I'm sure the drive would be able to mount exactly as before. 

Does anyone have any knowledge on how to fix this?

Here is what diskutil reports:

AppleRAID sets (1 found)

===============================================================================

Name:                 PCIe Storage
Unique ID:            78D78E3E-73E0-4F4E-8224-C573B133DA2E
Type:                 Concat
Status:               Offline
Size:                 6.0 TB (6000164831232 Bytes)
Rebuild:              manual
Device Node:          -
-------------------------------------------------------------------------------
#  DevNode   UUID                                  Status     Size
-------------------------------------------------------------------------------
0  disk0s2   AF7AD992-97C8-4A5E-B2C2-0E4AF006D779  Online     2000054943744
1  disk2s2   E39B5659-DDAE-4F76-8D51-0A0C9267CE4E  Online     2000054943744
-  -none-    8A90617A-2EFE-4E8E-8F88-F7E772228FDC  Missing/Damaged
3  disk1s2   26C52D06-A1A3-4462-9DD5-FBD06D74529E  Online     2000054943744
===============================================================================

  I'm new to this RAID thing and I just bought OWC express 4m2. Recently, when I was transferring files from another HDD/ downloading files from the Internet to my SSD, at some point it just froze. The transferring or downloading progress just stopped so I had to force quit the app, but, reopening the app didn't work so I had to restart my mac, however, unfortunately, restart didn't work either, I had to force shut down my computer. Or, I just couldn't stop the progress and the progress window didn't disappear, same problem when emptying the trash bin, so I had to, the same, force shut down. It's so weird because the monitor log hasn't shown any errors yet. I can still open SSD during all this nuisance or even run blackmagic disk and both read/ write speeds are all normal. Hence, to my understanding, I think the culprit was the RAID software itself? It doesn't happen all the time, but if it happens, it's a real pain in the ass 😫 . It feels like after forcing quit apps, something abt SoftRAID is still lurking in the background. Had never encounter this problem before using SoftRAID. And I do think this constant-force-reopen/ shut down behavior would somehow cause some damage to my iMac and SSDs. Any solutions or suggestions would be appreciated. Thanks in advance.

HDD: Buffalo DriveStation DDR 2TB

suspicious files: .ewi(every time if I open this kinda file, the whole computer crashes, incompatible with SoftRAID maybe?)

note. ewi. file is a VST from http://www.soundsonline.com

Downloading Site: BaiduNetdisk/ EW Installation Center

I use OWC express 4m2 with ADATA XPG SX8200Pro M.2 2280 PCIe 3x4 SSD 2TBx4 with RAID 0, certified

iMac Retina 5K, 27-inch, 2019, Mojave 10.14.6, 3,6 GHz Intel Core i9, 72GB 2267 MHz DDR4

SoftRAID Lite XT 5.8.4(I believe this one is the latest version)

I've finally gotten to the point where I've torn down the system configuration to base install and removed any other PCI cards besides the GPU.  My hardware is fine, I had been using an earlier Accelsior E2 card in the exact same slot with no problems.  What I seem to have found through step-by-step modifications is some form of kernel extension conflict between SoftRAID and Paragon Software's NTFS for Mac and extFS for Mac file system packages.  I wouldn't think these would be particularly uncommon to run into (at least the NTFS package, it continues to be fairly popular), so it surprises me that I haven't run across any reported issues.

Has anyone run into this problem with their installation?  I can live without the extFS capability (mostly there as a backup in case on of my Linux servers has an issue and I need to access a physical file systems), but I regularly use the NTFS capabilities provided by their read/write driver so this is kind of a show-stopper for me at the moment.  Hoping someone else has seen this and has some thoughts, I'm not real confident in this solution at this point and it seems like this would be an issue even when I move to newer MacPro hardware in the near future since it's not a hardware problem but a kernel extension issue.

I have shared SoftRAID logs with OWC Tech Support, not sure if those have been reviewed by anybody from the SoftRAID side of the house or not but can try and share again here if I can get it up and stable long enough to grab something.  It's crashing fairly early in the boot cycle so I haven't been able to grab any console logs that have been helpful so far, hence having to resort to walking back the configuration and adding back in piece-by-piece to get this far.

Thanks in advance for any advice!  Really would like this to work but not feeling optimistic at this point.

Thanks for your help.

Dan Kabat