Any idea why upgrading to 7.6 from 7.5 the helper tool gets hung up?

Are you getting the "monitor" failed, or a part of the "Application" failed?

Posted by: @softraid-support

↑

Are you getting the "monitor" failed, or a part of the "Application" failed?

The same part of the "Application" failed error. try restarting.

Also note that on my M1 MacBook Pro MAX it installs just fine.

@john-graham 

I think we have enough people trying the debug version, so just hang in there until we can figure this out.

@bob_stan 

Same as John, we created a debug version to figure this out, but probably have enough people generating debug logs.
If you create a new admin user, you get same issue?
(A clean install, without migrating data, on a second system should work also, its easy to do now, just create a new volume with DiskUtility, startup in recovery mode, "reinstall MacOS", point it to the new volume and install. Use the same admin name, but do not import data.)
that will almost certainly get around this, but we want to figure out root cause.

Posted by: @softraid-support

↑

@bob_stan 

Same as John, we created a debug version to figure this out, but probably have enough people generating debug logs.
If you create a new admin user, you get same issue?
(A clean install, without migrating data, on a second system should work also, its easy to do now, just create a new volume with DiskUtility, startup in recovery mode, "reinstall MacOS", point it to the new volume and install. Use the same admin name, but do not import data.)
that will almost certainly get around this, but we want to figure out root cause.

I tried that with Sonoma, but no lock. It did install OK on my M1 Mac Book.

@john-graham 

Intersesting, on a clean install? Very strange.

Posted by: @softraid-support

↑

@john-graham 

Intersesting, on a clean install? Very strange.

I get this from the logs.

Sep 28 10:43:59 - SoftRAID Application: Launching application: SoftRAID version 7.6
Sep 28 10:44:01 - SoftRAID Application: Tool terminating - status = 6, reason = NSTaskTerminationReasonUncaughtSignal

Posted by: @softraid-support

↑

@john-graham 

Intersesting, on a clean install? Very strange.

I have this problem too.  I'm going to offer a thought that there's something in common with our storage hardware configurations that is causing the app to bail when it starts to collect the system state.  Here's mine:

RAID 10:

• two Sonnet M.2 4x4 PCIe cards, each with 4 Samsung 970 512GB SSD drives
• four RAID 1 mirrors striped as RAID 0

RAID 1:

• two Samsung 870 EVO 4TB SATA drives off the internal SATA connectors

non-RAID:

• stock Apple 1TB SSD boot drive
• external LaCie 4TB USB-C drive

macOS 13.6 (22G120)

Posted by: @dpz

↑

I have this problem too.  I'm going to offer a thought that there's something in common with our storage hardware configurations that is causing the app to bail when it starts to collect the system state.  Here's mine:

RAID 10:

• two Sonnet M.2 4x4 PCIe cards, each with 4 Samsung 970 512GB SSD drives
• four RAID 1 mirrors striped as RAID 0

RAID 1:

• two Samsung 870 EVO 4TB SATA drives off the internal SATA connectors

non-RAID:

• stock Apple 1TB SSD boot drive
• external LaCie 4TB USB-C drive

macOS 13.6 (22G120)

 

To add I'm on a 2019 Mac Pro. Thunder bey 4, with 4 Iron wolf 8TB Raid 5 drives.

@john-graham 

Its very unlikely this is a hardware issue, the problem is SoftRAID Monitor is not getting through to the Application. We have another debug build I am sending out to gather information.

@john-graham 

What if you go to System Settings/General/Login.
Is OWC listed (and enabled) for background services?

@softraid-support 

For me it is, but looks a little weird:

@bob_stan - this is the error that I get exactly, as per the screen shot of 27/9/23 at 7:33pm

I have OWC running in the background under general login.

I have various OWC external enclsoures running on my MacPro 2019, all TB set to R0 on the enclosure.  I also have an 8TB OWC accelsior M2 RAID PCIe card inside the machine also set up with OWC R0.  Note 7.5 and all previous 6 versions have run fine.  I've only ever had problems trying to run 6.1 on 13.5.2.  Not tried it on 13.6 yet given the issues.