Thunderbay 4 Mini a...
 
Notifications
Clear all

Thunderbay 4 Mini and Softraid 6.2 crashing M1 Max on Monterey

49 Posts
6 Users
1 Likes
1,892 Views
(@morgangold)
Posts: 6
Active Member
Topic starter
 

Running 6.2 and Monterey 12.0.1

Running SoftRaid and Thunderbay 4 Mini HAS worked.

But it's also crashed and restarted my laptop on an endless loop several times.

 

When I unplug the Thunderbay, the crashing stops.

 

Today, every time I try to plug the Thunderbay in, the computer begins to crash endlessly.

 

Attached a report from SoftRaid

 
Posted : 31/10/2021 4:05 pm
(@softraid-support)
Posts: 8006
Member Admin
 

Support file was not attached and I think the panic you reported is not connected here.

This appears to be the Thunderbolt bus crash we are working on.

We are swapping out a system with a user with this problem, so we have an example we can bring into Apple engineering.

If you remove exactly one disk to your volume from your enclosure, I suspect the system does not crash, correct?

 
Posted : 31/10/2021 6:44 pm
(@morgangold)
Posts: 6
Active Member
Topic starter
 

I haven’t tried. This is my first time with a RAID system.

Is there any risk to the data on the disks removing the single drive?

 

Attached the file below.

 
Posted : 31/10/2021 7:17 pm
(@softraid-support)
Posts: 8006
Member Admin
 

@morgangold

Removing the disk means you do not have "parity" protection, but there is no actual risk to the data.

Make sure your backups are up to date (or update them!)

If it lets you use your system until we can all get this figured out, though, it gets you past the worst.

 
Posted : 31/10/2021 10:29 pm
(@morgangold)
Posts: 6
Active Member
Topic starter
 

Just as an additional data point, I attempted to use the RAID on my M1 Air running Monterey.

As soon as I updated SoftRaid to 6.2 and had the Thunderbay Mini connected, the endless crashing began again.

 
Posted : 01/11/2021 5:50 pm
(@softraid-support)
Posts: 8006
Member Admin
 

@morgangold

Please remove one drive, until we can figure this out. I expect we will get an example failing computer this weekend.

 
Posted : 02/11/2021 12:05 am
(@morgangold)
Posts: 6
Active Member
Topic starter
 

I can confirm that if I don't have my laptop plugged into its power supply, the Thunderbay 4 Mini mounts (with all 4 drives), works and does NOT crash my system.

 
Posted : 13/11/2021 11:23 am
(@softraid-support)
Posts: 8006
Member Admin
 

@morgangold

We received a users system and have started testing. So far, I can confirm this is not caused by the enclosure. It is a System problem. We are testing multiple clean macOS installs next. (that is time consuming) So far, it appears to be a problem in the specific System folder on the host machine.

When we have enough information we will be working with Apple on getting this fixed.

 
Posted : 13/11/2021 11:36 am
(@jwbuckl)
Posts: 24
Eminent Member
 

 

Screen Shot 2021 11 15 at 1.37.38 AM

@softraid-support

I don't know if this helps, but through Terminal I was able to screenshot this "Incompatible architecture: Binary is for x86_64, but needed arch arm64e". See attached. Running M1 Max with latest Monterrey and Thunderbay 8. Looping crashes.

 
Posted : 15/11/2021 10:25 am
(@softraid-support)
Posts: 8006
Member Admin
 

@jwbuckl

Over the weekend, I identified the trigger, not the cause. If you change your RAID level to RAID 4, the crashes will go away.

Also, a clean system install will fix this, but since the problem is clearly caused by something inside macOS, its possible it is a third party app triggering this, rather than a setting or something in macoS. A third party installation would most explain why we see such a low percentage of users with this issue. Its too early to tell, but now we have the hardware to dig deep.

this will be a high priority to get the information we are learning to Apple engineering, so a fix (from us or Apple) can be identified. But it is much more promising now.

 
Posted : 15/11/2021 12:46 pm
jwbuckl reacted
(@jwbuckl)
Posts: 24
Eminent Member
 

@softraid-support. Here is the kernel panic report in the event that it helps you figure stuff out.

panic(cpu 1 caller 0xfffffe001f12ac98): busy timeout[0], (60s): 'Untitled 4' @IOService.cpp:5520

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 21A559

