Jump to content

JorgeB

Moderators
  • Posts

    67,603
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Parity disk is SMR (also disk6), but parity can really have an impact on all write performance.
  2. Likely related to this, see if it 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. This should be much faster with 10GbE, while it's caching to RAM. But this suggests it's not just a network issue, in any case I would start with a single stream iperf test.
  4. Can't download diags, forum problem, what model SSD?
  5. NVMe device dropped offline, power cycling the server (not just rebooting) should bring it back, sometimes this helps with this issue: Some NVMe devices have issues with power states on Linux, try this, on the main GUI page click on flash, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (on the top right) and add this to your default boot option, after "append" and before "initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 Reboot and see if it makes a difference.
  6. That mostly depends on the hardware used and pool config, I have a 6 disk RAID5 pool and get around 350MB/s sustained writes.
  7. Pools are still part of the user shares, any top folder in a pool is a share.
  8. Then don't have other suggestions, other than using different hardware.
  9. First link has alternative ways of configuring dockers.
  10. 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.
  11. See here for some recovery options: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490
  12. If safe mode is working it's likely a plugin, uninstall them all.
  13. Then it's most likely a hardware issue, look for a BIOS update if you don't already
  14. 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/
  15. First fix that then see if it solves the problem, don't see any reasons for the crashing logged.
  16. 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/
  17. 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
  18. 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.
×
×
  • Create New...