Tristankin

Yeah, it is a bit hard to tell if the kernel panic isn't even appearing. I have tried turning off all C states in the BIOS and underclocking the ram since the last reboot. Not sure what else to try without taking the server offline for days turning off dockers and doing memory tests, I have a lot of family and friends relying on the uptime.

And again. Jul 28 13:03:19 Firefly smbd[7089]: daemon_ready: daemon 'smbd' finished starting up and ready to serve connections Jul 28 13:03:19 Firefly root: /usr/sbin/winbindd -D Jul 28 13:03:19 Firefly winbindd[7102]: [2021/07/28 13:03:19.158615, 0] ../../source3/winbindd/winbindd_cache.c:3203(initialize_winbindd_cache) Jul 28 13:03:19 Firefly winbindd[7102]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Jul 28 13:03:19 Firefly winbindd[7102]: [2021/07/28 13:03:19.159091, 0] ../../lib/util/become_daemon.c:135(daemon_ready) Jul 28 13:03:19 Firefly winbindd[7102]: daemon_ready: daemon 'winbindd' finished starting up and ready to serve connections Jul 28 19:56:22 Firefly kernel: microcode: microcode updated early to revision 0xde, date = 2020-05-25 Jul 28 19:56:22 Firefly 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 28 19:56:22 Firefly kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Jul 28 19:56:22 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Jul 28 19:56:22 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Jul 28 19:56:22 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Jul 28 19:56:22 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Jul 28 19:56:22 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Jul 28 19:56:22 Firefly kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Jul 28 19:56:22 Firefly kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Jul 28 19:56:22 Firefly kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Jul 28 19:56:22 Firefly kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. Jul 28 19:56:22 Firefly kernel: BIOS-provided physical RAM map: This time I disabled suspend to ram in the bios and lowered the ram clock to 2133 (i3-9100 2400MT/s is not overclocking) Any other suggestions?

You seem to have the same issue as I do. Any chance you are running intel hardware?

Your issue seems to be very similar to mine. I am also seeing nothing before the freeze requiring a hard reset. For me it has only happened with 6.9.x. I rolled back to 6.8.3 and the problem was gone. I thought it might have been my fault because I did not change the go file for plex, but even with the go file changes it is still restarting. Might go back to 6.8.3 again.

Is there a lower level log that I can turn on to perhaps catch some mor einformation?

The roll back to 6.8.3 fixed the issue completely last time. I would doubt it is a hardware issue if the old version works for 12 months total including the roll back without a single freeze. I was hoping to help find an issue with 6.9 but I guess I will just roll back again?

Another freeze last night, both times now the mover was the last thing to run. Jul 27 05:02:46 Firefly crond[1711]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null syslog

Took me a while to find the setting for host access. This has been disabled the whole time I am pretty sure. There are quite a few networks in all as I have had to push jackett, radarr and sonarr clients through deluge since the proxy has been disabled. I also have a few dockers that are setup for external access through swag and only plex which appears on the host network. Let me know if you see anything stupid though...

Hi All, Wondering if I could get some support for 6.9.2. I previously upgraded and was freezing every 24 hours or so so I rolled back to 6.8.3 (I did not change the config in the go file so this was my fault). I have recently tried 6.9.2 again and the system is now freezing at least once a week. I am using intel iGPU transcoding on my i3-9100, the setup is pretty basic in all with only a few dockers running. The 2 periods I was on 6.8.3 (~12 months total) the system has been 100% rock solid but for some reason 6.9.2 doesn't like my system. As far as I can tell there is no useful information in the syslog. I rebooted at 19:09 on July 22. If anyone can point e in the right direction it would be excellent. syslog firefly-diagnostics-20210722-2358.zip

Any chance you are using igpu transcoding in plex? You may have used old config steps. I was having the same issue on my system.