Kernel version: Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:01 PDT 2021; root:xnu-8019.41.5~1/RELEASE_ARM64_T6000

Fileset Kernelcache UUID: 3B2CA3833A09A383D66FB36667ED9CBF

Kernel UUID: 67BCB41B-BAA4-3634-8E51-B0210457E324

iBoot version: iBoot-7429.41.5

secure boot?: YES

Paniclog version: 13

    <snip>

 

last started kext at 1041546149: com.boxcryptor.BCFS.filesystems.bcfs     2081.20 (addr 0xfffffe001df5c000, size 6240)

loaded kexts:

com.boxcryptor.BCFS.filesystems.bcfs          2081.20

com.softraid.driver.SoftRAID 6.2

<snipped to save space>

This post was modified 2 years ago by SoftRAID Support
 
Posted : 16/11/2021 11:48 pm
(@softraid-support)
Posts: 8006
Member Admin
 

@jwbuckl

this is a totally different panic. When does this occur?
this appears to be caused by boxcryptor, it is in the backtrace, and the last kernel extension executed.

 

This crash is unrelated to the M1 problem we have been tracking.

 
Posted : 17/11/2021 12:00 am
(@jwbuckl)
Posts: 24
Eminent Member
 

@softraid-support. You are right looking at it. I just replicated the same results. Truncated panic report below. Odd thing is that Boxcryptor is not on or touch any data on the Thunderbay. Also odd is that this exact same software setup works perfectly on my Intel-based Macbook Pro. I mirrored the laptops complete with Boxcryptor, Softraid 6.2 etc. What I can attempt to do is temporarily remove Boxcryptor from the M1 Max MacBook Pro and retest. This will be quite involved, unfortunately.

panic(cpu 3 caller 0xfffffe00110739e4): Kernel data abort. at pc 0xfffffe0012ae05cc, lr 0x65bc7e0012ad3b80 (saved state: 0xfffffe70e179b9e0)
 x0:  0xfffffe150e82c2a0 x1:  0x0000000000000000  x2:  0x0000000000000010  x3:  0xfffffe70e179bd8c
 x4:  0x9ca9fe0012ad3b44 x5:  0xfffffe0013d0b818  x6:  0x0000000000000065  x7:  0x00000000000007e0
 x8:  0xfffffe150e6c4480 x9:  0xfffffe1511d34a00  x10: 0x0000000000000000  x11: 0x0000000000000001
 x12: 0x0000000000400001 x13: 0x00000000ffcfffff  x14: 0x000000000000000f  x15: 0x00000000ffffffc9
 x16: 0x1084fe0013d0b818 x17: 0x00000000000009f0  x18: 0x0000000000000000  x19: 0xfffffe70e179bd8c
 x20: 0x0000000000000000 x21: 0x0000000000000010  x22: 0xfffffe150e82c2a0  x23: 0x0000000000000000
 x24: 0xfffffe00143efb20 x25: 0xfffffe00143efb24  x26: 0xcda1fe150e62b7f0  x27: 0xfffffe150e62b808
 x28: 0x20c49ba5e353f7cf fp:  0xfffffe70e179bd70  lr:  0x65bc7e0012ad3b80  sp:  0xfffffe70e179bd30
 pc:  0xfffffe0012ae05cc cpsr: 0x60401208         esr: 0x96000004          far: 0x0000000000000030
 
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 21A559
Kernel version: Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:01 PDT 2021; root:xnu-8019.41.5~1/RELEASE_ARM64_T6000
Fileset Kernelcache UUID: 3B2CA3833A09A383D66FB36667ED9CBF
Kernel UUID: 67BCB41B-BAA4-3634-8E51-B0210457E324
iBoot version: iBoot-7429.41.5
secure boot?: YES
Paniclog version: 13
KernelCache slide: 0x0000000008f08000
KernelCache base:  0xfffffe000ff0c000
Kernel slide:      0x0000000009730000
Kernel text base:  0xfffffe0010734000
Kernel text exec slide: 0x0000000009818000
Kernel text exec base:  0xfffffe001081c000
mach_absolute_time: 0x3112a1b67
Epoch Time:        sec       usec
  Boot    : 0x61948dd0 0x00026b69
  Sleep   : 0x00000000 0x00000000
  Wake    : 0x00000000 0x00000000
  Calendar: 0x61948fee 0x0006a66a
 
