Did SoftRAID 6 fix the issue where enabling sleep caused instability and potential kernel crashes?
I'm loath to try it once more out of fear of corrupting my volumes.
I have a RAID 5 volume in an OWC ThunderBay4 which is currently linked to a 2019 iMac via Thunderbolt 3.
PS: On a positive note, the hard drives in this ThunderBay were moved from my old Mac Pro and I just noticed that the volume was created in October 2014 and has 0 IO errors up to now with almost 5 Billion IO operations! Rock solid indeed.
Refresh me what exact issue you are referring to?
there is no instability/kernel panic from sleep as a generic issue.
There is a "volume lock" issue, where macOS can renumber disks waking from sleep, where SoftRAID detects this and forces a restart to protect against data corruption.
Let me know exactly and I can see if I can answer. But we have not changed any driver settings that would affect sleep, it is totally under the control of macOS.
When I turn on sleep, on wake-up, I either get the SoftRAID message that the disks were renumbered and I have to restart, or I get a system message telling me there was a problem and the computer had to restart. Not sure they are the same.
I just tried it over the weekend and it's still the case so back to scheduled shut-downs and no sleep for me.
Here it is...
What if you connect your enclosure directly, without the dock? have you tried that?
- Also, I am surprised your SoftRAID driver is loading, you have multiple unsigned and obsolete extensions.
The enclosure is connected directly to the Mac. My second screen is hanging of a doc, connected to the enclosure but not sure if that would have an impact?
How do i get rid of those old extensions?
tun the terminal.app and paste each line below in:
sudo rm -r /Library/Extensions/JMicronATA.kext
sudo rm -r /Library/Extensions/SiLabsUSBDriver64.kext
sudo rm -r /Library/Extensions/SiLabsUSBDriver.kext
sudo kmutil clear-staging
sudo kextcache -i /
restart. this will eliminate those drivers.
I would do a test to see if removing the dock and/or Monitor helps your sleep issue. Worth a try, even though in theory, the Thunderbolt buses on the Mini M1 are all independent.
Removing the doc (and second screen) slaved from the enclosure seemed to have improved stability but this morning i got the message again that the computer (a 2019 iMac Intel i9 btw) had to be restarted due to a problem. Console is no help. Could be enabling power nap (the only difference between last night and the night before) caused the issue.
Back to disabling sleep.
Thanks for the help in cleaning up the extensions.
The forum only accepts .txt attachments, but you can save the next crash like this in text edit and save it as text, you can attach it. I suspect this is a watchdog crash. (a macOS timer)
OMG, third time I'm trying to enter this response.
Several processes crashed and I'm not sure which one was responsible for the kernel panic. AdobeIPCBroker and bzserve (a Backblaze process) are the most common. I'm already regretting testing sleep very much.
However, after the last crash, Time Machine stopped working. A First Aid run with Disk Utility showed corrupt snapshots being the culprit but removing those only temporarily solved the issue as new snapshots (except for the very first one) show the same corruption: some hash witch is not what it should be (times 100).
So there's probably an underlying problem with my startup disk now. I also see an error message in First Aid that a number of dstreams are missing their associated stream ID objects. Whatever that means?
To add insult to injury, after the update to SoftRAID 9.05 this morning, my RAID5 volume on the external OWC enclosure doesn't mount anymore. This volume contains all my data so it's critical!
Trying to mount the volume in SoftRAID does nothing. Restarting does nothing.
New tech support report for information.
Try deleting the two wacom drivers, then resinstalling SoftRAID's driver.
the terminal commands are:
sudo rm -r /Library/Extensions/Wacom Tablet.kext
sudo rm -r /Library/Extensions/FTDIKext.kext
sudo kmutil clear-staging
sudo kextcache -i /
restart. Then "reinstall SoftRAID driver" from volumes menu. See if it triggers the System Preferences/Security dialog box.
Did you get that prompt when you updated the driver?
I did get the prompt after updating to 9.05. There's something not completely clear about that process though. SoftRAID wants me to restart after installing the driver but then System Preferences pops up to allow me to clear OWC as trusted source and also wants me to restart. Which restart takes precedence?
Anyway, I deleted the Wacom kext and all the rest but can't 'reinstall SoftRAID driver'. The menu item is greyed out. The volume still doesn't mount.
Silly me. I had to select the startup volume for the 'reinstall driver' menu to be available (of course).
However, when I do that, the volume mounts but then SoftRAID wants me to restart and after the restart the volume again doesn't mount. Catch 22.