I am using behex plex on my server. I have rolled back to 6.8.3 as I have many friends and family relying on this machine and get harassed when it goes down let alone stopping the docker for longer than an hour. I copied the 6..8.3 files onto the usb and still used the new disk config (did not have to revert to the .bak file) and everything mounted ok once reassigning the cache disks to the array (nothing lost off the cache) Not going to be an early adopter again. Going to wat a few months next time.

Progress! I like it when someone sees a pattern! Unfortunately plex is the main reason for this box so I will have to roll back to 6.8.3 unless there is a new kernel in the upcoming release that will fix this issue.

Might have also been the unraid API, I removed that to test aswell.

OK, 3rd halt in 1 day, The system in now less stable with the cache 1MB alignment. I have paired back to the same docker containers that previously gave 3 days uptime. Is it a cache pool issue? What do I need to look for? Mar 19 16:08:36 Firefly unassigned.devices: Mounting 'Auto Mount' Remote Shares... Mar 19 16:08:36 Firefly kernel: docker0: port 1(vethe1c8de7) entered blocking state Mar 19 16:08:36 Firefly kernel: docker0: port 1(vethe1c8de7) entered disabled state Mar 19 16:08:36 Firefly kernel: device vethe1c8de7 entered promiscuous mode Mar 19 16:08:36 Firefly kernel: docker0: port 1(vethe1c8de7) entered blocking state Mar 19 16:08:36 Firefly kernel: docker0: port 1(vethe1c8de7) entered forwarding state Mar 19 16:08:36 Firefly kernel: docker0: port 1(vethe1c8de7) entered disabled state Mar 19 16:08:37 Firefly kernel: eth0: renamed from vethb11e8e3 Mar 19 16:08:37 Firefly kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe1c8de7: link becomes ready Mar 19 16:08:37 Firefly kernel: docker0: port 1(vethe1c8de7) entered blocking state Mar 19 16:08:37 Firefly kernel: docker0: port 1(vethe1c8de7) entered forwarding state Mar 19 16:08:37 Firefly kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready Mar 19 16:08:37 Firefly rc.docker: binhex-delugevpn: started succesfully! Mar 19 16:08:37 Firefly rc.docker: binhex-jackett: started succesfully! Mar 19 16:08:38 Firefly rc.docker: binhex-plex: started succesfully! Mar 19 16:08:38 Firefly rc.docker: binhex-radarr: started succesfully! Mar 19 16:08:38 Firefly rc.docker: binhex-sonarr: started succesfully! Mar 19 16:08:38 Firefly kernel: docker0: port 2(veth705544b) entered blocking state Mar 19 16:08:38 Firefly kernel: docker0: port 2(veth705544b) entered disabled state Mar 19 16:08:38 Firefly kernel: device veth705544b entered promiscuous mode Mar 19 16:08:39 Firefly kernel: eth0: renamed from veth5e4ec31 Mar 19 16:08:39 Firefly kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth705544b: link becomes ready Mar 19 16:08:39 Firefly kernel: docker0: port 2(veth705544b) entered blocking state Mar 19 16:08:39 Firefly kernel: docker0: port 2(veth705544b) entered forwarding state Mar 19 16:08:39 Firefly rc.docker: pihole-template: started succesfully! Mar 19 16:51:44 Firefly kernel: microcode: microcode updated early to revision 0xde, date = 2020-05-25 Mar 19 16:51:44 Firefly kernel: Linux version 5.10.19-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Sat Feb 27 08:00:30 PST 2021 Mar 19 16:51:44 Firefly kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Mar 19 16:51:44 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Mar 19 16:51:44 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Mar 19 16:51:44 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Mar 19 16:51:44 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Mar 19 16:51:44 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Mar 19 16:51:44 Firefly kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Mar 19 16:51:44 Firefly kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Mar 19 16:51:44 Firefly kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Mar 19 16:51:44 Firefly kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.