Zone info:
Foreign   : 0xfffffe0017c14000 - 0xfffffe0017c28000
Native    : 0xfffffe100071c000 - 0xfffffe300071c000
Readonly  : 0 - 0
Metadata  : 0xfffffe7c88394000 - 0xfffffe7c94338000
Bitmaps   : 0xfffffe7c94338000 - 0xfffffe7cabd54000
CORE 0 PVH locks held: None
CORE 1 PVH locks held: None
CORE 2 PVH locks held: None
CORE 3 PVH locks held: None
CORE 4 PVH locks held: None
CORE 5 PVH locks held: None
CORE 6 PVH locks held: None
CORE 7 PVH locks held: None
CORE 8 PVH locks held: None
CORE 9 PVH locks held: None
CORE 0: PC=0xfffffe00108a2c6c, LR=0xfffffe00108a2c6c, FP=0xfffffe6032bd3ef0
CORE 1: PC=0x000000018c3fb150, LR=0x000000018ef853e8, FP=0x000000016ba29430
CORE 2: PC=0xfffffe0010dbd180, LR=0xfffffe0010dbd0c4, FP=0xfffffe603855bcb0
CORE 3 is the one that panicked. Check the full backtrace for details.
CORE 4: PC=0xfffffe0010999d60, LR=0xfffffe0010999f1c, FP=0xfffffe603801be80
CORE 5: PC=0xfffffe00108a2c70, LR=0xfffffe00108a2c6c, FP=0xfffffe6032c53ef0
CORE 6: PC=0xfffffe00108a2c6c, LR=0xfffffe00108a2c6c, FP=0xfffffe70e1b9bef0
CORE 7: PC=0xfffffe00108a2c6c, LR=0xfffffe00108a2c6c, FP=0xfffffe61105f3ef0
CORE 8: PC=0xfffffe00108a2c6c, LR=0xfffffe00108a2c6c, FP=0xfffffe70e1cdbef0
CORE 9: PC=0xfffffe00108a2c6c, LR=0xfffffe00108a2c6c, FP=0xfffffe6032bc3ef0
Panicked task 0xfffffe150def06a8: 0 pages, 632 threads: pid 0: kernel_task
Panicked thread: 0xfffffe1515d08d10, backtrace: 0xfffffe70e179b090, tid: 15459
 lr: 0xfffffe001086e488  fp: 0xfffffe70e179b100
 lr: 0xfffffe001086e158  fp: 0xfffffe70e179b170
 lr: 0xfffffe00109aa558  fp: 0xfffffe70e179b190
 lr: 0xfffffe001099d2d4  fp: 0xfffffe70e179b210
 lr: 0xfffffe001099ac9c  fp: 0xfffffe70e179b2d0
 lr: 0xfffffe00108237f8  fp: 0xfffffe70e179b2e0
 lr: 0xfffffe001086ddcc  fp: 0xfffffe70e179b680
 lr: 0xfffffe001086ddcc  fp: 0xfffffe70e179b6f0
 lr: 0xfffffe001106c748  fp: 0xfffffe70e179b710
 lr: 0xfffffe00110739e4  fp: 0xfffffe70e179b890
 lr: 0xfffffe001099d0cc  fp: 0xfffffe70e179b900
 lr: 0xfffffe001099b02c  fp: 0xfffffe70e179b9c0
 lr: 0xfffffe00108237f8  fp: 0xfffffe70e179b9d0
 lr: 0xfffffe0012ad3b80  fp: 0xfffffe70e179bd70
 lr: 0xfffffe0012ad3b80  fp: 0xfffffe70e179bda0
 lr: 0xfffffe0011fb8bb4  fp: 0xfffffe70e179be10
 lr: 0xfffffe0011fb8aac  fp: 0xfffffe70e179be50
 lr: 0xfffffe0012ce5e64  fp: 0xfffffe70e179bea0
 lr: 0xfffffe0012ce7e1c  fp: 0xfffffe70e179bf20
 lr: 0xfffffe001082ce78  fp: 0x0000000000000000
      Kernel Extensions in backtrace:
         com.apple.iokit.IOPCIFamily(2.9)[38E6DC01-BDA7-38F0-A6AF-C1FEAA322FB4]@0xfffffe0012acc2d0->0xfffffe0012ae8937
         com.apple.iokit.IOThunderboltFamily(9.3.2)[E896F277-30A1-3DDD-8FBE-AE396CD8EEBA]@0xfffffe0012be74c0->0xfffffe0012d02ca7
            dependency: com.apple.driver.AppleSMC(3.1.9)[97ECDD11-21A9-3B18-8EF5-F1A228CED252]@0xfffffe0011cf0230->0xfffffe0011d1fe33
         com.apple.driver.AppleThunderboltPCIUpAdapter(4.1.1)[061ECCC3-BAA4-3438-BB38-934954001C4B]@0xfffffe0011fa96e0->0xfffffe0011fc2133
            dependency: com.apple.driver.AppleThunderboltPCIDownAdapter(4.1.1)[9FE7E8B7-5511-398A-AB30-1FAE4578A84A]@0xfffffe0011fa4270->0xfffffe0011fa96d3
            dependency: com.apple.iokit.IOPCIFamily(2.9)[38E6DC01-BDA7-38F0-A6AF-C1FEAA322FB4]@0xfffffe0012acc2d0->0xfffffe0012ae8937
            dependency: com.apple.iokit.IOThunderboltFamily(9.3.2)[E896F277-30A1-3DDD-8FBE-AE396CD8EEBA]@0xfffffe0012be74c0->0xfffffe0012d02ca7
 
