One or more of the disks for the volume ___ is no longer usable

@mountaincat 

I have not tested, removing the volume from Time Machine, then adding it back, if Time Machine will recognize the prior backups and keep the increments. Of course it should. It appears this will work, but I have not tested a restore, after a remove disk, and adding it back.

Just got a SoftRAID kernel panic. Is this related? Here it is along with softraid support log.

@mountaincat 

Its different. When do you get this panic?

If you change sleep to "never" does it still crash?

SoftRAID is inside this backtrace it appears, so our engineering would be very interested in investigating this further.

@softraid-support I am currently using manual sleep settings via PMSET right now. The values are:

AC Power:
Sleep On Power Button 1
standby 0
ttyskeepawake 0
powernap 0
displaysleep 10
womp 0
networkoversleep 0
sleep 60
tcpkeepalive 0
autorestart 0
disksleep 60
SleepServices 0

The system had been sleeping today and when I woke it up I saw the message that it had restarted with the kernel panic.

@mountaincat 

Thanks. Same kind of panic?

@softraid-support Not sure what you mean exactly. The panic I've generally been getting has been after clicking through all the drives locked messages, then, it will either work properly, or it will lock up, like no pointer movement, and panic/reboot. For this particular panic, it must have happened on its own, because when I went to log in the system warned me that it had restarted due to an error.

This is making my work impossible, so I surrendered to prevent all sleeping for the time being. That is not going to work long term for me. But my current settings are:

AC Power:
Sleep On Power Button 1
standby 0
ttyskeepawake 0
powernap 0
displaysleep 10
womp 1
networkoversleep 0
sleep 0
tcpkeepalive 0
autorestart 0
disksleep 0
SleepServices 0

Despite that change, I still got a panic in the middle of working. In addition, I am still getting the problem where I launch softraid, and although the monitor is running in the menubar, the softraid app is completely blank when launched. No drives listed. Even though the Thunderbay works in the finder. If I relaunch the monitor then the app will work. This time after a few minutes the app started to work again without relaunching. Not sure if that is connected but I never previously had that issue.

Panic and log attached.

I need to see what engineering thinks of this, the SoftRAID driver is in the backtrace.

Today, despite sleep being turned off, I came back to the system and was greeted by the kernel panic restart message again. System is now what I consider to be unstable. No reason for these kernel panics. It's the same MacMini M1 with no changes. Softraid is listed in the backtrace. Log files:

@mountaincat 

Wait till I can get some feedback next week.

Hi, I've come back from a few weeks away. Do you have any more info? I need stability here. Thanks

@MountainCat
I am waiting for feedback from engineering. This appears to be related to a hibernation issue in macOS. We are in discussions with this with Apple. We may need a "core dump" for this.
This is repeatable? How long do you step away for this to happen ? More than 2 hours?
does it happen about 20-30% of the time?

Don't know yet. I removed and reinstalled SoftRaid because I was often getting a blank window when launching it. Still have sleep off. But it hasn't happened yet since the reinstallation. The SoftRaid blank launch issue does appear to be fixed from the reinstall. Before the reinstall, the panic was happening reliably several times a day. No it isn't, at least not in the last couple of days. However, I suspect that the two are not totally correlated and I may just be temporarily lucky, because the issue has come in waves before.

@MountainCat

These issues are frustrating when they come and go. Let me know when you see a pattern or if it comes back. the 7.0.1 is a obscure issue we have not figured out yet, but hopefully soon. Running 7.0 is the quickest workaround. (not installing the driver). the app rarely needs to run, so it is not a critical bug.