Notifications
Clear all
Big Sur Issues
45
Posts
8
Users
2
Likes
1,410
Views
This becomes code that has to be managed/supported
Love this answer. Thank you softraid-support!! Appreciate the updates. Is it possible you could start a compatibility thread for every release? I usually check here before upgrading.
Posted : 01/08/2021 3:03 pm
We add a thread for major releases, but each sub release is a bit much. I think it would be somewhat confusing.
Posted : 02/08/2021 10:13 am
Topic starter
@softraid-support Hi yes the command worked however like what the others are saying is there an update that will fix this so we don't have to do this everytime? Thanks.
Posted : 09/08/2021 10:24 pm
Yes there will be a macOS update at some point that fixes this.
Did you try 11.5.1 to see if it helps you? It does not have the fix, but has helped a good percentage of users with this issue.
Posted : 10/08/2021 12:55 am
Topic starter
@softraid-support Yes I’m on 11.5.1 and it did fix the issue for a while but just yesterday it went back after my WD utility tool updated to its latest version. So Im not sure if it affected softraid in anyway but that was the only thing that I did yesterday.
Posted : 10/08/2021 2:04 am
these driver loading issues are Big Sur bugs. You can try a "reinstall SoftRAID driver" and "Allow" OWC again as an identified developer and see if that helps.
Otherwise you may need to manually load the driver with this:
sudo kextstat -b com.softraid.driver.SoftRAID
Posted : 10/08/2021 9:01 am
Topic starter
@softraid-support I have tried uninstall and install via utilities but every time I install, it does not ask for it to be allowed and I don't even have to give full disk access as it has already been given full access.
Posted : 10/08/2021 9:09 am
Full Disk Access is only for the app, it does not help the driver load.
If you are not prompted to "Allow", then you may have old/obsolete extensions. Attach a SoftRAID Tech Support file, I can look
Posted : 10/08/2021 9:16 am
Topic starter
Posted : 10/08/2021 9:35 am
I may need some clarification. You have a Thunderbay 6 named volume that is mounting. It appears fine.
there is also a iMacM42 volume, RAID 0 that is not mounting. However, this is an Apple RAID 0 volume. Its lack of mounting is not from SoftRAID (it is not controlled by the SoftRAID driver), this volume is controlled by the Apple RAID drivers.
From looking at it, it appears the HFS directory is damaged. Do you have access to Disk Warrior to repair the directory? Disk Warrior is the best tool to repair damaged directories.
Otherwise, assuming you have backups, erase the volume with Disk Utility and copy your data back.
Posted : 10/08/2021 11:32 am
Yes there will be a macOS update at some point that fixes this.
Did you try 11.5.1 to see if it helps you? It does not have the fix, but has helped a good percentage of users with this issue.
For my installation of 11.5.1 it is clearly not a premanent fix. It still recurs under the circumstance where a complete shutdown is done and/or a new OS is loaded and then the original OS drive is re-started. This kext issue recurs at that time. Maybe you could explain for all the details?
Macbook Pro 14" Retina 2021 M1 Pro internal 1TB storage, 32GB RAM, two external T3 enclosures (2.5TB online storage), 6x500GB, EVO SSD, RAID 4; MacOS 12.3.1
Posted : 10/08/2021 11:55 am
I do not understand the actual bug, so I don't think i can explain any better.
I do not know when a permanent fix will be released. Since 11.5.1 fixes this for some, I am asking and gathering data when it works or does not.
Posted : 10/08/2021 12:22 pm
Topic starter
@softraid-support The drive/volume in question is the thunderbay 6. A few weeks ago this was APFS then this issue with mounting happened. I wiped it clean and formatted the volume to HFS+ but still the issue was there. Then for reasons that I don’t understand after a final uninstall and install it went back to mount again. The only thing I did different was to tick show HD is the finder’s preference this was ok for a fortnight.
Then yesterday it started not to mount again after WD restarted my Mac for an update. It is ok at the moment because I used your terminal command. But as soon as I restart my Mac it will again not mount and I will have to use the command.
If the directory is actually damage and causes the volume not to mount how come it did not mount when I change from APFS to HFS+, how come it mounted again for a forthright and how come it mounts with the terminal command that you gave. I really don’t want to back up my files and reformat it unless I’m absolutely sure that this will fix the issue.
Where can I get disk warrior? Thanks.
This post was modified 2 years ago by Mgarrucho
Posted : 10/08/2021 1:20 pm
Topic starter
@henry-in-florida 11.5.1 fixed this for a fortnight then it reverted back to not being able to mount.
Posted : 10/08/2021 3:15 pm
