[Sticky] Monterey Other issues

@zaja 

When you include a support file, you generally do not need to add any screen captures.

You are going to need to "clear io counters" on the disks. Then, "recover failed disks" on the volume and let it validate.

Its possible your volume has directory damage to have triggered this, it can also happen if the disks ejected (loose cable etc).

@softraid-support Thanks for your answer. After clearing io counters and recovering failed disks no more errors appear.

When you say that the volume may have directory damage, I'm guessing this would happen again soon. If so, what would be the way to correct the issue?  

thanks

@zaja 

the ejects are a physical issue. It can cause minor damage to the directory (maybe like dropping a book)

Disk Warrior is the best application for repairing the volume directory, and can also help volumes stay "snappy". It only rebuilds HFS volumes, however.

@softraid-support Thanks for the reply. Unfortunately, I got two error messages today at the same time that the RAID disconnected:

It talks about turning off sleep, but unless I'm missing something, it is already turned off. See the images below:

@zaja 

Is Display sleep set to never also? This is a bug ini MacOS, so you need to disable all over where MacOS is trying to power things off.
Also, keep in mind that more complex setups are more likely to have disk eject events, including systems with Thunderbolt monitors.

@softraid-support yes, the display never goes to sleep. So I don't know what else I can disable to stop Mac power things off. Any thoughts?

In terms of my complex set-up, I've had it for 2 years and I had no issues until now, when I upgraded the OS. So, I can only guess that the issue is related to this OS upgrade and not from the set-up. It feels like something in the new OS set-up or system is making the RAID unstable. I'd really appreciate if you could help me figure out how I can solve this, as an unstable RAID is useless to me. Thanks  

@zaja 

In screen saver/screen lock, you have everything disabled also?

@softraid-support I have 'show screen saver after 1h' which is the longest time that I can choose

@zaja 

You can set everything to never. See if this works. At least it is a start point to figure out a solution.

@softraid-support @softraid-support Hi, I hadn't realised you could turn off the screen saver. Done. And now I think everything is turned off. See screenshots. And unfortunately, it's still happening. Any thoughts? Am I missing something? I'm still getting the same message saying to 'turn off sleep in the Energy saver panel of system preferences'

@zaja 
Do you have sleep ddisabled under Power also? This is a bug, so the sleep settings don't alway make logical sense.

@softraid-support Hi, I have everything disabled in the Power Adapter, apart from preventing Mac from sleeping when the display is off (see screenshots attached in the previous message). Am I missing anything else?

@zaja 

That looks correct. In Ventura, you may also need to put screen saver (lock screen) to never. Try that also.

The issue is your disks are still ejecting every time the system is left alone for a while, or manually sleeping?

@softraid-support Hi, I was trying to figure out if there was a pattern, but I can't find one. They eject and immediately remount once or twice a day when they are in use, not when the computer is left alone. I still get the same error messages I did (screenshots attached), but after I click on them, now the drives re-mount and no errors appear inside SoftRAID.

I'm in Monterrey, and everything related to energy consumption that I know is now on never, including screen saver (screenshots attached). So I can't see what else I can change.

I've had the same system for a couple of years and I never encountered any issue. The only change has been the recent update of the OS. 

Any thoughts? Thanks 

@zaja 

Make sure all cables are tightly connected. If you have done no changes, then try booting into recovery mode and "reinstall MacOS". It will not change any settings, delete any apps, etc. But might fix this.