Jump to content

JorgeB

Moderators
  • Posts

    67,647
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Best bet is to post in the appropriate support thread/link:
  2. See if this applies to you: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
  3. https://lime-technology.com/forums/topic/72837-error-log-filled-to-100-in-1day-47min-with-this/?do=findComment&comment=669775
  4. Yes, but there is nf_conntrack which is usually related.
  5. SMART looks fine so likely also a power/connection issue.
  6. Don't understand what you mean, disk1 is unmountable but enable, disk4 is disable but mounting.
  7. You can do that with the IPMI plugin and and board with IPMI support, e.g., from Supermicro, current boards will cost from around $200, you can also get used much cheaper.
  8. Docker image looks to be pretty new, add the docker containers from previous apps: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
  9. If the extended test passed the disk is fine, at least for now, and the pending sectors are a false positive, but if you want they can usually be reset with a full disk write.
  10. Please use the existing plugin support thread:
  11. There also some data corruption detected on disk4: May 15 11:38:32 Tower kernel: BTRFS info (device md4): bdev /dev/md4 errs: wr 0, rd 0, flush 0, corrupt 25, gen 0 You can run a scrub to identify any corrupt data, also good idea to run a memtest.
  12. Wait for the test to finish and proceed according to the result.
  13. To keep the data you could only use multiple "pools" of single drives.
  14. Do you mean raid1? Please post the diagnostics: Tools -> Diagnostics
  15. Run a filesystem check on disk1, disk4 appears to be really failing, you can run an extended SMART test to confirm, if it fails replace.
  16. Since the traces are mentioning xfs run a filesystem check (without -n) on all your xfs filesystems and see if it helps.
  17. It might have been a one off thing, don't remember seeing anyone else with issues with wireguard.
  18. Yeah, I was going to mention that at first, but though it would be kind of obvious, or the device wouldn't be powered
×
×
  • Create New...