Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,831

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    It's normal with some SMR drives, it will show correct speed once the drive is fully written once.
  2. JorgeB
    Please post after the rebuild, before it's just all invalid partitions, need to see how it is after.
  3. JorgeB
    Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  4. JorgeB
    See if this applies to you, if yes, upgrading to v6.10 and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), or see below for more info.: 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/
  5. JorgeB
    Aug 30 04:40:02 Tower kernel: FAT-fs (sda1): Directory bread(block 537257) failed Aug 30 04:40:02 Tower kernel: FAT-fs (sda1): Directory bread(block 537258) failed Aug 30 04:40:02 Tower kernel: FAT-fs (sda1): Directory bread(block 537259) failed Aug 30 04:40:02 Tower kernel: FAT-fs (sda1): Directory bread(block 537260) failed Aug 30 04:40:02 Tower kernel: FAT-fs (sda1): Directory bread(block 537261) failed Flash drive problems, you can try backup and reformatting it, also make sure it's using a USB 2.0 port, if issues continue replace it.
  6. JorgeB
    Lets see it @bonienlcan take a look.
  7. JorgeB
    Not sure why network-rules is not being created, try renaming/deleting network.cfg also and reboot.
  8. JorgeB
    Yes, and that's from the UD plugin, not Unraid.
  9. JorgeB
    Please post the diagnostics.
  10. JorgeB
    Diags are after rebooting so we can't see what caused the errors or the rebuild, likely some controller/power issue to cause them in multiple disks, you also need to check filesystem on disk6, possibly the result of the errors during the rebuild.
  11. JorgeB
    This is a known issue that will happen when you have a single array device formatted with btrfs, parity will have an invalid btrfs filesystem that causes issues during btrfs device scan for the pools, solution for now would be to format disk5 with xfs like the remaining devices or if you really want btrfs for that device you can use encrypted btrfs.
  12. JorgeB
    Disk3 is failing and since old parity was also overwritten you need to copy everything you can from that disk to other(s), alternatively you can use ddrescue to clone the disk and recover as much as possible.
  13. JorgeB
    Syslog stopped writing because of spam, cannot see what happened after switching the disks to the onboard controller, please reboot and post new diags after array start.
  14. JorgeB
    You can go to Settings - Network Settings - Interface Rules to reassign the NICs, If that doesn't work delete network-rules.cfg and reboot, then go there again.
  15. JorgeB
    Parity check after an unclean shutdown is normal, not so normal taking over 3 days, please post the diagnostics.
  16. JorgeB
    Disk is showing some SMART issues, though the tests passed, I would still recommend swapping with a different disk to completely rule out the cables, if it happens again you know it's the disk.
  17. JorgeB
    Check/replace cables on parity disk.
  18. JorgeB
    Please post the diagnostics.
  19. JorgeB
    Most likely, and it's not a lack of bandwidth problem, that could be the problem if the check started say at 180/190MB/s and after a couple of hours it was still going at that speed.
  20. JorgeB
    HBA links are OK, expander is also using dual link Something else is the problem, is 116.5MB/s the average speed or the starting speed? i.e., if you start a parity check a what speed does it start? Make sure nothing else is using the array.
  21. JorgeB
    Disk dropped offline, so there's no no SMART, but it's not logged as a disk problem, swap cables/slot with a different disk and see if the problem follows the disk. Also having what look like power/connection issues with cache2, check/replace cables.
  22. JorgeB
    Check the HBAs link speed and with, you can do that with lspci -d 1000: -vv Also check that the expander is using dual link cat /sys/class/sas_host/host1/device/port-1\:0/sas_port/port-1\:0/num_phys if it's not host1 you need to adjust the command, e.g. for host7 it would be cat /sys/class/sas_host/host7/device/port-7\:0/sas_port/port-7\:0/num_phys Output of 8 means dual link, 4 means single link, you can also post the diags if you want me to check the correct host for you.
  23. JorgeB
    If you are getting lower speeds than that during rebuilds/parity check HBAs are not the problem.
  24. JorgeB
    Yes, around that.
  25. JorgeB
    Those are PCIe 2.0, a PCIe 3.0 model connected to the expander with dual link would increase total bandwidth from the currently usable 3GB/s to 4.8GB/s, assuming of course the board/CPU supports PCIe 3.0.
×
×
  • Create New...