last started kext at 1883915797: com.boxcryptor.BCFS.filesystems.bcfs 2081.20 (addr 0xfffffe000fd90000, size 6240)
loaded kexts:
com.boxcryptor.BCFS.filesystems.bcfs 2081.20
com.softraid.driver.SoftRAID 6.2
com.apple.filesystems.autofs 3.0
com.apple.fsplaceholder 1.14.1
com.apple.fileutil 20.036.15
com.apple.UVCService 1
com.apple.driver.AppleAHCIPort 351
com.apple.driver.AppleFWOHCI 5.7.4
com.apple.iokit.AppleBCM5701Ethernet 11.0.0
com.apple.driver.AppleBiometricServices 1
com.apple.driver.CoreKDL 1

 

 
Posted : 17/11/2021 12:23 am
(@jwbuckl)
Posts: 24
Eminent Member
 

@softraid-support. The panic is now happening on an Apple driver rather than Boxcryptor. Why can't we attach PDFs for you in this forum? Sorry to dump so much data here.

panic(cpu 2 caller 0xfffffe0018e379e4): Kernel data abort. at pc 0xfffffe001a8a45cc, lr 0xee907e001a897b80 (saved state: 0xfffffe60329c39e0)
 x0:  0xfffffe150e104620 x1:  0x0000000000000000  x2:  0x0000000000000010  x3:  0xfffffe60329c3d8c
 x4:  0x7ae5fe001a897b44 x5:  0xfffffe001bacf818  x6:  0x0000000000000065  x7:  0x0000000000000360
 x8:  0xfffffe150e084360 x9:  0xfffffe150ee3ea00  x10: 0x0000000000000000  x11: 0x0000000000000001
 x12: 0x0000000000400001 x13: 0x00000000ffcfffff  x14: 0x000000000000000f  x15: 0x00000000ffffffc9
 x16: 0x1084fe001bacf818 x17: 0x00000000000009f0  x18: 0x0000000000000000  x19: 0xfffffe60329c3d8c
 x20: 0x0000000000000000 x21: 0x0000000000000010  x22: 0xfffffe150e104620  x23: 0x0000000000000000
 x24: 0xfffffe001c1b3b20 x25: 0xfffffe001c1b3b24  x26: 0xcda1fe150e02f200  x27: 0xfffffe150e02f218
 x28: 0x20c49ba5e353f7cf fp:  0xfffffe60329c3d70  lr:  0xee907e001a897b80  sp:  0xfffffe60329c3d30
 pc:  0xfffffe001a8a45cc cpsr: 0x60401208         esr: 0x96000005          far: 0x0000000000000030
 
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 21A559
Kernel version: Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:01 PDT 2021; root:xnu-8019.41.5~1/RELEASE_ARM64_T6000
Fileset Kernelcache UUID: 3B2CA3833A09A383D66FB36667ED9CBF
Kernel UUID: 67BCB41B-BAA4-3634-8E51-B0210457E324
iBoot version: iBoot-7429.41.5
secure boot?: YES
Paniclog version: 13
KernelCache slide: 0x0000000010ccc000
KernelCache base:  0xfffffe0017cd0000
Kernel slide:      0x00000000114f4000
Kernel text base:  0xfffffe00184f8000
Kernel text exec slide: 0x00000000115dc000
Kernel text exec base:  0xfffffe00185e0000
mach_absolute_time: 0x2881c9946
Epoch Time:        sec       usec
  Boot    : 0x6194a56d 0x000c6723
  Sleep   : 0x00000000 0x00000000
  Wake    : 0x00000000 0x00000000
  Calendar: 0x6194a72c 0x00047054
 
