D4M4EVER

I pulled out all my drives and tossed into other server to see if i get the same issue on another setup using different motherboard, ram & cpu's. While running unraid on the "backup server" I still get these kernel panics that freeze up/crash unraid. While I was running on the "backup server" I ran memtest86 on the original mobo, cpu, & ram setup. Ran memtest for just over 8days and it showed zero error's. Unraid crashes on both of my mobo, cpu, ram setups about every 20-25hrs.

Searching for hours for my kernel panic issues on here, didn't realized these guys are on unraid OS 6.8.3, i seen the same kernel issues I'm fighting on the beta version. On a side note i did run memtest for just over 8days and it showed zero issues.

I've been fighting kernel panic issues for last few weeks aswell. I pulled all my drives and USB stick out and swapped over to another server setup and was able to go 8 days before getting the kernel panic. Here's a pastebin of my last kernel panic attack. https://pastebin.com/vN5vQ8EN

Last few days server has crashed twice for Kernel Panic "Fatal exception in interrupt" First occurrence was running Unraid version 6.9.0-beta25, happened 2 days ago (image dated 2020-10-03). I took screen shot of the display using the IPMI KVM access. I upgraded Unraid version to latest beta version (Unraid V6.9.0Beta29) after the kernel alarm on 2020-10-03, all seemed fine until today. Got another kernel alarm screen shot catapulted off IPMIView mobile app (image dated 2020-10-05). After rebooting the server today after the 2nd occurrence of the kernel panic withing a few minutes of array starting backup my syslog is getting flooded with "Unraid shfs: share cache full" I have activated the syslog to write to flash to try and gather more info for if/when the kernel panic happens again, I hope to get some assistance on figuring out the cause of the kernel panic's. Attached is current Diagnostics file and copy of latest syslog pulled from the flash drive. Thanks in advance for you help. unraid-diagnostics-20201005-1811.zip syslog

Issue solved, Thanks guys for the help.

Whoops, need mess with setting to only have it spin down the SATA drives then. After fixing setting on spin downs, I'll do a reboot and see if its not longer getting filled up

Not sure if this helps but about 20 hours ago I did setup my disks to spin down if inactive for 4 hours. Then I started a fairly large data dump from a different NAS, about 2.3TB, when the file transfer started it had ETA of 8.5 hours or so. The file transfer is still going on now, been over 20 hours. Here's a ss of system stats for last day.

Yes my SAS is running in non-RAID mode, at least I hope it is. All drives on connected by HP SAS expander, my onboard LSI SAS is running in IT mode. I just ran a few manual SMART checks om a couple drives to see what kind of reporting I would get. from what i see it looked OK. I haven't installed atop.

Here's the complete diagnostics file.

Hi all, came home to a fix common problems warning. I'm still very new to unraid (1st trial period not over yet). The warning I recieved is tas follows: /var/log is getting full (currently 73 % used) Suggested fix = "Either your server has an extremely long uptime, or your syslog could be potentially being spammed with error messages." My system uptime is currently 23 hours, don't think that is causing the issue. What are some things I should check out to narrow the root cause down. Thanks in advance.