10.14.6 Supplemental Update SoftRaid Mount Failures

If you let the system sit for a while, does the volume mount?

My guess is there is directory damage triggered by the update, and the volume is taking a long time to mount because OS X is repairing hte directory. Do you have Disk Warrior?

DW made things worse unfortunately. Rebuilding the array now—will post results.

If you let the system sit for a while, does the volume mount?

My guess is there is directory damage triggered by the update, and the volume is taking a long time to mount because OS X is repairing hte directory. Do you have Disk Warrior?

Rebuild and restore from backup worked. DW is surprisingly YMMV.

If you let the system sit for a while, does the volume mount?

My guess is there is directory damage triggered by the update, and the volume is taking a long time to mount because OS X is repairing hte directory. Do you have Disk Warrior?

So DiskWarrior run results in a cascade of errors in SoftRaid even on a freshly rebuilt volume—is this normal? If not, it shouldn't be recommended.

If you let the system sit for a while, does the volume mount?

My guess is there is directory damage triggered by the update, and the volume is taking a long time to mount because OS X is repairing hte directory. Do you have Disk Warrior?

If you are referring to "disk errors" when running Disk Warrior, ignore those. The directory is pointing to a non existent location on the disk, causing the error (SoftRAID reports every disk error regardless of cause. but we are going to start suppressing these errors in a future release of SoftRAID)

Disk Warrior is pretty amazing at recovering damaged directories, but it is not 100%. Seems with Mojave some damages caused by system upgrades are beyond the abilities of even this amazing utility. that is why the Preview is important, look at the changes (open a few ransom files also) before committing to the replacement directory.

Gotcha. Though it's not just modal "disk error" alerts kicked up in the Finder during DW dir replacement, volume becomes flagged in app as well and doesn't go away even after restarts and attempts to Clear IO Errors. Ignore this all?

If you are referring to "disk errors" when running Disk Warrior, ignore those. The directory is pointing to a non existent location on the disk, causing the error (SoftRAID reports every disk error regardless of cause. but we are going to start suppressing these errors in a future release of SoftRAID)

Disk Warrior is pretty amazing at recovering damaged directories, but it is not 100%. Seems with Mojave some damages caused by system upgrades are beyond the abilities of even this amazing utility. that is why the Preview is important, look at the changes (open a few ransom files also) before committing to the replacement directory.

When you use "clear IO errors" these errors should clear. Do they not?

They don't clear, no. I've tried this twice—this second time on a freshly initialized and rebuilt volume with no files. Notes: my drives are 4x Samsung 970 EVOs in an Express 4M2 and I'm running SoftRaid XT 5.75.

When you use "clear IO errors" these errors should clear. Do they not?

There are errors in the disks tile? Or the volume tile?
When you use "clear IO counters" and clear the errors, what exactly does or does not happen?

Disks tile for certain—all four disks had errors. As I recall, Clearing IO Errors on the individual disks resulted in an animated refresh of sorts, but definitely no change in status. Errors persisted after reboots and retry of Clear IO Errors, which prompted me to initialize and rebuild the volume. I DO back up my array, so a rebuild wasn't too big of a deal. Array is working properly now, so there was directory damage caused by the OS update. Will unmount the array prior to updating going forward.

If you see anythng like this again, I would like to see a support file. Clearing the error counters should clear everything regarding errors on disks.

Seeing the same thing on a brand new ThunderBlade. DW run results in errors in SoftRaid XT—Volume tile this time, individual disks tiles are fine. Clearing error counters does nothing. Obviously erroneous, but really should be addressed in the next build of SoftRaid.

If you see anythng like this again, I would like to see a support file. Clearing the error counters should clear everything regarding errors on disks.

You are referring to a bug/problem, where running Disk Warrior can result in an error(s) on the disks?

We have a volume in house that can reproduce this, and intend to fix this. Not sure whether 5.8 or a 6.0 release, though.

I've been having the same issue as well, my Thunderbay 4 Thunderbolt 2 will only work if its all connected to my iMac before I turn the iMac on. Any help will be greatly appreciated thanks.
Phil.