Zone info:
Foreign   : 0xfffffe001fc14000 - 0xfffffe001fc28000
Native    : 0xfffffe1000038000 - 0xfffffe3000038000
Readonly  : 0 - 0
Metadata  : 0xfffffe886a824000 - 0xfffffe88767a8000
Bitmaps   : 0xfffffe88767a8000 - 0xfffffe888e1c8000
CORE 0 PVH locks held: None
CORE 1 PVH locks held: None
CORE 2 PVH locks held: None
CORE 3 PVH locks held: None
CORE 4 PVH locks held: None
CORE 5 PVH locks held: None
CORE 6 PVH locks held: None
CORE 7 PVH locks held: None
CORE 8 PVH locks held: None
CORE 9 PVH locks held: None
CORE 0: PC=0x00000001c0960d94, LR=0x00000001c0941f74, FP=0x000000016d8e2390
CORE 1: PC=0xfffffe001889802c, LR=0xfffffe001889802c, FP=0xfffffe60fc5eb510
CORE 2 is the one that panicked. Check the full backtrace for details.
CORE 3: PC=0xfffffe0018666c70, LR=0xfffffe0018666c6c, FP=0xfffffe6032983ef0
CORE 4: PC=0xfffffe0018666c70, LR=0xfffffe0018666c6c, FP=0xfffffe603843bef0
CORE 5: PC=0xfffffe0018666c70, LR=0xfffffe0018666c6c, FP=0xfffffe611101bef0
CORE 6: PC=0xfffffe0018666c70, LR=0xfffffe0018666c6c, FP=0xfffffe60ff9f3ef0
CORE 7: PC=0xfffffe0018666c70, LR=0xfffffe0018666c6c, FP=0xfffffe60d4dfbef0
CORE 8: PC=0xfffffe0018666c6c, LR=0xfffffe0018666c6c, FP=0xfffffe611051bef0
CORE 9: PC=0xfffffe0018666c6c, LR=0xfffffe0018666c6c, FP=0xfffffe80acbf3ef0
Panicked task 0xfffffe150d7e86a8: 0 pages, 632 threads: pid 0: kernel_task
Panicked thread: 0xfffffe1517f5c150, backtrace: 0xfffffe60329c3090, tid: 14997
 lr: 0xfffffe0018632488  fp: 0xfffffe60329c3100
 lr: 0xfffffe0018632158  fp: 0xfffffe60329c3170
 lr: 0xfffffe001876e558  fp: 0xfffffe60329c3190
 lr: 0xfffffe00187612d4  fp: 0xfffffe60329c3210
 lr: 0xfffffe001875ec9c  fp: 0xfffffe60329c32d0
 lr: 0xfffffe00185e77f8  fp: 0xfffffe60329c32e0
 lr: 0xfffffe0018631dcc  fp: 0xfffffe60329c3680
 lr: 0xfffffe0018631dcc  fp: 0xfffffe60329c36f0
 lr: 0xfffffe0018e30748  fp: 0xfffffe60329c3710
 lr: 0xfffffe0018e379e4  fp: 0xfffffe60329c3890
 lr: 0xfffffe00187610cc  fp: 0xfffffe60329c3900
 lr: 0xfffffe001875f02c  fp: 0xfffffe60329c39c0
 lr: 0xfffffe00185e77f8  fp: 0xfffffe60329c39d0
 lr: 0xfffffe001a897b80  fp: 0xfffffe60329c3d70
 lr: 0xfffffe001a897b80  fp: 0xfffffe60329c3da0
 lr: 0xfffffe0019d7cbb4  fp: 0xfffffe60329c3e10
 lr: 0xfffffe0019d7caac  fp: 0xfffffe60329c3e50
 lr: 0xfffffe001aaa9e64  fp: 0xfffffe60329c3ea0
 lr: 0xfffffe001aaabe1c  fp: 0xfffffe60329c3f20
 lr: 0xfffffe00185f0e78  fp: 0x0000000000000000
      Kernel Extensions in backtrace:
         com.apple.iokit.IOPCIFamily(2.9)[38E6DC01-BDA7-38F0-A6AF-C1FEAA322FB4]@0xfffffe001a8902d0->0xfffffe001a8ac937
         com.apple.iokit.IOThunderboltFamily(9.3.2)[E896F277-30A1-3DDD-8FBE-AE396CD8EEBA]@0xfffffe001a9ab4c0->0xfffffe001aac6ca7
            dependency: com.apple.driver.AppleSMC(3.1.9)[97ECDD11-21A9-3B18-8EF5-F1A228CED252]@0xfffffe0019ab4230->0xfffffe0019ae3e33
         com.apple.driver.AppleThunderboltPCIUpAdapter(4.1.1)[061ECCC3-BAA4-3438-BB38-934954001C4B]@0xfffffe0019d6d6e0->0xfffffe0019d86133
            dependency: com.apple.driver.AppleThunderboltPCIDownAdapter(4.1.1)[9FE7E8B7-5511-398A-AB30-1FAE4578A84A]@0xfffffe0019d68270->0xfffffe0019d6d6d3
            dependency: com.apple.iokit.IOPCIFamily(2.9)[38E6DC01-BDA7-38F0-A6AF-C1FEAA322FB4]@0xfffffe001a8902d0->0xfffffe001a8ac937
            dependency: com.apple.iokit.IOThunderboltFamily(9.3.2)[E896F277-30A1-3DDD-8FBE-AE396CD8EEBA]@0xfffffe001a9ab4c0->0xfffffe001aac6ca7
 
