Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,572

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    You can also look for the the 6 port Asmedia ASM1166, but make sure it's that chip, there are some 6 port models that use the 2 port ASM1161 and a SATA port multiplier, and those are no good.
  2. JorgeB
    Try booting in safe mode.
  3. JorgeB
    This would be better asked in the preclear support thread, but looks like it aborted due to low memory.
  4. JorgeB
    Start a transfer to the array with turbo write enable and grab the diagnostics after the transfer slows down.
  5. JorgeB
    Did you reboot before?
  6. JorgeB
    Do this: With the array stopped, if Docker/VM services are using the cache pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), re-enable Docker/VMs if needed, start array.
  7. JorgeB
    You can boot using GUI mode to reconfigure the LAN, if that's not possible delete network.cfg and network-rules.cfg on /boot/config and reboot.
  8. JorgeB
    This an Unraid issue, not btrfs, corrected on v6.9, though if you have an odd number of devices using raid1 it will still be wrong, and that is a btrfs issue.
  9. JorgeB
    The ebay link doesn't mention the backplane model, nor can I see by the photos, but most likely it's an expander backplane, so you need an HBA.
  10. JorgeB
    Best bet is to backup. re-format and restore data.
  11. JorgeB
    Try this and then post the log. P.S. cache fs is corrupt, likely because of all the crashing.
  12. JorgeB
    No errors logged, just let it go on for now.
  13. JorgeB
    How many drives on the chassis? If more than 8 it has an expander backplane, so you'd need a SAS HBA to connect it.
  14. JorgeB
    That rules out the expander, do you have cables to connect some of the drives to the onboard SATA controller, to rule out the HBA?
  15. JorgeB
    They will all work, just need the correct cables.
  16. JorgeB
    It's a problem with parity2, replace both cables.
  17. JorgeB
    Of the drives you currently have these are SMR: ST5000DM000 and ST8000DM004
  18. JorgeB
    Not that I know of.
  19. JorgeB
    Yep.
  20. JorgeB
    Parity and Parity2 are SMR, you could replace them with the the WDs and then try the same transfer to another WD (or other non SMR drive).
  21. JorgeB
    You posted: Didn't even notice it is the full diags, that is enough.
  22. JorgeB
    And it throttled to the same 24MB/s?
  23. JorgeB
    Please post the full diagnostics instead, grabbed during a transfer.
  24. JorgeB
    lol, did you fall asleep on the keyboard?
  25. JorgeB
    Unlikely to be a disk problem, could be power, controller, expander, etc, I would first try not using the expander, you won't be able to use all the drives but do it for testing.
×
×
  • Create New...