Monterey Crash/kern...
 
Notifications
Clear all

[Sticky] Monterey Crash/kernel panics

Page 19 / 22
(@softraid-support)
Member Admin

@maximegoussephoto 

While we have seen a small number of cases where 64k does not fix this, generally yes it does.

Disable Safeguard on your volume.

Delete the volume

Create a new RAID 5 volume

Select 64k Stripe unit size when prompted.

that should work.

ReplyQuote
Topic starter Posted : 06/07/2022 4:38 pm
(@nicksyrett)
Active Member

@softraid-support Thanks for your reply but it doesn't really help me.  I am going to need to move away from Softraid.  I cannot have my systems go down like this, and it has been a less-than-good experience with you for about 3 years now.  I'm not sure I understand how, with all the many Betas that Apple releases, your software still doesn't work.  You provide a critical function in many professionals workflows but a failure like this isn't something we can live with. BTW my migration to M1 was a clean install bit a migration assistant install. 

I've opted to move everything to Apple Raid (raid0) and just back those drives up daily to another larger drive. 

Please can you tell me the best way to get my drives from Raid 5 to Apple Raid.  I think I saw a feature in your software that does this?  How stable is it? Any advice?

Thanks for your help.

This post was modified 3 months ago by nicksyrett
ReplyQuote
Posted : 06/07/2022 6:04 pm
(@softraid-support)
Member Admin

@nicksyrett 

You cannot migrate to RAID 0 from RAID 5. You need to backup, delete the volume zero disks, then create an Apple volume.

 

The current issue is a ARM/MacOS bug. It cannot be "fixed" from SoftRAID, Apple has to put a fix in macOS. We bought them a users system, so they could see it in Apple engineering, agreed it was their bug, but not fix has made it into macOS yet. We are told they have a fix, but when it will make it into any macOS release is unknown.

ReplyQuote
Topic starter Posted : 06/07/2022 8:58 pm
(@qiji07)
New Member

 I have had the exact same experience with my new M1 Max 12.01 with Thunderbay 8. Have you been able to reach any conclusions yet? I am stuck in the water.

 

This post was modified 3 months ago by SoftRAID Support
ReplyQuote
Posted : 06/07/2022 9:19 pm
(@softraid-support)
Member Admin

@qiji07 

Which problem are you having? The panic with connecting your volume?

Is this a new enclosure, so you can delete the volume and create it again with 64k stripe unit size?

ReplyQuote
Topic starter Posted : 07/07/2022 3:05 am
(@nicksyrett)
Active Member

@softraid-support Thank you again for responding.  I changed my mind and decided to try the step you suggested (waiting at least 5 mins).  This seems to have worked.  No crashes.  

 

Question - is there a way to determine whether my Raid 5 drives have 16 or 64 stripe?  I was working thru them (moving datas, deleting volume, recreating with 64 stripe) but got covid in the middle of this process and have forgotten which drives I did.  How can I tell?

Thanks again.

ReplyQuote
Posted : 07/07/2022 2:30 pm
(@softraid-support)
Member Admin

@nicksyrett 

In the SoftRAID volume tile, expand it, it shows the stripe unit size.

ReplyQuote
Topic starter Posted : 07/07/2022 4:00 pm
(@nicksyrett)
Active Member

@softraid-support 

I've now been through all my external hard drives changing the stripe size etc.   Everything is working well and I don't get any crashes.  So that is good.

However, my Mac does seem to be crashing overnight - every time I sit down in front of it each morning it has a crash report etc.  It always begins with:

"panic(cpu 10 caller 0xfffffe00144508d4): Sleep transition timed out after 35 seconds while calling power state change callbacks. Suspected bundle: com.apple.driver.AppleTypeCPhy. Thread 0x66b55."

I think "AppleTypeCPhy" has something to do with thunderbolt of USB drivers?  So I suspicion that softraid could still be the culprit here.  Any ideas?

Thanks

 

ReplyQuote
Posted : 15/07/2022 12:58 pm
(@softraid-support)
Member Admin

@nicksyrett 

This is a macOS bug, it can happen even with no SoftRAID disks.

 

What if you try using caffeine to keep the drives awake?

​​​​​​​ https://intelliscapesolutions.com/apps/caffeine

ReplyQuote
Topic starter Posted : 15/07/2022 1:20 pm
(@rsmith4321)
Active Member

I’ve been using Caffeine and had no crashes for weeks

ReplyQuote
Posted : 15/07/2022 1:26 pm
(@nicksyrett)
Active Member

@rsmith4321 

Allow me to ask a few questions about Caffeine.  I have installed it but there does not seem to be many options.  For example, I don't want my screen on all night - sounds like this stops the screen from sleeping.  I'm only interested in trying to avoid the crashes caused by the softraid drives etc.   Any thoughts?

ReplyQuote
Posted : 15/07/2022 2:02 pm
(@softraid-support)
Member Admin

@nicksyrett 

Turn off the screen at night.

Caffeine exists not because of SoftRAID, but because this is a generic macOS issue. Its been going on for 10 years.

To this day, I can take a Apple RAID volume, connect it to an M1, as an example, running the latest macOS, let it sleep, and every 15-30 minutes or so the drives will spin up and after a while spin back down. 100% of the time.

ReplyQuote
Topic starter Posted : 15/07/2022 2:06 pm
(@rsmith4321)
Active Member

@nicksyrett Just use the drive alive feature. You don’t have to enable anything else. The screens will sleep normally and shut off.  You don't have to manually shut off displays as stated above. 

This post was modified 3 months ago by rsmith4321
ReplyQuote
Posted : 15/07/2022 5:42 pm
(@jmax313)
Active Member

Hi! 

Having issues with all versions of softraid, no matter what I do I get kernel panics. Please help! I've attached my log files from 3 seperate versions of the softraid software. Really need to connect to my raid.

 

J

 

ReplyQuote
Posted : 08/08/2022 10:44 am
(@softraid-support)
Member Admin

@jmax313 

This is an ARM, correct?

This is a DART chip bug/crash, triggered by RAID 5 volumes.

Solutions are:

For most users with this issue, waiting 5 minutes after restart, avoids this.

Remove cover, pull out one disk, then after 5 minutes, you can push the drive in and it should not cause the panic

Or, delete volume, create it again as RAID 5 with 64 k Stripe unit size

Apple is finally fixing this in Ventura, macOS 13 in the autumn.

 

ReplyQuote
Topic starter Posted : 08/08/2022 1:46 pm
Page 19 / 22
Share:
close
open