spdelope

Members
  • Posts

    14
  • Joined

  • Last visited

spdelope's Achievements

Noob

Noob (1/14)

2

Reputation

  1. Thank you! I upgraded shortly after 6.11 released and made the change and havent had this issue again
  2. I would except with the file permission issues I had with 6.10 all the way to 6.10.3. I saw quite a few others with the same problem.
  3. I mean servers are supposed to be on 24/7 but you can use a smart plug like a kasa hs105 or something like that. And make sure there's a setting in bios to turn on after getting power restored. Then, when you want to turn it on, just reset the outlet.
  4. I went ahead and turned off the pihole docker (it was a backup to my pi anyways) we'll see how long I can go with out a crash!
  5. The only docker I have running in br0 with its own ip address is pihole. I had countless file permission issues with v6.10. Do you think just stopping pihole will resolve my issue? Thank you
  6. syslog (2)I also posted the syslog file here. I had crashes at Sept 9 12:03p, Sept 4 7:43a, Sept 1 2:54p, Aug 22 2:58a. Thanks for the help
  7. This is the result from df -h / Filesystem Size Used Avail Use% Mounted on rootfs 16G 1.7G 14G 11% / I had the larger docker image size just to avoid it filling up. I'm at 16gb now and I think I just went to 120 since I have plenty of space on my cache so didn't want to deal with it again.
  8. I'm the OP, I posted the last few lines from syslog. I have it mirroring to usb
  9. unraid-server-diagnostics-20220910-1004.zip Diagnostics attached. I have tried deleting some plugins not used and disabling igmp snooping and stp for the port on my switch and still have the issue.
  10. I have had this issue for a while and can't quite nail it down. My server will randomly hang and become unresponsive, requiring me to reboot on the machine. Cannot access via webgui, ssh, or via monitor plugged in. Never any real info in the logs from what I can tell. Here are from the last time this happened. My server locked up later around 12:01pm or so but the logs stopped until I rebooted. The last line is concerning. Sep 9 11:53:12 UnRaid-Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth367ca58: link becomes ready Sep 9 11:53:12 UnRaid-Server kernel: docker0: port 18(veth367ca58) entered blocking state Sep 9 11:53:12 UnRaid-Server kernel: docker0: port 18(veth367ca58) entered forwarding state Sep 9 11:53:21 UnRaid-Server kernel: docker0: port 18(veth367ca58) entered disabled state Sep 9 11:53:21 UnRaid-Server kernel: vethd0ae93e: renamed from eth0 Sep 9 11:53:21 UnRaid-Server kernel: docker0: port 18(veth367ca58) entered disabled state Sep 9 11:53:21 UnRaid-Server kernel: device veth367ca58 left promiscuous mode Sep 9 11:53:21 UnRaid-Server kernel: docker0: port 18(veth367ca58) entered disabled state Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered blocking state Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered disabled state Sep 9 11:54:21 UnRaid-Server kernel: device vethee550ee entered promiscuous mode Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered blocking state Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered forwarding state Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered disabled state Sep 9 11:54:21 UnRaid-Server kernel: eth0: renamed from vethd3a5f8d Sep 9 11:54:21 UnRaid-Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethee550ee: link becomes ready Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered blocking state Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered forwarding state Sep 9 11:54:26 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered disabled state Sep 9 11:54:26 UnRaid-Server kernel: vethd3a5f8d: renamed from eth0 Sep 9 11:54:26 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered disabled state Sep 9 11:54:26 UnRaid-Server kernel: device vethee550ee left promiscuous mode Sep 9 11:54:26 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered disabled state Sep 9 11:54:27 UnRaid-Server kernel: general protection fault, probably for non-canonical address 0x49e5ef1403d70: 0000 [#3] SMP NOPTI Sep 9 11:54:27 UnRaid-Server kernel: CPU: 0 PID: 8290 Comm: Disk Tainted: P D W O 5.10.28-Unraid #1 Sep 9 11:54:27 UnRaid-Server kernel: Hardware name: ASUS System Product Name/PRIME Z590-A, BIOS 1202 10/27/2021 Sep 9 11:54:27 UnRaid-Server kernel: RIP: 0010:page_vma_mapped_walk+0x209/0x4dc
  11. One of the recent updates is causing my gpu to not go to a sleep state. Would go to P8 after a single login. Now it goes to sleep mode for a second or two and then goes back to P0. Not sure what caused it
  12. Are there limitations to the games I can install, like I can't seem to install among us? Can I install ISO images?