SoftRaid 7.0.1 Kern...
 
Notifications
Clear all

SoftRaid 7.0.1 Kernel Panic

7 Posts
4 Users
0 Reactions
724 Views
(@richlesh)
Posts: 1
New Member
Topic starter
 

Been using SoftRaid with OWC Thunderbay since Nov on M1 Mac Mini with no problems.  After the latest Ventura 13.2.1 upgrade I can't boot because the SoftRaid kext causes a kernel panic.  I noticed that this is an outstanding issue and that setting stripe size to 64k works around the problem.  How do I set stripe size to 64k in SoftRaid 7.0.1?  When I try to create a new RAID set the only options are RAID type (I still want RAID5) and "Optimize for".

 
Posted : 08/03/2023 11:55 am
(@softraid-support)
Posts: 9200
Member Admin
 

@richlesh

the next step lets you choose the stripe unit size.

 
Posted : 08/03/2023 3:44 pm
(@drlizardo)
Posts: 5
Active Member
 

So if I have to remake the RAID in order to get around this new and exciting problem, what am I supposed to do with the 30TB of data that are already on that volume? Buy a second RAID to put that on so I can fix the first one?

 
Posted : 14/03/2023 1:04 pm
(@softraid-support)
Posts: 9200
Member Admin
 

@DrLizardo

Note: you should never rely on a single source for all your data, I recommend a backup locally and a cloud (BackBlaze) or off site backup also. Data is expensive and fragile.

 

Since we have a likely fix release of 13.4, maybe you can get by with one of these two methods:
1. when you restart, have your unit disconnected for about 5 minutes, then plug it in.
2. Pull out one drive slightly, so your system starts, then after 5 minutes, push it in.

 
Posted : 14/03/2023 2:43 pm
(@drlizardo)
Posts: 5
Active Member
 

@softraid-support Thanks, I'll give it a shot. My data is indeed backed up to Backblaze but restoring 30TB of data from their methods would take days.

 
Posted : 14/03/2023 4:45 pm
(@softraid-support)
Posts: 9200
Member Admin
 

@drlizardo 

Glad it is backed up! So many users conflate buying a RAID system with backing up. ;-)

 
Posted : 14/03/2023 7:30 pm
(@dragonshivu)
Posts: 8
Member
 

I had the same issue. Working with MacOS 13.4 beta seems to solve the problem without having to play with any workarounds.

 
Posted : 17/04/2023 11:13 am
Share:
close
open