Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,386

  • Joined

  • Last visited

  • Days Won

    705

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    That issue should be gone with v6.8, it's about to go final, though rcs are perfectly safe to use.
  2. JorgeB
    Ohh, I missed this, format is never part of a rebuild, it deletes all data on the disk and updates parity. The correct way to fix your problem would be to check filesystem, not rebuild. Now, only option is to restore from backup or use a file recovery util like UFS explorer.
  3. JorgeB
    Disk looks fine, just check file system.
  4. JorgeB
    Check file system on disk6 https://wiki.unraid.net/Check_Disk_Filesystems Next time please post complete diags (tools -> diagnostics)
  5. JorgeB
    Yes, you can also use the onboard SATA ports for any SSD, LSI SAS3 models, like the 9300-8i support trim, but only on the devices with determinist trim, you can check with: OK for LSI hdparm -I /dev/sdc | grep TRIM * Data Set Management TRIM supported (limit 8 blocks) * Deterministic read ZEROs after TRIM Not OK for LSI hdparm -I /dev/sdb | grep TRIM * Data Set Management TRIM supported (limit 8 blocks)
  6. JorgeB
    There's a known issue with LSI SAS2 models and trim with latest firmwares (>p16), the only strange thing here is that trim it is working on the cache devices, more so since it should never work on the 850 EVO as LSI requires deterministic read zeros after trim for trim to work, 860 EVO would be OK, maybe the mixed pool is confusing it?
  7. JorgeB
    Disk3 is failing, but like mentioned if you can get disk2 back it will allow you to replace disk3, try connecting disk2 using different cables, swap with disk3 for example, both power and SATA cables.
  8. JorgeB
    SMART test failed = failed disk, you should replace it.
  9. JorgeB
    Ryzen on Linux can lock up due to issues with c-states, make sure bios is up to date, then look for "Power Supply Idle Control" (or similar) and set it to "typical current idle" (or similar), or completely disable C-sates. More info here: https://forums.unraid.net/bug-reports/prereleases/670-rc1-system-hard-lock-r354/
  10. JorgeB
    Disks won't mount in maintenance mode.
  11. JorgeB
    To me looks more like a disk problem, not necessarily bad disks but something related to them, do you have a different model disk you could try, maybe even a couple of old SATA disks just to test?
  12. JorgeB
    Controller problem again: Dec 6 13:19:53 Tower kernel: mpt2sas_cm0: SAS host is non-operational !!!! Errors in multiple disks, no point in continuing the sync.
  13. JorgeB
    If using v6.7.x try again with v6.8-rc
  14. JorgeB
    Ryzen on Linux can lock up due to issues with c-states, make sure bios is up to date, then look for "Power Supply Idle Control" (or similar) and set it to "typical current idle" (or similar), or completely disable C-sates. More info here:
  15. JorgeB
    Yep.
  16. JorgeB
    *Should* be fine, as long as parity1 slot is used, when sync is done do a new config and check "parity is already valid" before starting the array. Alternatively clone the disk with dd then do a new config and also trust parity.
  17. JorgeB
    This should be post on the preclear plugin support thread.
  18. JorgeB
    Only for metadata, i.e., you'll lose data if one of the devices fails.
  19. JorgeB
    And current diags please, grabbed after array start.
  20. JorgeB
    So that we're clear, formatting would delete any new and old data, i.e. all existing data on disk2.
  21. JorgeB
    Format is never a an option, unless there's no data on disk2, after a format data can't be recovered from parity, seems to be a common misconception. You could try fixing the filesystem on the emulated disk2 first and if successful rebuild, but since there can be some corruption, and assuming nothing was written to disk2 once it got disabled, doing a new config with IMHO be the way to go.
  22. JorgeB
    👍
  23. JorgeB
    It was a controller problem: Dec 6 06:22:09 Tower kernel: mpt2sas_cm0: SAS host is non-operational !!!! Mmake sure it's well seated and sufficiently cooled, you can also try a different PCIe slot if available. As for the disabled disk either rebuild on top if the emulated disk is mounting correctly and data looks fine, or, and assuming nothing was written to it after it got disabled, do a new config and resync parity.
  24. JorgeB
    That's good enough for me, I don't really mind when users don't say thank you, I do appreciate when people at least respond to say if it helped or worked.
  25. JorgeB
    Not sure I understand the question, just start the array.
×
×
  • Create New...