I was getting errors with my workgroup name length "home.ubernerd.com.au" so I changed it to workgroup. I also am not able to access my shares via the computer name \\firefly (no credentials work) and have to go to the IP directly. Mar 19 16:07:07 Firefly nmbd[22431]: [2021/03/19 16:07:07.319174, 0] ../../source3/nmbd/nmbd_workgroupdb.c:56(name_to_unstring) Mar 19 16:07:07 Firefly nmbd[22431]: name_to_nstring: workgroup name HOME.UBERNERD.COM.AU is too long. Truncating to Mar 19 16:07:17 Firefly nmbd[22431]: [2021/03/19 16:07:17.328826, 0] ../../source3/nmbd/nmbd_workgroupdb.c:56(name_to_unstring) Mar 19 16:07:17 Firefly nmbd[22431]: name_to_nstring: workgroup name HOME.UBERNERD.COM.AU is too long. Truncating to Mar 19 16:07:17 Firefly nmbd[22431]: [2021/03/19 16:07:17.328865, 0] ../../source3/nmbd/nmbd_workgroupdb.c:56(name_to_unstring) Mar 19 16:07:17 Firefly nmbd[22431]: name_to_nstring: workgroup name HOME.UBERNERD.COM.AU is too long. Truncating to I have turned off WSD NETBios and local master Still cant access by going to \\FIREFLY but the ip still works Recent syslog attached firefly-syslog-20210319-0512.zip

Also why am I still getting IPV6 messages when I do not have IPV6 enabled?

Ok, so not just bitwarden, went down again with MQTT HASS and OrganizrV2, I'm sooo bored of this and not really getting anywhere. I know its dockers, might be something to do with networking but I literally have had no feedback from the team regarding what I should be looking for or how I can get more info. Mar 19 13:30:07 Firefly kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethac2e790: link becomes ready Mar 19 13:30:07 Firefly kernel: docker0: port 3(vethac2e790) entered blocking state Mar 19 13:30:07 Firefly kernel: docker0: port 3(vethac2e790) entered forwarding state Mar 19 13:30:09 Firefly kernel: br-b33c13ba4d4e: port 3(veth778e457) entered blocking state Mar 19 13:30:09 Firefly kernel: br-b33c13ba4d4e: port 3(veth778e457) entered disabled state Mar 19 13:30:09 Firefly kernel: device veth778e457 entered promiscuous mode Mar 19 13:30:09 Firefly kernel: br-b33c13ba4d4e: port 3(veth778e457) entered blocking state Mar 19 13:30:09 Firefly kernel: br-b33c13ba4d4e: port 3(veth778e457) entered forwarding state Mar 19 13:30:09 Firefly kernel: br-b33c13ba4d4e: port 3(veth778e457) entered disabled state Mar 19 13:30:10 Firefly kernel: eth0: renamed from veth5b009f2 Mar 19 13:30:10 Firefly kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth778e457: link becomes ready Mar 19 13:30:10 Firefly kernel: br-b33c13ba4d4e: port 3(veth778e457) entered blocking state Mar 19 13:30:10 Firefly kernel: br-b33c13ba4d4e: port 3(veth778e457) entered forwarding state Mar 19 13:34:35 Firefly ntpd[1693]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Mar 19 13:34:36 Firefly nmbd[8340]: [2021/03/19 13:34:36.710929, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Mar 19 13:34:36 Firefly nmbd[8340]: ***** Mar 19 13:34:36 Firefly nmbd[8340]: Mar 19 13:34:36 Firefly nmbd[8340]: Samba name server FIREFLY is now a local master browser for workgroup WORKGROUP on subnet 172.18.0.1 Mar 19 13:34:36 Firefly nmbd[8340]: Mar 19 13:34:36 Firefly nmbd[8340]: ***** Mar 19 13:34:36 Firefly nmbd[8340]: [2021/03/19 13:34:36.710995, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Mar 19 13:34:36 Firefly nmbd[8340]: ***** Mar 19 13:34:36 Firefly nmbd[8340]: Mar 19 13:34:36 Firefly nmbd[8340]: Samba name server FIREFLY is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1 Mar 19 13:34:36 Firefly nmbd[8340]: Mar 19 13:34:36 Firefly nmbd[8340]: ***** Mar 19 14:18:32 Firefly kernel: microcode: microcode updated early to revision 0xde, date = 2020-05-25 Mar 19 14:18:32 Firefly kernel: Linux version 5.10.19-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Sat Feb 27 08:00:30 PST 2021 Mar 19 14:18:32 Firefly kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Mar 19 14:18:32 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Mar 19 14:18:32 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Mar 19 14:18:32 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Mar 19 14:18:32 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Mar 19 14:18:32 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Mar 19 14:18:32 Firefly kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Mar 19 14:18:32 Firefly kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Mar 19 14:18:32 Firefly kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Mar 19 14:18:32 Firefly kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. Mar 19 14:18:32 Firefly kernel: BIOS-provided physical RAM map:

