Not much to offer.  I've got syslog writing to flash but it's not seeming to capture anything useful.  Services all start up, finds some parity problems, and then the fresh boot.  

I've got a picture of one of the bad boots from a couple days ago.  It seems to run fine for a week or so and then get these error bouts and lockup every couple of hours.  Usually during the parity check.

 

Jul 17 19:47:15 Diskstation kernel: docker0: port 5(vethd360b9b) entered blocking state
Jul 17 19:47:15 Diskstation kernel: docker0: port 5(vethd360b9b) entered forwarding state
Jul 17 19:47:40 Diskstation rc.docker: sabnzbd: started succesfully!
Jul 17 19:47:40 Diskstation rc.docker: sabnzbd: wait 1 seconds
Jul 17 19:51:09 Diskstation rc.docker: Plex-Media-Server: wait 2 seconds
Jul 17 19:51:09 Diskstation rc.docker: Plex-Media-Server: started succesfully!
Jul 17 19:52:31 Diskstation kernel: process '1d9f504654e675d1d436ebc59735f28e772d2ab792b7112dd05516cfc7fefecd/usr/bin/par2' started with executable stack
Jul 17 20:31:30 Diskstation kernel: md: recovery thread: P incorrect, sector=833814792
Jul 17 20:31:30 Diskstation kernel: md: recovery thread: P incorrect, sector=833814808
Jul 17 20:31:30 Diskstation kernel: md: recovery thread: P incorrect, sector=833815160
Jul 17 20:31:30 Diskstation kernel: md: recovery thread: P incorrect, sector=833815168
Jul 17 21:47:59 Diskstation kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13
Jul 17 21:47:59 Diskstation kernel: Linux version 5.10.28-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Wed Apr 7 08:23:18 PDT 2021
Jul 17 21:47:59 Diskstation kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot

ideas?

diskstation-diagnostics-20210717-2200.zip

I'm so stupid when it comes to this stuff, but my Manjaro Linux box (arch, like unraid, as I understand it), asked me to upgrade my kernel recently. I didn't know what to do, but followed "things" and Manjaro is working great.

 

I thought unraid might upgrade kernels, but I thought Manjaro would do the same. I only say this because you said, "Kernel panic reoccurring" and, assumed "kernel" to be the linux kernel. I'm probably wrong.

 

Now, I'm worried unraid is running on an old kernel and won't fix it.

 

6.

I've had two more lockups since posting this. 

 

Only guess is that a docker is causing some issues. I'll let the current parity check happen and then turn them on one at a time.

Jul 18 11:24:59 Diskstation kernel: docker0: port 5(veth7b8674a) entered forwarding state
Jul 18 11:24:59 Diskstation kernel: docker0: port 5(veth7b8674a) entered disabled state
Jul 18 11:27:19 Diskstation nginx: 2021/07/18 11:27:19 [error] 2471#2471: *29722 upstream timed out (110: Connection timed >
Jul 18 11:27:19 Diskstation nginx: 2021/07/18 11:27:19 [error] 2471#2471: *29755 upstream timed out (110: Connection timed >
Jul 18 11:28:10 Diskstation kernel: docker0: port 5(veth7b8674a) entered disabled state
Jul 18 11:28:10 Diskstation kernel: device veth7b8674a left promiscuous mode
Jul 18 11:28:10 Diskstation kernel: docker0: port 5(veth7b8674a) entered disabled state
Jul 18 14:16:05 Diskstation kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13
Jul 18 14:16:05 Diskstation kernel: Linux version 5.10.28-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-sla>
Jul 18 14:16:05 Diskstation kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot

 

Without nothing logged in the syslog it's usually hardware related, but one thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.