Kernel panic reboot once a day or once every few days

I do not see the cause of the panics...
 "panicString" : "panic(cpu 7 caller 0xfffffe002eaae574): os_refcnt: overflow (rc=0xfffffe24d5fb71f0) @refcnt.c:71

CORE 7 is the one that panicked. Check the full backtrace for details.
Compressor Info: 1% of compressed pages limit (OK) and 8% of segments limit (OK) with 0 swapfiles and OK swap space
Panicked task 0xfffffe200c33dd80: 8694 pages, 11 threads: pid 40656: smbd

There are a few reports of this panic (search MacOS os_refcnt: overflow), but nothing I can see as a cause. If you have Apple support, see if they know anything, although I know they can be pretty sparse with information. I do not think SoftRAID is involved.

7?

in the my log i see

panic(cpu 1 caller 0xfffffe001f75e574): os_refcnt: overflow (rc=0xfffffe209d3035e0) @refcnt.c:71

CORE 1 is the one that panicked. Check the full backtrace for details.

panic(cpu 1 caller 0xfffffe001f75e574): os_refcnt: overflow (rc=0xfffffe209d3035e0) @refcnt.c:71
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 24B83
Kernel version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:05:14 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T8103
Fileset Kernelcache UUID: 22D9AC632B9EAC2B827A76C207589E9B
Kernel UUID: DE9B89B9-56BA-3C0E-8CEF-091C3439CFC2
Boot session UUID: 1291063D-2A7F-4DDA-906E-88F527082983
iBoot version: iBoot-11881.41.5
secure boot?: YES
roots installed: 0
Paniclog version: 14
KernelCache slide: 0x0000000016800000
KernelCache base: 0xfffffe001d804000
Kernel slide: 0x0000000016808000
Kernel text base: 0xfffffe001d80c000
Kernel text exec slide: 0x0000000017e88000
Kernel text exec base: 0xfffffe001ee8c000
mach_absolute_time: 0x2cab39649ba
Epoch Time: sec usec
Boot : 0x672ccbd4 0x000098fc
Sleep : 0x00000000 0x00000000
Wake : 0x00000000 0x00000000
Calendar: 0x672ebf6b 0x00057b0e

Zone info:
Zone map: 0xfffffe1a35eb0000 - 0xfffffe3a35eb0000
. VM : 0xfffffe1a35eb0000 - 0xfffffe1f02b7c000
. RO : 0xfffffe1f02b7c000 - 0xfffffe209c514000
. GEN0 : 0xfffffe209c514000 - 0xfffffe25691e0000
. GEN1 : 0xfffffe25691e0000 - 0xfffffe2a35eac000
. GEN2 : 0xfffffe2a35eac000 - 0xfffffe2f02b78000
. GEN3 : 0xfffffe2f02b78000 - 0xfffffe33cf844000
. DATA : 0xfffffe33cf844000 - 0xfffffe3a35eb0000
Metadata: 0xfffffe100c250000 - 0xfffffe1014250000
Bitmaps : 0xfffffe1014250000 - 0xfffffe101705c000
Extra : 0 - 0

CORE 0 recently retired instr at 0xfffffe001f04adb0
CORE 1 recently retired instr at 0xfffffe001f0495fc
CORE 2 recently retired instr at 0xfffffe001f04adb0
CORE 3 recently retired instr at 0xfffffe001f04ada8
CORE 4 recently retired instr at 0xfffffe001f04adb0
CORE 5 recently retired instr at 0xfffffe001f04adb0
CORE 6 recently retired instr at 0xfffffe001f04adb0
CORE 7 recently retired instr at 0xfffffe001f04adb0
TPIDRx_ELy = {1: 0xfffffe2a36e65800 0: 0x0000000000000001 0ro: 0x000000016d9cf0e0 }
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 0: PC=0xfffffe001ef2658c, LR=0xfffffe001ef2658c, FP=0xfffffe3a37693ed0
CORE 1 is the one that panicked. Check the full backtrace for details.
CORE 2: PC=0xfffffe001ef2658c, LR=0xfffffe001ef2658c, FP=0xfffffe3a3607fed0
CORE 3: PC=0x0000000104cdb2b0, LR=0x0000000104cdcc08, FP=0x000000016df42980
CORE 4: PC=0xfffffe001ef2658c, LR=0xfffffe001ef2658c, FP=0xfffffe3a379e3ed0
CORE 5: PC=0xfffffe001ef2658c, LR=0xfffffe001ef2658c, FP=0xfffffe3a37d97ed0
CORE 6: PC=0xfffffe001ef2658c, LR=0xfffffe001ef2658c, FP=0xfffffe3a36e53ed0
CORE 7: PC=0xfffffe001ef2658c, LR=0xfffffe001ef2658c, FP=0xfffffe3a374a7ed0
Compressor Info: 0% of compressed pages limit (OK) and 8% of segments limit (OK) with 0 swapfiles and OK swap space
Panicked task 0xfffffe33ce228950: 2125 pages, 5 threads: pid 663: smbd
Panicked thread: 0xfffffe2a36e65800, backtrace: 0xfffffe3a3772f760, tid: 5288495
lr: 0xfffffe001eee98ac fp: 0xfffffe3a3772f7f0
lr: 0xfffffe001f04188c fp: 0xfffffe3a3772f860
lr: 0xfffffe001f03fc74 fp: 0xfffffe3a3772f920
lr: 0xfffffe001ee93b88 fp: 0xfffffe3a3772f930
lr: 0xfffffe001eee91b0 fp: 0xfffffe3a3772fd00
lr: 0xfffffe001f751ed8 fp: 0xfffffe3a3772fd20
lr: 0xfffffe001f75e574 fp: 0xfffffe3a3772fd50
lr: 0xfffffe001f3e1274 fp: 0xfffffe3a3772fd80
lr: 0xfffffe001f42ddd8 fp: 0xfffffe3a3772fdf0
lr: 0xfffffe001f5638f4 fp: 0xfffffe3a3772fe50
lr: 0xfffffe001f03fd40 fp: 0xfffffe3a3772ff10
lr: 0xfffffe001ee93b88 fp: 0xfffffe3a3772ff20
lr: 0xfffffe001ee93b50 fp: 0x0000000000000000

