Big Sur on M1 machi...
 
Notifications
Clear all

[Sticky] Big Sur on M1 machines and SoftRAID issues

880 Posts
78 Users
38 Reactions
140 K Views
(@joemikeb)
Posts: 93
Member
 

@softraid-support

I am running macOS 11.4 beta 1 and nothing has changed since macOS 11.3 beta 7 or 8. I suppose it was too much to hope for, but I had hoped encryption and the SoftRAID 6.0.3 app's issue with APFS would have been fixed. Perhaps a subsequent macOS 11.4 beta or SoftRAID 6.0.4? 🤞

______________

Make intentional errors β€”
Otherwise the Great Spirit
realizes you have fulfilled
your purpose on earth.

β€” Navajo saying

 
Posted : 23/04/2021 3:12 pm
(@softraid-support)
Posts: 9197
Member Admin
Topic starter
 

APFS is on us, we will be addressing APFS in the user interface in 6.1.

Β 

Encryption is on macOS. We are hoping it gets addressed soon.

 
Posted : 23/04/2021 10:16 pm
(@softraid-support)
Posts: 9197
Member Admin
Topic starter
 

To all who are subscribed to this thread. macOS 11.3 has been released, which fixes the M1 driver issue.

Β 

thanks everyone for your patience in this, it has been frustrating waiting.

 
Posted : 26/04/2021 3:59 pm
(@eccles)
Posts: 1
New Member
 
Posted by: @softraid-support

To all who are subscribed to this thread. macOS 11.3 has been released, which fixes the M1 driver issue.

Β 

thanks everyone for your patience in this, it has been frustrating waiting.

No, not fixed here, fresh install of 11.3 and softraid Extension does not load. Using Softraid 6.0.3!

 
Posted : 28/04/2021 3:41 am
(@sunstarfire)
Posts: 129
Estimable Member
 

OK, so where does the Beta-discussion continue? Is there a dedicated thread for testing 6.1?

 
Posted : 28/04/2021 5:11 am
(@mountaincat)
Posts: 56
Trusted Member
 

I have not had a disk lockup issue now for 11 days. I wish I could tell you what changed but nothing did that I am aware of. I don't want to jinx it, but if that issue is over I am a happy camper. Now headed to finally update SoftRAID to official version 6.

 
Posted : 28/04/2021 10:17 am
(@softraid-support)
Posts: 9197
Member Admin
Topic starter
 

@sunstarfire

I will open one when we have a 6.1 beta. ;-)

We are working on an interim release then on to 6.1.

 
Posted : 28/04/2021 11:00 am
(@softraid-support)
Posts: 9197
Member Admin
Topic starter
 

@eccles

Β 

M1 works now, with 11.3. There are two reasons you may not be working

the most usual is enabling third party extensions:

https://support.apple.com/en-lk/guide/mac-help/mchl768f7291/mac
Select reduced security and enable this:
Select the β€œAllow user management of kernel extensions from identified developers” checkbox to allow installation of software that uses legacy kernel extensions.

Then when you "reinstall SoftRAID driver", you should get the dialog box to go to System Preferences/Security to "Allow" OWC as an identified developer?

Β 

If you do not see this dialog box, then the solutions is deleting obsolete extensions. Big Sur does not like old extensions hanging around. I am working on clarifying these instructions into a document.

 
Posted : 28/04/2021 11:02 am
(@thierrycoopman)
Posts: 14
Active Member
 

Β 

Is there a known issue with ThunderBlade?Β 

I have had issues (unresponsiveness in Finder, IO timeouts I think) with 6 Beta and 11.0/11.1. So I held out for the official 6.0.3 and 11.3 to use the device again.

The issues seems to be same/similar, even if it's a bit more "stable".

My media test is rebuilding the iCloud Photo Library of +-700GB download originals from scratch. It gets up to 30-40GB every time and then gets 'stuck'. Photos.app unresponsive, Finder unresponsive, restart waiting forever, and eventually kernel panicking.

If the device is not connected I have no issues, so my suspicion is related to the heavy IO resulting in the use of Photos.app (other use, normal files copy etc... seems to be ok). The device is formatted APFS

Attached is the kernel panic that happened when I started a reboot at the time the symptoms happened.Β 

Let me know how and if I can provide more info, the whole system becomes "unresponsive" at a certain point, so not sure what info I get at that moment.Β 

This post was modified 5 years ago by thierrycoopman
 
Posted : 29/04/2021 3:55 am
(@softraid-support)
Posts: 9197
Member Admin
Topic starter
 

Also attach a support file. There is no generic issue with the Thunderblade, not that you cannot have a specific issue.

the panic was a kernel bug in macOS, when shutting down, it takes too long to flush disk cache's so panics. I do not think it is specific to your thunderbay, but generally more with HDD's. (unless one of your blades is hanging)

 
Posted : 29/04/2021 4:19 am
(@thierrycoopman)
Posts: 14
Active Member
 

@softraid-support

I seem to be able to repeat this issue, so I guess that is a good thing. When the issue happens, I'm not sure if I can generate a report, as all IO to the Thunderblade seems blocked.Β 