last started kext at 1297874182: com.apple.driver.driverkit.serial 6.0.0 (addr 0xfffffe00183d71a0, size 3432)
loaded kexts:
com.softraid.driver.SoftRAID 6.2
com.apple.filesystems.autofs 3.0
com.apple.fsplaceholder 1.14.1
com.apple.fileutil 20.036.15
com.apple.UVCService 1
com.apple.driver.AppleAHCIPort 351
com.apple.driver.AppleFWOHCI 5.7.4
com.apple.iokit.AppleBCM5701Ethernet 11.0.0
com.apple.driver.AppleBiometricServices 1
com.apple.driver.CoreKDL 1
com.apple.driver.AppleTopCaseHIDEventDriver 5010.1
com.apple.driver.BCMWLANFirmware4387.Hashstore 1
com.apple.driver.SEPHibernation 1
com.apple.driver.DiskImages.ReadWriteDiskImage 493.0.0
com.apple.driver.DiskImages.UDIFDiskImage 493.0.0
com.apple.driver.DiskImages.RAMBackingStore 493.0.0
com.apple.driver.DiskImages.FileBackingStore 493.0.0
com.apple.filesystems.apfs 1933.41.2
com.apple.driver.AppleUSBDeviceNCM 5.0.0
com.apple.driver.AppleThunderboltIP 4.0.3
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.nke.l2tp 1.9
com.apple.filesystems.tmpfs 1
com.apple.filesystems.lifs 1
com.apple.IOTextEncryptionFamily 1.0.0
com.apple.filesystems.hfs.kext 582.40.4
com.apple.security.BootPolicy 1

 

 
Posted : 17/11/2021 2:01 am
(@softraid-support)
Posts: 8006
Member Admin
 

@jwbuckl

In the Apple discussions there is a similar panic, but not caused by boxcryptor, caused by Symantec

https://discussions.apple.com/thread/253180195

 

Maybe it is worth posting this panic to the discussion forums, but recently the quality of helpers on the forums seem to have dropped dramatically.

 
Posted : 17/11/2021 2:03 am
Page 1 / 4
Share:
close
open