last started kext at 2308577803: com.apple.filesystems.smbfs 6.0 (addr 0xfffffe001e33e6c0, size 110834)
loaded kexts:
com.apple.filesystems.smbfs 6.0
com.apple.driver.SoftRAID 8.3
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleAHCIPort 383
com.apple.driver.CoreKDL 1
com.apple.driver.AppleBiometricServices 1
com.apple.AppleEthernetAquantiaAqtionFirmware 1.0.36
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.iokit.SCSITaskUserClient 498
com.apple.driver.AppleUSBMassStorageInterfaceNub 556
com.apple.driver.AppleAOPVoiceTrigger 400.40
com.apple.driver.SEPHibernation 1
com.apple.driver.AppleUSBDeviceNCM 5.0.0
com.apple.driver.AppleThunderboltIP 4.0.3
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleFileSystemDriver 3.0.1

@sergey 

Same thing. No need to post panic logs here, they are in the support file.

I was just showing an example. SoftRAID is not in the backtrace. Seeing SMB, it might be related to network traffic. But a quick search of the panic string, os_refcnt: overflow Did not show much in the way results.

the error continues once every few days usually during the time when the server is not currently in use early in the morning, I am attaching a new log, updating to 15.1. 1 did not help

lust nloaded kest network and softraid

chat gpt says about this error, try disabling network services to check (which I can't do) and remove the sfotraid extension

@sergey 

I would be surprised if ChatGPT knew how to diagnose this.

What I need is a system diagnose file, after the next panic.

On restart, run this in terminal.app, as soon as possible.

sudo sysdiagnose -f ~/Desktop/

When the System Diagnose completes, which will take 5-10 minutes or so, then save a System report (System Settings/General/About, scroll down)

Also save a new SoftRAID support file.

Click on select files, put them in a folder and compress.

, go to

https://filetransfer.io

Select the Diagnostic file folder on your desktop.
Paste the link here, I will not post it.

did you receive my archive?

@sergey 
Yes, thank you, I thought I had posted, sorry.
We submitted this to Apple for review, but since it is a holiday week, it won't be for another week plus before we hear back.

I did find this interesting post at Apple discussions, which is the same panic you are seeing:
https://discussions.apple.com/thread/251318504?sortBy=rank

Its the only reference to this panic I could find

Any chance your Mini could be over heating? is it ventilated? What apps are you running that are intensive, if any?

This computer serves exclusively as a server, absolutely no applications except the operating system and SoftRaid with external thunderbay 8 and 2 time machine backups, 1 inside thunderbay and 1 external usb. The computer does not overheat at all, I monitor its temperature with the help of mac fan control,he is cold. No one is working on the computer. Let me remind you once again that panic does not occur during the working day when the load is stronger

@sergey 

Let me see what I can learn. I asked about over heating, as it seemed to be the trigger on the only related panic I could find online. I have never seen this panic before, and I see a lot of different kernel panics!

Thank you. So far the new crash happened a little before 6am and I noticed it after a few minutes, no one was working with the server at that time (maybe some computers were left connected in the studio) I can send a new log if it helps

also the disks in thunderbay do not overheat

One System Diagnose is enough.
In the Apple forum, the trigger seemed to be CPU/GPU related, not drives, but you give me a though.
Disable SMART checks with Disk Drill. Maybe they are doing something odd with SMART checks, its possible, and worth the test.