OK, I have changed the cache to 1MB aligned, turned off hass and MQTT and turned on bitwarden and then a few hours later I had a crash after 3 day uptime. I have turned on all dockers except for bitwarden and will see how things go. Restart log: Mar 19 10:55:15 Firefly root: plugin: creating: /usr/local/emhttp/plugins/dynamix.unraid.net/include/cfgMigration.php - from INLINE content Mar 19 10:55:15 Firefly root: plugin: running: anonymous Mar 19 10:55:15 Firefly root: plugin: running: anonymous Mar 19 10:55:15 Firefly root: plugin: running: anonymous Mar 19 10:55:18 Firefly root: Starting unraid-api in "production" mode. Mar 19 10:55:19 Firefly root: Daemonizing process. Mar 19 10:55:19 Firefly root: Daemonized successfully! Mar 19 10:55:20 Firefly root: Starting unraid-api in "production" mode. Mar 19 10:55:21 Firefly root: Daemonizing process. Mar 19 10:55:21 Firefly root: Daemonized successfully! Mar 19 11:02:00 Firefly flash_backup: adding task: php /usr/local/emhttp/plugins/dynamix.unraid.net/include/UpdateFlashBackup.php update Mar 19 13:28:45 Firefly kernel: microcode: microcode updated early to revision 0xde, date = 2020-05-25 Mar 19 13:28:45 Firefly kernel: Linux version 5.10.19-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Sat Feb 27 08:00:30 PST 2021 Mar 19 13:28:45 Firefly kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Mar 19 13:28:45 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Mar 19 13:28:45 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Mar 19 13:28:45 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Mar 19 13:28:45 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Mar 19 13:28:45 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Mar 19 13:28:45 Firefly kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Mar 19 13:28:45 Firefly kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Mar 19 13:28:45 Firefly kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Mar 19 13:28:45 Firefly kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. Mar 19 13:28:45 Firefly kernel: BIOS-provided physical RAM map:

I'm just a little worried about formatting my cache drives if I need to roll back to 6.8.3 as they will need to have the alignment changed back for them to work again.

Yeah, this is definitely not my issue. I have been using /dev/shm from the beginning. 3 Day uptime so far, I have added SWAG back in and tomorrow I will start up hass and MQTT and see what happens.

Well 1 Day 10 Hour uptime with 6.9.0 and the reduced number of dockers running. I had restarts with 6.9.1 and 6.9.0 before so somehow the combination is either slowing the issue or one of the dockers I am no longer running is the culprit.

I have turned off half of my docker containers to see if any of them are the culprit. I prioritised services my friends and family rely on. Here is a graphic to show what is on and off. 16 hour uptime so far...

