Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,519

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Syslog is spammed with these: Sep 23 04:40:12 Tower kernel: bond0: (slave eth0): An illegal loopback occurred on slave Sep 23 04:40:12 Tower kernel: Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports Sep 23 04:40:13 Tower kernel: bond0: (slave eth1): An illegal loopback occurred on slave Sep 23 04:40:13 Tower kernel: Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports Check and fix network config
  2. JorgeB
    This is obviously not a general problem, and if we can't reproduce it's difficult to find where the problem is.
  3. JorgeB
    What I do in this cases is to search the syslog for "thread", this will find all parity check/sync/rebuilds info, since they all start with "md recovery thread"
  4. JorgeB
    If you restore the config fodler will also have the disk assignments, and the docker templates.
  5. JorgeB
    Start by running a single stream iperf test.
  6. JorgeB
    You can try cloning it with dd, but if there are errors rebuild from parity.
  7. JorgeB
    Not if the disk is really failing, it can't correct any read errors, best to just do a standard rebuild.
  8. JorgeB
    Rebuild was successful, error was from a corrected block on parity2: Sep 12 18:17:05 Tower kernel: md: recovery thread: Q corrected, sector=128 I would ignore for now, but keep an eye on it, any more sync errors (without a reason like from an unclean shutdown) might indicate a hardware issue.
  9. JorgeB
    HBA is crashing and keeps re-initializing: Sep 22 09:10:01 BMS kernel: mpt2sas_cm0: fault_state(0x2665)! Start by updating the firmware since it's on a very old one: Sep 22 09:10:03 BMS kernel: mpt2sas_cm0: LSISAS2008: FWVersion(02.15.63.00) Current one is 20.00.07.00
  10. JorgeB
    We can't do that on this forum, we can only recommend a post so it appears at the top, but only mods can do that, though it's really not a solution in this case, but I'll do it in case another user has the same issue before it's fixed and finds this thread.
  11. JorgeB
    If the pool is redundant you just need to remove that device, then assign another one later.
  12. JorgeB
    That already is a massive problem.
  13. JorgeB
    👍
  14. JorgeB
    Yes, single parity protects from a single missing disk.
  15. JorgeB
    Correct.
  16. JorgeB
    https://wiki.unraid.net/Un-Official_UnRAID_Manual#High_Water
  17. JorgeB
    New config allows to reconfigure the array devices keeping the existing data. So, tools -> New config - re-assign both disks (make sure not to assign a data disk to a parity slot) with disk2 using a SATA port and start the array, if both disk mount you're done, if disk2 doesn't mount, repeat the procedure with disk2 back in the USB enclosure, you'll then need to empty it before using a SATA port.
  18. JorgeB
    Try just the new config first, if it works you won't need to do anything else.
  19. JorgeB
    You'll need to do a new config because of the different ID, and if the partition created by the USB enclosure is non standard it might still not work.
  20. JorgeB
    This will only happen to very few users, and most of those cases the problem was already in the pool, just undetected.
  21. JorgeB
    Disk3 does appear to be failing, so replace that one first, you can use the parity swap procedure. CRC errors are usually not a disk problem.
  22. JorgeB
    CRC is a connection problem, as long as it doesn't keep increasing issue is resolved.
  23. JorgeB
  24. JorgeB
    There are some known issues with some Samsung SSDs and AM3 chipsets, you could use a different controller, e.g. a 2 port Asmedia.
  25. JorgeB

    RO USB

    JorgeB replied to Spritzup's topic in General Support

    You don't need to wait for Limetech, key replacement is automatic.
×
×
  • Create New...