Freeze/restart only when backing up SoftRAID volumes to SoftRAID Time Machine volume
Understand now. that should be OK, but I don't understand the kernel panic in that case.
Note: the dock does not have enough heat dissipation to be used full time as RAID disks/volumes. RAID may be OK, but heat is a possible issue, so not recommended, especially for HDD's. The XT license is for all "Certified" OWC enclosures, and the Docks are not certified for RAID, so are not included.
(I would have liked for the docks to be supported with XT licences, but my understanding is this was in part deemed a support cost issue.)
Got it, thanks.
I used CCC to back up my large SR Media volume to my SR Backup volume, from scratch, overnight. Looks like it completed at 5am without restarting, for the first time in almost two years, but then it restarted a couple hours later for some reason.
I did get the Send To Apple window again and attached the text file. I've attached the SR report too.
I have Amphetamine running now, but it's making the volume icons on my desktop "refresh" every 10 seconds which is disconcerting. Any way we can get this to work without a kludge? Before the last couple years I had very few if any problems with SoftRAID Thunderbay volumes but it's been very difficult since. I don't know how much longer I can hold out.
Thanks again for your help.
Apr 5 0421 Virus-MacBook-Air syslogd: ASL Sender Statistics
Apr 5 0554 Virus-MacBook-Air syslogd: ASL Sender Statistics
Apr 5 0505 Virus-MacBook-Air syslogd: ASL Sender Statistics
Apr 5 0524 Virus-MacBook-Air syslogd: ASL Sender Statistics
Apr 5 0549 Virus-MacBook-Air syslogd: ASL Sender Statistics
Apr 5 0638 Virus-MacBook-Air syslogd: ASL Sender Statistics
Apr 5 0608 Virus-MacBook-Air syslogd: ASL Sender Statistics
Apr 5 0608 Virus-MacBook-Air bootlog: BOOT_TIME 1649159528 705474
This panic, SoftRAID is in the backtrace, so it was definitely related to an I/O to a SoftRAID disk.
One thing I notice is your Time Machine is still HFS. This was migrated from a pre-Monterey Time Machine, correct (Monterey now requires APFS on all new Time Machine volumes)
I wonder if HFS/Time Machine is related. Maybe Time machine activated? Just speculating.
Nope, the Backup RAID 5 volume is HFS because I'm now using Carbon Copy Cloner for all SoftRAID stuff. I learned the hard way Time Machine on APFS HDDs is a poopshow. I switched to only using Time Machine to backup my internal SSD to a small SSD in my OWC TB Drive Dock, instead.
But after using that for a couple days I think I'm going to get rid of TM completely because backing up is so much slower than CCC, snapshots take up too much space on the source, and running first aid on it takes forever due to those hourly snapshots. I can use CCC to do snapshots on the target SSD instead of the source. Incremental backups take mere seconds that way.
Another restart this morning while building a new Plex library from videos started on Media volume plus hourly CCC backups. Send To Apple text attached. Thunderbolt is mentioned. This might be my fault because I didn't return my "Turn display off after" to "Never" after testing sleep with my new LG 34WK95U display which was exhibiting wake from sleep issues. It's back to Never now.
After removing Amphetamine and before trying Caffiene, my Thunderbays appear to have stopped spinning down for going on 36 hours now.
Reports are the public 12.4 Monterey beta is stable — and I have snapshot backups. Would it be helpful for me to update and see if Apple fixed anything? I'm willing to try it if it won't make anything worse.
The panic was a "Wake transition timed out after 35 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOThunderboltFamily. Thread 0x2b58c1"
I found this Apple discussion:
One of the responders indicated contacting Apple directly on this, that user had a Thunderbolt monitor. Its clearly a time-out issue of some kind.
let us know if changing the sleep setting avoids this.
Yep, that has to be it. I'm connected directly to the display with a Thunderbolt cable. The other port on my Air is for the Thunderbay daisy chain. Also Thunderbay Daisy Chain is the name of my new band.
That was just a lame joke ;)
I installed the 12.4 public beta today and all Thunderbolt drive spindowns have ceased. I've also had zero kernel panics after waking from sleep with the new LG display. And no crashes while backing up with CCC. Wow.
Too early to say for sure, but I'm optimistic that Apple fixed something on their end.
I'll keep you posted.
I installed the macOS 12.4 public beta which has seemed to resolve my ThunderBay spin down issues. Freakin' huzzah. No crashes while backing up with CCC at all, either. Running great for 2 days.
However I am experiencing restarts after sleeping my system overnight, probably related to the display over Thunderbolt. (The next thing I'll try is a Display Port cable, but then I'll need to buy a Thunderbolt dock so I can charge my Air while it's hooked up to my ThunderBays.) I wake it up and am greeted with the Report To Apple thing. However now that I'm beta testing it enabled some more detail, I filed a report with Feedback Assistant, and it gathered up the regular log and panic logs plus some .core files that I've never seen before.
Would those be useful for you? I don't know if I could attach them since they'd have to be zipped?
Let me know if you'd like to see any of this stuff, in case it could shed some light on the possibly-fixed spin down or anything SoftRAID related.
Did you get a "report to Apple" dialog box? the text in there would be potentially useful. (normal crash logs are near impossible to read.)
If you can next crash, attach that, just copy/paste the text into text edit, "make plain text" and save it, and you can attach that.
the detailed core dumps are beyond my ability to interpret.
The reason I don't like .panic log formats is they are unreadable, unlike the logs that show up when you "Report to Apple", and copy/paste the text into text edit, where it is all aligned, etc. the .core is "normal", however.
If you look at this line:
"panicString" : "panic(cpu 4 caller 0xfffffe0020216a60): Wake transition timed out after 35 seconds while calling power state change callbacks.
Suspected bundle: com.apple.iokit.IOThunderboltFamily.
this is some kind of time out on the Thunderbolt bus. I have seen these discussed on Apple forums and generally "call Apple support" is the response. the ones I saw related to Thunderbolt monitors, I don't know if that is the exclusive cause, or what, yet.