Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,616

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    First link has alternative ways of configuring dockers.
  2. JorgeB
    What filesystem is Lexar#1?
  3. JorgeB
    Monitor the pool for errors, though this is important for any btrfs pool, pool should be immediately scrubbed after any unclean shutdown, but keep in mind that scrub on raid5/6 pools are painfully slow, unless you're using SSDs, so be prepared for that.
  4. JorgeB
    See here for some recovery options: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490
  5. JorgeB
    If safe mode is working it's likely a plugin, uninstall them all.
  6. JorgeB
    No link detected on eth0: Link detected: no
  7. JorgeB
    Then it's most likely a hardware issue, look for a BIOS update if you don't already
  8. JorgeB
    Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. 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/
  9. JorgeB
    First fix that then see if it solves the problem, don't see any reasons for the crashing logged.
  10. JorgeB
    Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. 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/
  11. JorgeB
    This seems to be the number one reason for crashing (on non Ryzen hardware), see if it applies to you: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/?do=getNewComment&d=2&id=1356
  12. JorgeB
    There are Macvlan call traces
  13. JorgeB
    Yes, disk looks fine, swap cables/slot with another disk to rule that out and if the emulated disk is mounting and contents look correct you can rebuild on top.
  14. JorgeB
    Current set shutdown timeout is not long enough, stop the array manually and time how long it takes for the array to stop, add a few seconds and set that as your VM shutdown timeout, then add 30 seconds or so to that value and set that as the general Unraid timeout.
  15. JorgeB
    Enable this then post that syslog after a crash, also post the complete diagnostics.
  16. JorgeB
    Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/
  17. JorgeB
    There are still some issues, but it can be used, I have several btrfs RAID5 pools, but also have good backups.
  18. JorgeB
    No, and those errors after spin down are not that uncommon, and not a real problem, sometimes changing the disks APM level or disabling it helps.
  19. JorgeB
    Not the disk errors, looks like disks 9 and 10 dropped offline.
  20. JorgeB
    Disk looks OK, replace or swap cables/slot with another disk and try again.
  21. JorgeB
  22. JorgeB
    That's normal, free space is always trimmed, you can check the log for the plugin output.
  23. JorgeB
    When this happens Unraid saves the diags in the flash drive, those could give a clue on what's causing it.
  24. JorgeB
    https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923
  25. JorgeB
    Unraid currently only supports one array, pools use btrfs, and can use any of the available btrfs profiles, including raid5/6, but note that those are still considered experimental.
×
×
  • Create New...