Notifications
Clear all
Big Sur Issues
47
Posts
5
Users
0
Likes
2,417
Views
Here is the soft raid report you asked me to generate when it crashes.
Posted : 01/08/2021 8:23 pm
No clues yet. I am unfamiliar with this panic and there is nothing on the discussion forums at Apple. You can try the SoftRAID 6.1 beta, but I do not think it will make a difference. (We did make one driver change)
Might be worth a call to Apple. What I would do to save time is after next panic, paste this into terminal immediately after the restart, and have the file ready when you call Apple. They will want this after a panic for troubleshooting and it will save a lot of time. It will be a large 200MB file.
sudo sysdiagnose -f ~/Desktop/
They will also want you to try a "clean install". What I recommend before is deleting your old extensions with these terminal commands:
sudo rm -r /Library/Extensions/FTDIKext.kext
sudo rm -r /Library/Extensions/hp_fax_io.kext
sudo rm -r /Library/Extensions/hp_io_printerclassdriver_enabler.kext
sudo rm -r /Library/Extensions/SiLabsUSBDriver64.kext
sudo rm -r /Library/Extensions/XQD Memory Card.kext
sudo rm -r /Library/Extensions/EPSONUSBPrintClass.kext
sudo rm -r /Library/Extensions/JMicronATA.kext
sudo kmutil clear-staging
sudo kextcache -i /
Restart. Now you are ready in the case of the next panic, to save the system diagnostic and give a call to Apple. Let us know what information you get.
Posted : 02/08/2021 2:04 pm
I've tried many times to call Apple, that's a road that doesn't get me anywhere. What I do know is that the moment I remove the Softraid Drive Enclosure all my crashing stops. It's only when I plug that drive in that my crashing begins. No other hard drives trigger the problem.
I've tried a clean install 3 times now (once because my wife accidentally upgraded to the new beta OS). Each time the same problem exist, and again only when I plug in the OWC Raid enclosure. I was having similar issues on my i9 iMac, but over the updates you fixed my crashing, now it only happens on the M1. It appears I'm not the only person having this problem, has anyone else been able to figure out a solution?
I know the data cable is thunderbolt 3 and I believe the new M1 Mac mini uses thunderbolt 4. Could changing the cable fix anything, does data transfer differently over the cables?
Posted : 03/08/2021 7:59 am
Its not cables. Tb4 is essentially the same as TB3 cables. Since the "DART" crash appears to involve thunderbolt, your description makes logical sense of when it happens.
You are not the only one, but this is rare and weird. If you had time, you could try making your enclosure non RAID (Apple format), or RAID 0, where you could convert to Apple RAID and back for testing.
the problem is it is difficult to debug M1 machines. Getting a core dump to see what is actually crashing requires you have a second computer to capture the data with. If you do, I can send instructions. (It also requires hard wired ethernet, direct or over Thunderbolt, not over USB)
So unless we can create this in house (I have tried and never seen these crashes), we cannot do much except hope the M1 fixes this, or we get a customer who can get a core dump and work with us and Apple.
Posted : 03/08/2021 9:29 am
I have two computers, can I do a core dump with an i9 chip connected the m1 Mac. Or do I need two m1 Macs?
The challenge for me is that the drive contains 8 TB of data, I can't easily reformat this drive and try that. I would need a second drive to test this. I'm guessing you wouldn't send me a drive to test this on would you?
Posted : 03/08/2021 10:22 am
If the second is running Big Sur, yes you can. Any chance you can hard wire the two computers together with Ethernet? (they must be built in, which I am guessing the older has, but the newer, you need a Ethernet / Thunderbolt adapter, or a Thunderbolt dock with ethernet, not a USB/Ethernet adapter.
this process does not affect any data on computer 1 or 2. The question is whether you have ethernet "compatiblity".
Posted : 03/08/2021 3:42 pm
I can handle the ethernet portion of it. I have an adapter if I need, but both machines also have in built in. Can you send me detail instructions on what I need to do?
Posted : 03/08/2021 3:53 pm
Built-in is great. Let me get you instructions. If I cannot put them together today, it will be tomorrow.
Posted : 03/08/2021 5:04 pm
I pulled out a Thunderbolt 2 enclosure and put in two new drives. I tried doing a RAID 0 of these two 3TB drives. The system still crashed having this setup. I then initialized those drives and just had the enclosure mount the 3TB drive with no RAID configuration and so far almost 24 hours no crashes. It seems to be the moment I setup the RAID in any format it crashes.
My test I was hoping that since I've moved these drives over from Softraid 5 that setting up a fresh set of drives in VS 6 would fix this most random bug. It still exist, I haven't seen instructions on how to do the dump via ethernet yet.
My current solution, I just ordered a single 10TB drive. I'm going to use this inside one of the enclosures and skip the RAID protection for the time being. Hopefully giving you guys time to figure this out. At this point the crashing is causing so many productivity issues I just need to find a way around it.
At this time, I've tried two different enclosures, both have the same problem. I've tried plugging directly into the computer and via OWC thunderbolt hub. Also tried turning off bluetooth and running hard wired mouse and keyboard (you mentioned once that the during the crash the last activity it tried to do was the keyboard). Everything still crashes.
My one thought since this is so random, I do have backup blaze running on backing up the computer and the enclosure. Maybe something with this is causing a conflict? I've been doing this for years and didn't have problems until recently. My guess is at this point there must be some common 3rd party software interacting with your software. Maybe you can see what else other people are doing/running on their systems. Maybe there is a common element. If it's not backup blaze, is anyone else using a backup software that constantly scans your system for changes?
Posted : 12/08/2021 9:07 am
To get a Core Dump, you need another Modern computer, with hardware ethernet you can connect them with (must be Thunderbolt, or a Thunderbolt dock, USB does not work) Do you have this ability? If you can get us a core dump, can we supply your contact information to an Apple engineer? We have a engineering contact at Apple very interested in investigating this problem.
I do not think this is because of BackBlaze. There are no specific issues by Acronis for example, which does the same thing. Most likely this is a hardware issue somewhere.
Posted : 12/08/2021 9:35 am
I have two computers that have a dedicated ethernet port next to each other. I have an iMac and the Mac mini. One is intel and the other is M1 chip. If that's not a problem I can do this. I just need to know how.
Posted : 12/08/2021 9:38 am
Perfect!
Here are the first few pages from the Apple two machine debugging instructions:
Performing Two-Machine Debugging
The KDK supports the debugging of kernel-level code, such as kernel extensions, from a second Mac.
- The target device is the Mac that runs the code you want to debug. - The host device is the Mac that runs the debugger.
Identify Device Compatibility
On Apple silicon, perform two-machine debugging using your Mac’s built-in Ethernet ports.
On Intel-based Macs, perform two-machine debugging using your Mac’s built-in Ethernet ports, the Ethernet port on the Apple Thunderbolt display, or the Apple Thunderbolt to Gigabit Ethernet adapter. You may also use third-party Thunderbolt Ethernet adapters that support one of the following chipsets:
-
Broadcom C-IV
-
Aquantia AQC107/113
-
Intel 82574L
Note: You cannot perform two-machine debugging using USB Ethernet adapters or wireless networking on any Mac.
You must connect the host and target device to the same network, but there are no other restrictions on how the devices connect to that network.
Configure Apple silicon as a Target Device
Use the following steps to configure your Apple silicon as a target device for debugging.
Step 1: Modify the Security Configuration of Your Mac
Modify the security configuration of your system as follows:
1. Reboot your Mac in Recovery Mode.
2. Launch Terminal and run the following command to disable System Integrity Protection (SIP):
⁃ csrutil disable
3. If prompted to lower your system security to “permissive”, enter y to accept.
4. Reboot your Mac.
Step 2: Identify the Correct Ethernet Device
Run the ifconfig tool in Terminal to identify which Ethernet device your target device uses to connect to the network. In the following example, en1 is the Ethernet device connected to the network.
en0: flags=8963 mtu 1500
options=60
ether 32:00:13:er:19:e0
media: autoselect
status: inactive
en1: flags=8863 mtu 1500
options=10b
ether 40:6c:8f:5b:a2:96
inet6 fe80::426c:8fff:fe5b:a296%en2 prefixlen 64 scopeid 0x4
inet6 2620::1b07:114:426c:8fff:fe5b:a296 prefixlen 64 autoconf
inet6 2620::1b07:114:88d6:bbba:7ac9:b0a7 prefixlen 64 autoconf
temporary
inet 10.128.19.135 netmask 0xfffff800 broadcast 10.128.23.255
nd6 options=1
media: autoselect (1000baseT )
status: active
Step 3: Set the boot-args
Run the nvram tool in Terminal to add the following arguments to your target device’s boot- args key:
-
debug=0x44—Tells the kernel to wait for a debugger to attach to the device, when the kernel receives a non-maskable interrupt (NMI).
-
kdp_match_name=enX—Set the value of this key to the Ethernet device (en0, en1, etc.) identified in Step 2: Identify the Correct Ethernet Device.
-
wdt=-1—Disables watchdog monitoring. For example:
sudo nvram boot-args=“debug=0x44 kdp_match_name=en1 wdt=-1”Step 4: Reboot the Device
Upon reboot, you may connect to your target device from the host.
Configure an Intel-based Mac as a Target Device
Use the following steps to configure your target device for debugging.
Step 1: Modify the Security Configuration of Your Mac
Modify the security configuration of your system as follows:
1. Reboot your Mac in Recovery Mode.
2. If your device has the Apple T2 Security Chip, set the Secure Boot policy to “Medium
Security”.
3. Launch Terminal and run the following command to disable System Integrity Protection (SIP):
⁃ csrutil disable 4. Reboot your Mac.
Step 2: Identify the Correct Ethernet Device
Run the ifconfig tool in Terminal to identify which Ethernet device your target device uses to connect to the network. In the following example, en1 is the Ethernet device connected to the network.
en0: flags=8963 mtu 1500
options=60
ether 32:00:13:er:19:e0
media: autoselect
status: inactive
en1: flags=8863 mtu 1500
options=10b
ether 40:6c:8f:5b:a2:96
inet6 fe80::426c:8fff:fe5b:a296%en2 prefixlen 64 scopeid 0x4
inet6 2620::1b07:114:426c:8fff:fe5b:a296 prefixlen 64 autoconf
inet6 2620::1b07:114:88d6:bbba:7ac9:b0a7 prefixlen 64 autoconf
temporary
inet 10.128.19.135 netmask 0xfffff800 broadcast 10.128.23.255
nd6 options=1
media: autoselect (1000baseT )
status: active
Step 3: Set the boot-args
Run the nvram tool in Terminal to add the following arguments to your target device’s boot- args key:
-
debug=0x44—Tells the kernel to wait for a debugger to attach to the device, when the kernel receives a non-maskable interrupt (NMI).
-
kdp_match_name=enX—Set the value of this key to the Ethernet device (en0, en1, etc.) identified in Step 2: Identify the Correct Ethernet Device.
-
wdt=-1—Disables watchdog monitoring. For example:
sudo nvram boot-args=“debug=0x44 kdp_match_name=en1 wdt=-1”Step 4: Reboot the Device
Upon reboot, you may connect to your target device from the host.
Posted : 12/08/2021 9:55 am
When you get a panic, if the machine auto restarts, wait a few minutes (up to ten) and then use "go to folder" to go to:
/private/var/tmp/
If the machine hard hangs, then press the Power button for a full second and release. Then wait 10 minutes before restarting.
There should be a kernel panics folder in that directory. Let me know if not.
What we need is this, and a couple other items:
System diagnosis file, System Profiler and SoftRAID Tech Support file.
Create the System Diagnose file with this terminal command:
sudo sysdiagnose -f ~/Desktop/
Its best to create this file immediately after the crash. (It can be while you are waiting for the core dump to get created)
I can arrange a way for you to get this all to us, two of the files are quite large.
This post was modified 3 years ago by SoftRAID Support
Posted : 12/08/2021 10:01 am
I'm pretty tech savvy, but I do need to be pointed in the very absolute direction. I see that I need to download the Kernel Debug kit, when I go to the downloads there are multiple versions. Which version do I need to do?
Can you send me the link to apples support page that I should follow exactly? I'm sorry this way I know I am not doing something wrong.
Posted : 12/08/2021 10:04 am
I thought you could generate the core dump without, but let me get the URL for this. One minute
Posted : 12/08/2021 10:08 am
