6.0.4 RAID won't mount
I have an idea to test on this driver loading issue. I will post it to a few posters until we see if this helps:
Boot into internet recovery mode. Run the terminal.app.
Paste this command in:
/usr/sbin/spctl kext-consent add Q9P8K45M5C
restart and see if the driver loads normally.
Hi. Neither a clean install + SoftRAID nor your suggestion work and I also found out that SR is the cause of sudden restarts of my 27" 2020 iMac. From what I can see the driver works (it recognizes disks than can be initialized and added to the RAID) but something prevents the disks from being mounted.
Appreciate your trying this. What it does is force macOS to "allow" OWC as a developer. This is a strange bug. A clean install of course would fix this, but I would prefer to figure out what the issue is in Big Sur. Once the driver is approved, Big Sur should allow it to load.
Thanks. Its very frustrating, as every time Apple changes its extension loading mechanism, bugs are introduced that a little more care from the engineering side would save users so much pain. In researching this more, I saw other driver/extensions companies have had issues, but since SoftRAID mounts disks, it is more mission critical than for instance, an anti virus application.
I hope to have this figured out soon, though.
When you create a new file system (new volume) we call macOS to initialize the volume. If the SoftRAID driver is not loaded, then this fails
You did a clean install with the same issue happening?
Sorry, I do not understand the question although I’m an IT on Macs.
Are maybe thinking I’m having Big Sur on raid? No, Big Sur are on internal ssd and the raid is on an external box.
Just a question: how can I be able to initialize an extra hd and add it to the raid1 I have if the driver is not loaded how it happens to me?
Sunday, May 23 2021, 17:41 GMT+2.
Nothing is impossible by my point of view. I took my external Inateck 2x2,5" box (with Thunderbolt 3 connection) with 2xSamsung EVO 960 SSD I use for Mac OS backups and replaced the HDs with 2x500Gbyte rotational. Erased them with SR 6.0.4 and built a RAID1 system. Works like a charm, also after a restart. In my case, surely, is not a driver load problem but something related to the USB 3.1 not-Thunderbolt (5 GBit/sec). Big Sur or SR? I don't know.
You mentioned that you tried a "clean install" of Big Sur and the driver problem existed on the new system? That was what I was commenting on.
Once you load the driver (with the terminal command line), and your volume is mounting, you can "Add disk", by initializing a disk with SoftRAID, and using the "Add disk" commend in the volumes menu.
I did what you recommended but I don't see any change. I still needed to run the command
sudo kextload -v /Library/Extensions/SoftRAID.kext
after the machine rebooted to get the drives to mount.
Nope. I’ve tested my raid (in usb3) in 2 different boxes on usb3. Rotational disks. Nothing changed. I can clear sector on a disk, initialize it and add it to the raid but the raid will never be mounted and the disk really added. Nothing happens. Could I do this with the driver unloaded?
I therefore made an experiment placing 2x rotational disks in my external 2bay box in raid1 and worked as it should. After posting the result you read I replaced the rotational disks with 2xssd (Sansung 860 evo) both in raid1 and raid0 and both worked well.
As the Inatech is the only TBolt connected enclosure I tested and worked flawlessly, as I tested my usual raid system in different enclosures and different usb3 cables and nothing changed I presume the problem, at least for me, is the usb3 connection as (also) all usb3 ports work fine (i put a disk in a single bay usb3 enclosure and initialized it with SR and worked well). And they do work well with other peripherals.
What can I think? What I already said: the problem of unmounting raids is not the driver’s loading but something conflicting 11.3.1 and SR 6.0.4 on the usb3 side.
Hope I was clear, I’m not mothertongue English.