I ran the report now (just after connecting the drive) and attached it, and I'll try to get a report when the issue happens again, but since the OS is more or less blocked every time the drive is involved, there is no guarantee.

Β 

 
Posted : 30/04/2021 3:21 am
(@thierrycoopman)
Posts: 14
Active Member
 

Β 

@softraid-support

Got it reproduced after 10 minutes

When asking the Support report, SoftRaid "stopped responding", and I requested the sample through Activity Monitor.Β 

Then I started using the disk through Finder, and the computer locked up.Β 

To note, I used this device on Catalina Intel Macs before without any issues, what is different:

- M1 versus Intel

- APFS versus HFS+

- Big Sur versus Catalina

- Softraid 6 verus Softraid 5

Β 

I consider any of these changes the possible culprit, but it's hard to get pin it down.Β 

Β 

Β 

Β 

Β 

Β 

 
Posted : 30/04/2021 3:51 am
(@softraid-support)
Posts: 9197
Member Admin
Topic starter
 

I am seeing a handful of these kinds of crashes all of a sudden, mostly watchdog panics. (A couple are "dart", which may be a hardware issue.)

My money is on M1, but its a guess.

Can you generate a system Diagnose file after a crash?

sudo sysdiagnose -f ~/Desktop/

I can tell you how to get it to us once you have it.

Β 

Β 

Β 

 
Posted : 30/04/2021 5:13 pm
(@thierrycoopman)
Posts: 14
Active Member
 

@softraid-support The issue happened again, I got the kernel panic again, and I made a sysdiagnose right after the crash

Below is the pop up to be sent to apple after the boot.

(snipped for brevity)

panic(cpu 1 caller 0xfffffe0028189e30): watchdog timeout: no checkins from watchdogd in 305 seconds (10421 totalcheckins since monitoring last enabled), shutdown in progress
Debugger message: panic
Memory ID: 0xff
OS release type: User
OS version: 20E232
Kernel version: Darwin Kernel Version 20.4.0: Fri Mar Β 5 01:14:02 PST 2021; root:xnu-7195.101.1~3/RELEASE_ARM64_T8101
Fileset Kernelcache UUID: 50FBF6E680084E0B373849299AD93D92
Kernel UUID: 4C260D10-173B-3E11-A79B-9D423527AAAC
iBoot version: iBoot-6723.101.4
secure boot?: YES
Paniclog version: 13
Β 
Panicked task 0xfffffe16668f4688: 56277 pages, 474 threads: pid 0: kernel_task
Panicked thread: 0xfffffe1666d17960, backtrace: 0xfffffe30698678b0, tid: 440
Β 
Β Kernel Extensions in backtrace:
com.apple.driver.AppleInterruptController(1.0d1)[1903B10D-E35E-3864-9842-4EE73CE97CD2]@0xfffffe002645c000->0xfffffe002645ffff
dependency: com.apple.driver.AppleARMPlatform(1.0.2)[58B65D99-A7B7-316F-8E28-CEDEE98BBC3E]@0xfffffe0025c50000->0xfffffe0025c9ffff
com.apple.driver.watchdog(1.0)[BEE7A0FC-B21D-32F4-8632-C669EA683887]@0xfffffe0028188000->0xfffffe002818bfff
com.apple.driver.AppleS5L8960XWatchDogTimer(1.0)[2B2069CC-0C2D-3A5A-B4FA-D10F4C2D8371]@0xfffffe00266e4000->0xfffffe00266e7fff
dependency: com.apple.driver.AppleARMPlatform(1.0.2)[58B65D99-A7B7-316F-8E28-CEDEE98BBC3E]@0xfffffe0025c50000->0xfffffe0025c9ffff
dependency: com.apple.driver.watchdog(1)[BEE7A0FC-B21D-32F4-8632-C669EA683887]@0xfffffe0028188000->0xfffffe002818bfff
dependency: com.apple.iokit.IOReportFamily(47)[789544EB-168A-39BF-9FAB-1D8E60EDF2EE]@0xfffffe002775c000->0xfffffe002775ffff
Β 
last started kext at 16176145919: com.softraid.driver.SoftRAID 6.0.3 (addr 0xfffffe0024598000, size 16384)
Β 

Β 

This post was modified 5 years ago by SoftRAID Support
 
Posted : 02/05/2021 3:03 pm
(@softraid-support)
Posts: 9197
Member Admin
Topic starter
 

@thierrycoopman

Send the system diagnose file using these steps.

Send the we transfer link to support at softRAID, referencing this URL of this page:

https://srforums.wpengine.com/big-sur-issues/big-sur-on-m1-machines-and-softraid-issues/paged/46/#post-9285

Β 

That will make it easier. (and keep your privacy)

Send the file to me via "wetransfer.com".
Instructions to send the System Diagnose file:

go to the url:
wetransfer.com
Click the button that says "I Agree".
Click the "Add your files" button and select the Sysdiagnose file.
Click the ... Button.
Select the "Get transfer link" button.
Click the large "Get a Link" button.
After a short period of time, the wetransfer site will give you a link.
Send that link to us.

 
Posted : 02/05/2021 10:11 pm
Page 45 / 59
Share:
close
open