noweakness

Ok I actually did the mirror to flash drive yesterday as a precaution since I didn't see any logs generated otherwise. At some point between Oct 3 and Oct 4 is when the computer last went offline. By the looks of it the last logs recorded were related to the network port. I'm sure my settings are a mess. I never had any issues before upgrading though which I find strange. Here is a snippet of the logs and I attached the full log (starting Oct 3). Thanks in advance Oct 3 15:16:34 GateKeeper kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbdcda6f: link becomes ready Oct 3 15:16:34 GateKeeper kernel: docker0: port 2(vethbdcda6f) entered blocking state Oct 3 15:16:34 GateKeeper kernel: docker0: port 2(vethbdcda6f) entered forwarding state Oct 3 15:16:39 GateKeeper kernel: docker0: port 2(vethbdcda6f) entered disabled state Oct 3 15:16:39 GateKeeper kernel: veth179c74e: renamed from eth0 Oct 3 15:16:39 GateKeeper kernel: docker0: port 2(vethbdcda6f) entered disabled state Oct 3 15:16:39 GateKeeper kernel: device vethbdcda6f left promiscuous mode Oct 3 15:16:39 GateKeeper kernel: docker0: port 2(vethbdcda6f) entered disabled state Oct 3 15:25:27 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 15:25:27 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 15:55:37 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 15:55:37 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 16:25:47 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 16:25:47 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 16:55:58 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 16:55:58 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 17:26:08 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 17:26:08 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 17:56:18 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 17:56:18 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 18:26:28 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 18:26:28 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 18:56:38 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 18:56:38 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 19:26:48 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 19:26:48 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 19:56:58 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 19:56:58 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 20:27:08 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 20:27:08 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 20:57:18 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 20:57:18 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 21:27:28 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 21:27:28 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 21:57:38 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 21:57:38 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 22:27:48 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 22:27:48 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 22:57:58 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 22:57:58 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 23:28:08 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 23:28:08 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 23:58:18 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 3 23:58:18 GateKeeper kernel: br0: received packet on bond0 with own address as source address (addr:90:e2:ba:96:13:1d, vlan:0) Oct 4 06:41:07 GateKeeper kernel: microcode: microcode updated early to revision 0x49, date = 2021-08-11 Oct 4 06:41:07 GateKeeper kernel: Linux version 6.1.49-Unraid (root@Develop-612) (gcc (GCC) 12.2.0, GNU ld version 2.40-slack151) #1 SMP PREEMPT_DYNAMIC Wed Aug 30 09:42:35 PDT 2023 Oct 4 06:41:07 GateKeeper kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Oct 4 06:41:07 GateKeeper kernel: BIOS-provided physical RAM map: syslog

Hi JorgeB, I have enabled the Syslog server but no logs are being generated. The Local syslog folder is my appdata and I tried another public share, and nothing is showing up. I also setup a remote Syslog server on my home desktop and enabled it on unraid with no logs being detected. My unraid server keeps crashing every 8-12 hours. Anywhere else I can look for whats causing the issue?

Perfect, thank you and will do.

Can someone point me in the right direction where I can review logs to see why unraid is crashing? When I check the logs after a reboot, they only start after I restart the server. The server has gone offline or been unreachable only after a day or two since I updated, very frustrating. I have also attached my diagnostics if anyone is better at reading them than myself. Thanks in advance. gatekeeper-diagnostics-20231002-1016.zip

I've tried everything I was able to Google to get the cache disk emptied with no luck. Any suggestions or links?

Hi all, I recently decided to upgrade Unraid because I was having some weird issues creating and running a Ubuntu VM, plus I decided I should update for the other obvious reasons. Now that I've upgraded, my docker tab says "Docker Service failed to start" and VM tab shows empty. I googled to try and find a solution, but so far no luck. Services are enabled. I also have issues stopping the Array, it just seems to spin and run non-stop showing "stopping" for over an hour, and I have to reboot it to get it back to normal. I've attached the diagnostic file. I think part of the reason might be the cache disk which is full and I've experienced this for the past year or so, for some reason it won't go down at all no matter what I've tried. But everything worked while it was full before upgrading. Keep in mind I'm not linux or unraid savvy, it took a lot of videos to get where I'm at today. I have a backup and don't mind going back to where everything was before the upgrade, but would be nice to run the latest version. Thanks in advance. gatekeeper-diagnostics-20230921-1346.zip

Two more questions if I can. 1. If I'm running pfsense virtual on unraid, is there a particular setup I need for IP allocation? Will I need to create a static IP on unraid AND pfsense for the unraid server, or does it matter? I have a feeling if I reboot unraid with pfsense not loaded yet, it won't retrieve its IP and not let me log in again. 2. Can I run 2 separate networks to unraid without problems? Network 1 - Pfsense 192.168.11.XXX subnet (Main)/2 ports bonded (Eth0 + Eth1) Network 2 - ATT box 192.168.1.XXX subnet (Backup or guest wifi network) I'm looking to purchase pfsense hardware, but for different setups, I'd like to know what options I have. Thanks in advance.

I guess it was as simple as unplugging the other connections and just plugging into Eth0 (after deleting the config file) to get an IP address. I'll start working on that setup, appreciate the information for bonding.

Oh interesting. Since Eth0 is my onboard NIC, I don't really need it. Can I just disable it within unraid or change it from Eth0 to something else from the config file or console? Also, any ideas how I can access my GUI? I knew bonding would mess things up....smh.

I should be able to access unraid even if the array isn't started, right? But yes, it should be set to automatically run.

So unraid has really testing my patience out, and I know its my fault but dang. I plan on getting a separate hardware device to install pfsense, but in the meantime I thought I'd get a temporary setup to get a head start setting everything up. Well somehow I can't login to my unraid GUI. I'm guessing because pfsense doesn't load until unraid is fully loaded and has an IP, but it can't reach pfsense because its not loaded yet. When I turn on my unraid machine, i get "IPv4 address: not set". I've deleted my config file from usb with no luck. Here is a summary of my NICs. Onboard NIC eth0 - Plugged into my ATT home router, also a wan port and connection to my old 192.168.1.XX network ( kept this connected for a backup, clearly this did not good) Intel NIC port 4 - WAN port within pfsense Intel NIC Port 1 & 2 - Unraid LAN bonding port with my new network 192.168.11.XX Below is my network config file settings, I tried to add [GATEWAY[0]="192.168.1.254"] to the config file hoping my AT&T router could at least give it an IP. Needless to say I'm stressed and running out of options to log into unraid. I tried looking up commands for console to reset or refresh my network settings but couldn't find anything except "ifconfig eth0 up/down" which did nothing. I appreciate any suggestions. pfsense loads up after a reboot and I can access it, just can't log into my unraid server because it can't get an IP. # Generated settings: IFNAME[0]="eth0" DESCRIPTION[0]="Onboard NIC" PROTOCOL[0]="ipv4" USE_DHCP[0]="yes" DHCP_KEEPRESOLV="no" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" IFNAME[1]="br1" BONDNAME[1]="bond1" BONDNICS[1]="eth1 eth2" BONDING_MODE[1]="4" BONDING_MIIMON[1]="100" BRNAME[1]="br1" BRNICS[1]="bond1" BRSTP[1]="no" BRFD[1]="0" DESCRIPTION[1]="LAG LAN" PROTOCOL[1]="ipv4" USE_DHCP[1]="no" IPADDR[1]="192.168.11.100" NETMASK[1]="255.255.255.0" GATEWAY[1]="192.168.11.98" IFNAME[2]="eth3" PROTOCOL[2]="ipv4" SYSNICS="3"

Any updates on this? I'm having the same issue.