Internal part of Softraid has stopped
I'm occasionally getting this message:
An internal part of the SoftRAID application has stopped functioning properly. Please quit SoftRAID and relaunch it.
Normally I just restart the application and I see no issues so it seem harmless, but I also don't think it should be happening.
The app is losing contact with the SoftRAID Monitor, so has to be restarted.
This seems to be a bug introduced by a security update. We have not yet figured out what is causing this.
It is indeed harmless. But annoying.
Any idea when this issue might be fixed? It makes "Verify" and "Certify" functions impossible to use since when the app crashes, the long running functions do as well.
I get this error several times a day if I leave the app running. macOS 10.14.6 beta 5. Happens on macOS 10.14.5 also.
Running a Mac mini (late 2012) - no T2 chip.
We do not yet have a fix for this.
Are you comfortable using the command line to do these functions? I can help with the commands. You need to identify the "disk#" of the device, either with SoftRAID (disk tile), or the terminal (diskutil list)
Lets say the disk is disk5:
softraidtool disk disk5 certify 3
Will certify the disk at disk5 with three passes.
Softraidtool disk disk5 verify
will verify the disk at disk5.
Same situation with running the verify from the command line - internal process fails and so does the verify.
Don't see a way to get around this. Verify and Certify can't be done. Now running Mojave 10.14.6 public release.
A solution to this would be nice.
I know a solution would be nice!
But when you certify from the command line, SoftRAID application is not involved. It should not even be running. Let the certify complete from the command line, you will get a "prompt" when completed.
But it doesn't complete! It simply stops running maybe a third of the way through the verify or certify (or at some other undefined point in the process) and the command prompt returns.
Generally when I've been able to verify a 5 TB drive to completion, it takes there days. Now, it will stop after say 12 hours, whether I've used the command prompt or GUI to initiate it. Makes no difference that I can tell.
Let me be clear on what you are seeing, so I can address this correctly.
(We have to separate the bug where the application can quit)
If you start a certify with a 5TB drive, yes it should take about 3 days. If you start with the command line and do NOT have SoftRAID app running, does it stop in 12 hours? Does terminal return to the command line prompt?
Or, is this the scenario where started via command line, and you kept the app running? Then certification also quit when the app put up the "I need to quit" dialog box?
When you run SoftRAID to certify, is it "about 12 hours" when the application quits on you?
thanks for helping me be sure I understand.
I'm running the verify process again to be sure of the situation. I have started the verify from the command line without the app running. I actually tried to run the verify from the app, but it crashed with an error code = 0 immediately. The command line version seems to be running normally so far.....
What specific disk is this and how is it connected?
Turns out, SoftRaidtool does not prevent sleep when run from a workstation which has sleep enabled. When sleep occurs, SoftRaidtool quits. Servers generally have sleep disabled, but not workstations.
Might be a nice enhancement for SoftRaidtool to prevent sleep while running.
SoftRAID neither prevents, nor helps the system sleep, the driver only follows the OS X settings.
Are you seeing the tool crashing when you sleep? softraidtool should not quit if there are SoftRAID disks connected.
Yes, it either crashes or terminates, either way the long running verify or certify process halts when the Mac sleeps.
the internal part of the SoftRAID application quitting is not a serious issue. Annoying, but not serious.
Restart the app. If you were certifying, restart it, it will pick up where it was when this stopped. You an also certify via the command line.
"Crashes" is different, and I would like more information if there are any crashes of any component.
Have tests on 10.14.6 shown any progress on the app losing connection with the system? Not a big deal by any means... except the small anxiety attack I have anytime I see an error from my array surface :)