Intel iMac: Drive not recognized (I think due to a bad .kext file)

Dont try manually removing drivers. that driver, I believe is part of macOS. (SoftRAID's driver is bundled with macOS)

Did you run SoftRAID and "uninstall SoftRAID - all components?"

restart and installed the driver?

Then made sure to go to System Preferences/Security to "Allow" OWC as an identified developer?

If you did all this and the driver doesnt appear to be loading, paste these two commands into the terminal.app and let me know what the output is for each one:

sudo kextstat -b com.softraid.driver.SoftRAID

sudo kmutil load -p /Library/Extensions/SoftRAID.kext

@softraid-support 

I did indeed run the SoftRAID uninstall all components. Restarted, and re-installed - and I'm not joking here - about 20 different times throughout the day. Clearly a little desperate (that's when I started researching how I can wipe the kernel extensions to try again).

I have also of course run through all the security permissions including the System Pref > Allow OWC (and Security > Full Disk Access). I've even restarted in recovery mode and disabled all security from unlicensed developers entirely.

It's not that the "driver" isn't loading, the very RAID array isn't even recognized when I plug it in (but it is recognized on a different M1 machine with the same software).

Here are the results of those terminal commands:

sudo kextstat -b com.softraid.driver.SoftRAID:

Executing: /usr/bin/kmutil showloaded --bundle-identifier com.softraid.driver.SoftRAID

No variant specified, falling back to release

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

  202    0 0xffffff7f9a3ac000 0x2f000    0x2f000    com.softraid.driver.SoftRAID (6.2.1) 59043142-3904-3FC4-A837-BC3F0C4AC9E4 <33 7 6 3>

sudo kmutil load -p /Library/Extensions/SoftRAID.kext:

> null (nothing happens when running this line)

Currently SoftRAID software is open and recognizes my startup disk and any other disk I plug into the computer, EXCEPT for my Thunderbay 4 (which, again, IS recognized on another machine with the same software). 

@neshmonster 

Attach a SoftRAID tech support file. Let me see.

@neshmonster 

Did you have the disks connected when you saved the support file?

If not, save another with the disks connected.

If they are, then this is a hardware issue, cable or something.

@softraid-support 

I'll try again. We can with total confidence exclude the possibility that this is cable or hardware issue because:

1. Other drives plugged in to the same ports with the same cable work on the iMac

2. The array in question that isn't read on the iMac IS read on another machine using the same cable.

3. I've tested this upwards of 30 times with 100% consistency

@neshmonster 

This is a hardware issue, it is a matter of figuring out the cause. Here is what System Profiler sees on your system.

Did you try the other port on the computer?
If the unit is currently connected, for some reason, the M1 does not think it is.
When you plug it in, do the drives spin up? Then at least you know the Thunderbolt signal is reaching the enclosure...

@softraid-support 

I made you a quick 1 minute video to clarify what's going on: https://www.youtube.com/watch?v=2fZPxpcv-w0

@neshmonster 

I did understand this is what you are dealing with, but its still a hardware issue of some kind.

(If the disks showed up, but SoftRAID could not mount them, then it is a software issue. the fact that they do not even power up, demonstrates this is something about the hardware)

Send me a SoftRAID support file with the SSD connected to the iMac and another with the array connected to the Laptop. that will tell me what I need about both.

Also let me know if the cable has a "3" on it, a "lightning bolt" icon, or nothing, stamped on the ends.

I saw the SSD is in a USB 2 enclosure, not sure if that meant anything yet.

@softraid-support

 - It is indeed a thunderbolt 3 cable

@neshmonster 

Do you have access to any other Thunderbolt devices?

Note if you connect a device, it should show up in System Profiler (about this mac), under the Thunderbolt tab on the left column.

You said you tried the other thunderbolt port, correct?

I cannot guess yet what is actually going on.

I have other USB C devices, which work fine, I don't think I have any other Thunderbolt (3? 4?)  devices. Everything I plug into these ports (audio units, external hard drives etc.) work except for the Thunderbay 4.

If you think it's a hardware issue, then there's only one possibility, and that's that the controller on the Logic board is fried. I really don't see any other option than to backup this machine, do a fresh reinstall, and and take it to the Apple store. I guess what I need to know from you guys is whether or not the Thunderbay can cause this kind of damage by leaving it on for extended periods of time, or keeping it plugged in while the computer is sleeping, or whatever. The thunderbay was working fine on this computer for about a month and then I woke up one morning to find it inoperable on this machine. 

@neshmonster 

I have never seen Thunderbolt damaged "from usage". We have had machines doing heavy IO for 3 years on 16 drives (in testing), no issues.

Here is what you can try next:

Do a clean install.

Run Disk Utility.

Click on your startup drive and click + on the upper menu, by volumes.

Create a new volume. This will be APFS, so it shares your volume space and does not affect your existing volume.

Startup with Command r on intel, or, the power button on M1 for options.

"reinstall mac OS" and install mac os onto it.

Use your same admin account name for simplicity

Now see if thunderbolt is working on that.

If it is not, then backup your main system and bring it into Apple.