Another hang today... Mar 15 13:20:12 Firefly rc.docker: MQTT: started succesfully! Mar 15 13:20:12 Firefly kernel: br-b33c13ba4d4e: port 3(veth1e1571d) entered blocking state Mar 15 13:20:12 Firefly kernel: br-b33c13ba4d4e: port 3(veth1e1571d) entered disabled state Mar 15 13:20:12 Firefly kernel: device veth1e1571d entered promiscuous mode Mar 15 13:20:12 Firefly kernel: br-b33c13ba4d4e: port 3(veth1e1571d) entered blocking state Mar 15 13:20:12 Firefly kernel: br-b33c13ba4d4e: port 3(veth1e1571d) entered forwarding state Mar 15 13:20:13 Firefly kernel: br-b33c13ba4d4e: port 3(veth1e1571d) entered disabled state Mar 15 13:20:13 Firefly webGUI: Successful login user root from 192.168.1.111 Mar 15 13:20:13 Firefly kernel: eth0: renamed from veth0b9a67a Mar 15 13:20:13 Firefly kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1e1571d: link becomes ready Mar 15 13:20:13 Firefly kernel: br-b33c13ba4d4e: port 3(veth1e1571d) entered blocking state Mar 15 13:20:13 Firefly kernel: br-b33c13ba4d4e: port 3(veth1e1571d) entered forwarding state Mar 15 13:20:13 Firefly rc.docker: organizrv2: started succesfully! Mar 15 13:20:13 Firefly kernel: br-b33c13ba4d4e: port 4(veth3465bc7) entered blocking state Mar 15 13:20:13 Firefly kernel: br-b33c13ba4d4e: port 4(veth3465bc7) entered disabled state Mar 15 13:20:13 Firefly kernel: device veth3465bc7 entered promiscuous mode Mar 15 13:20:13 Firefly kernel: br-b33c13ba4d4e: port 4(veth3465bc7) entered blocking state Mar 15 13:20:13 Firefly kernel: br-b33c13ba4d4e: port 4(veth3465bc7) entered forwarding state Mar 15 13:20:14 Firefly kernel: br-b33c13ba4d4e: port 4(veth3465bc7) entered disabled state Mar 15 13:20:14 Firefly kernel: eth0: renamed from vethcc29778 Mar 15 13:20:14 Firefly kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3465bc7: link becomes ready Mar 15 13:20:14 Firefly kernel: br-b33c13ba4d4e: port 4(veth3465bc7) entered blocking state Mar 15 13:20:14 Firefly kernel: br-b33c13ba4d4e: port 4(veth3465bc7) entered forwarding state Mar 15 13:20:14 Firefly rc.docker: swag: started succesfully! Mar 15 13:20:16 Firefly kernel: tun: Universal TUN/TAP device driver, 1.6 Mar 15 13:20:25 Firefly nmbd[8257]: [2021/03/15 13:20:25.807488, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Mar 15 13:20:25 Firefly nmbd[8257]: ***** Mar 15 13:20:25 Firefly nmbd[8257]: Mar 15 13:20:25 Firefly nmbd[8257]: Samba name server FIREFLY is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.10 Mar 15 13:20:25 Firefly nmbd[8257]: Mar 15 13:20:25 Firefly nmbd[8257]: ***** Mar 15 13:20:28 Firefly kernel: mdcmd (37): nocheck Cancel Mar 15 13:20:28 Firefly kernel: md: recovery thread: exit status: -4 Mar 15 13:25:41 Firefly nmbd[8257]: [2021/03/15 13:25:41.350529, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Mar 15 13:25:41 Firefly nmbd[8257]: ***** Mar 15 13:25:41 Firefly nmbd[8257]: Mar 15 13:25:41 Firefly nmbd[8257]: Samba name server FIREFLY is now a local master browser for workgroup WORKGROUP on subnet 172.18.0.1 Mar 15 13:25:41 Firefly nmbd[8257]: Mar 15 13:25:41 Firefly nmbd[8257]: ***** Mar 15 13:25:41 Firefly nmbd[8257]: [2021/03/15 13:25:41.350598, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Mar 15 13:25:41 Firefly nmbd[8257]: ***** Mar 15 13:25:41 Firefly nmbd[8257]: Mar 15 13:25:41 Firefly nmbd[8257]: Samba name server FIREFLY is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1 Mar 15 13:25:41 Firefly nmbd[8257]: Mar 15 13:25:41 Firefly nmbd[8257]: ***** Mar 15 13:26:00 Firefly ntpd[1708]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Mar 15 19:21:58 Firefly kernel: microcode: microcode updated early to revision 0xde, date = 2020-05-25 Mar 15 19:21:58 Firefly kernel: Linux version 5.10.21-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Sun Mar 7 13:39:02 PST 2021 Mar 15 19:21:58 Firefly kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Mar 15 19:21:58 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Mar 15 19:21:58 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Mar 15 19:21:58 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Mar 15 19:21:58 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Mar 15 19:21:58 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Mar 15 19:21:58 Firefly kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Mar 15 19:21:58 Firefly kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Mar 15 19:21:58 Firefly kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Mar 15 19:21:58 Firefly kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. Mar 15 19:21:58 Firefly kernel: BIOS-provided physical RAM map:

System hung again at about 1pm here. Nothing again in the logs, I have turned off privoxy on DelugeVPN and pushed everything through IP tables in case that was the issue. I'm at a loss at what to do. If I roll back that is a temporary fix, and not helpful for others experiencing the same issues. What do I need to do to provide enough info to get this sorted? I am really starting to worry about unexpected array errors or reduced disk life from constantly performing parity checks. Let me know what you need. Is it IPv6 config? I do not have IPv6 Enabled? Mar 15 06:59:12 Firefly crond[1743]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Mar 15 12:15:46 Firefly kernel: veth49c1513: renamed from eth0 Mar 15 12:15:46 Firefly kernel: br-b33c13ba4d4e: port 4(veth566858e) entered disabled state Mar 15 12:15:47 Firefly kernel: br-b33c13ba4d4e: port 4(veth566858e) entered disabled state Mar 15 12:15:47 Firefly kernel: device veth566858e left promiscuous mode Mar 15 12:15:47 Firefly kernel: br-b33c13ba4d4e: port 4(veth566858e) entered disabled state Mar 15 12:15:47 Firefly kernel: br-b33c13ba4d4e: port 4(veth6f57b1d) entered blocking state Mar 15 12:15:47 Firefly kernel: br-b33c13ba4d4e: port 4(veth6f57b1d) entered disabled state Mar 15 12:15:47 Firefly kernel: device veth6f57b1d entered promiscuous mode Mar 15 12:15:47 Firefly kernel: br-b33c13ba4d4e: port 4(veth6f57b1d) entered blocking state Mar 15 12:15:47 Firefly kernel: br-b33c13ba4d4e: port 4(veth6f57b1d) entered forwarding state Mar 15 12:15:47 Firefly kernel: br-b33c13ba4d4e: port 4(veth6f57b1d) entered disabled state Mar 15 12:15:48 Firefly kernel: eth0: renamed from veth852511e Mar 15 12:15:48 Firefly kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6f57b1d: link becomes ready Mar 15 12:15:48 Firefly kernel: br-b33c13ba4d4e: port 4(veth6f57b1d) entered blocking state Mar 15 12:15:48 Firefly kernel: br-b33c13ba4d4e: port 4(veth6f57b1d) entered forwarding state Mar 15 13:19:40 Firefly kernel: microcode: microcode updated early to revision 0xde, date = 2020-05-25 Mar 15 13:19:40 Firefly kernel: Linux version 5.10.21-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Sun Mar 7 13:39:02 PST 2021 Mar 15 13:19:40 Firefly kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Mar 15 13:19:40 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Mar 15 13:19:40 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Mar 15 13:19:40 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Mar 15 13:19:40 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Mar 15 13:19:40 Firefly kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Mar 15 13:19:40 Firefly kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Mar 15 13:19:40 Firefly kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Mar 15 13:19:40 Firefly kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Mar 15 13:19:40 Firefly kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. Mar 15 13:19:40 Firefly kernel: BIOS-provided physical RAM map:

Only thing different about my setup is that I held delugevpn back as the new iptables config broke everything with my swag setup. I'm trying to get it all changed over to the new IPtables config now.