Big Sur on M1 machi...
 
Notifications
Clear all

[Sticky] Big Sur on M1 machines and SoftRAID issues

882 Posts
79 Users
39 Likes
50 K Views
(@softraid-support)
Posts: 8051
Member Admin
Topic starter
 

@majortom67

Lets get the Sysdiagnosis file and if Apple is willing to work on this, they can help with the core dump, perhaps.

 

sudo sysdiagnose -f ~/Desktop/

and a fresh System Profile report and SoftRAID tech support file.

 

Get them to me with these instructions:

Post the link, I won't publish it.

go to the url:
wetransfer.com
Click the button that says "I Agree".
Click the "Add your files" button and select the Sysdiagnose file and other files.
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 here.

 

Lets see if we can get assistance on the core dump for you.

 

This post was modified 3 years ago by SoftRAID Support
 
Posted : 19/08/2021 10:41 am
(@majortom67)
Posts: 39
Eminent Member
 

Hi.

I apologize for the long wait (health problems and a serious mom's burn while cooking).

 - - -

I am able to replicate the kext crash but can't get the Core Dump file. I'm having a couple of doubts:

1) after pressing the power button in order to get the CD file I get the window with the "Restart/Whut Down/Sleep/Undo" buttons although disabled in the startup preferences. Is this correct? Is the CD file request going on?

2) is the Terminal situation (in picture) correct? I mean: is that a sort of (correct) wait for something (CD file) or is the command wrong (the eth port  - en10 - is correct) and should I have an exit?

https://ibb.co/DkjpVM6

All other crash logs are ready to be sent via We Transfer.

Thanks

Simon

 

This post was modified 3 years ago by majortom67
 
Posted : 22/08/2021 11:35 am
(@softraid-support)
Posts: 8051
Member Admin
Topic starter
 

@majortom67

At least send me the rest. We can see what we can do. the terminal command appears correct. If you are getting the restart options screen, maybe holding the button too long.

If you have the crash log, system diagnose, system report and SoftRAID support file, do this:

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 support at softraid. (or you can post the link here and I will delete it from the post)

 
Posted : 22/08/2021 12:52 pm
(@majortom67)
Posts: 39
Eminent Member
 

I found I site that explanes how to get the Core Dump and, regardless the fact that target machine and source machine are inverted also other operations and Xcode are nedeed. But maybe Apple's engineer can help us.

But, please, assuming you're procedure is enough, clarify me if the target machine (the one that collects the CD as per your instructions) must be restarted after changing the nvram boot options. If yes, do I just close the Terminal as in picture and restart? I may try once again before sending the data I already collected (642 mbytes).

Thanks Simon

 
Posted : 22/08/2021 1:19 pm
(@softraid-support)
Posts: 8051
Member Admin
Topic starter
 

@majortom67

Yes you need to restart. Then the NVRAM is set.

Send me the link to what you have and we can get this started. thanks!

 
Posted : 22/08/2021 6:42 pm
(@majortom67)
Posts: 39
Eminent Member
 

Here it is:

 

SimonV

This post was modified 3 years ago by SoftRAID Support
 
Posted : 22/08/2021 11:24 pm
(@softraid-support)
Posts: 8051
Member Admin
Topic starter
 

@majortom67

Can you also upload (the same way is great):

System Profile report

SoftRAID support file (new one)

A panic log

So I have it all in one location, to send to Apple.  thanks!

 
Posted : 23/08/2021 10:49 am
(@majortom67)
Posts: 39
Eminent Member
 

Following (next post) is a complete set of NEW crash logs as a tried a different way on the web without success (so, no Core Dump). You can then trash the previous system diagnose I sent. BTW, with a different USB-C to USB-C cable everything works fine. Are we sure it's a sw problem?

Thanks

Simon

 

 

 
Posted : 23/08/2021 11:11 am
(@majortom67)
Posts: 39
Eminent Member
 

Here it is.

Simon

 

 

 

This post was modified 3 years ago by SoftRAID Support
 
Posted : 23/08/2021 11:13 am
(@softraid-support)
Posts: 8051
Member Admin
Topic starter
 

@majortom67

 

If I get you a shipping label, can you send me the other cable? I would be interested in testing it. Are you in the USA?

 
Posted : 23/08/2021 1:40 pm
(@majortom67)
Posts: 39
Eminent Member
 

Unfortunately I don't have anymore shipping labels (as unfortunately I live in Italy). I can just say that:

1) this has an "MD" styled printing on one connector and works. You can find it on Amazon under the brand "Acagia" (or "Agiaca"): https://ibb.co/0tGrVwH

2) this, as you can see, is an ANKER branded and crashes the sys: https://ibb.co/2qRsQ8H

3) a third cable is branded AWM E 301195 Style 2725 and works.

4) a "3" (or similar greek letter - "Omega"?) branded cable that also works: https://ibb.co/Kj3Gkgp

Therefore looks that at least a cable is faulty or not TB3 completely compliant.

I also liked to have the possibility to check the cables' EFFECTIVE speed with CL!ng as I did in the past with an external GPU. Unfortunately CL!ing doesn't recognize neither the Terramaster RAID box nor my external GPU box with an AMD 470 inside. I can only remember that cable nr. 4 (strange branded) was fully running at 40 Gbps while another cable (not sure nr. 2 or nr. 3) was running at just 30 Gbps. Just curious to see if a speed different than 40 Gbps as a TB3 cable should be, could be involved - at least-  in my problem.

Simon

 

This post was modified 3 years ago by majortom67
 
Posted : 23/08/2021 3:30 pm
(@majortom67)
Posts: 39
Eminent Member
 

Had an idea know (while moving for night sleep - almost 11 pm here): if interested I can test those cables' speed with my mbpro 2018 tomorrow. As an Intel machine, can work with the eGPU. Assuming latest CL!ng version works with eGPUs like previous version.

Simon

 
Posted : 23/08/2021 3:46 pm
(@softraid-support)
Posts: 8051
Member Admin
Topic starter
 

@majortom67

Yes I would be looking forward to results.

 
Posted : 23/08/2021 4:52 pm
(@majortom67)
Posts: 39
Eminent Member
 

Here are the results:

(MBPro 2018 4TB3 - Mac OS 11.5.2 - Intel)

- MD/Acagia (or Agiaca): 35/36 Gbit/sec - circa 17/18 Gbit/sec per channel -> OK
- AWM: "peripheral not recognized" (eGPU) -> NOT OK
- "Omega": 35/36 Gbit/sec - circa 17/18 Gbit/sec per channel -> OK
- AMKER: 35/36 Gbit/sec - circa 8 Gbit/sec BUT host-to-device / circa 12 Gbit/sec device-to-host = 20 Gbit/sec -> ???

Therefore:

- the AMKER cable crashes the system (M1 Macmini) but works fine with the eGPU and the benchmarks gives odd results

- the AWM cable works fine with the RAID (M1 Macmini) but doesn't work with the eGPU (MBPro 2018 4TB3).

All cables have been bought as per high quality USB-C standard.

HTH - Simon

(In my experience, BTW, USB-C cables longer than 50 cm are not fine. (all cables here are 50 cm or less)).

 

 

This post was modified 3 years ago 3 times by majortom67
 
Posted : 24/08/2021 5:01 am
(@softraid-support)
Posts: 8051
Member Admin
Topic starter
 

@majortom67

I will see if I can get approval to purchase any of these. We will report this to Apple, also.

 
Posted : 24/08/2021 10:23 am
Page 57 / 59
Share:
close
open