Jump to content

JorgeB

Moderators
  • Posts

    67,572
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Data corruption and lots of segfaulting suggest a hardware issue, start by running memtest.
  2. Please post the diagnostics: Tools -> Diagnostics
  3. Server Is running out of RAM, most likely some docker.
  4. Yep, but most likely it's an expander bakplane.
  5. Those are checksum errors, it means data is getting corrupt, please post the diagnostics: Tools -> Diagnostics
  6. Then it's correct, as long as the share exists on cache it will be included in the total capacity.
  7. Unrelated but for best performance I would use on the non SMR disks (EFRX) for parity, of course it will only make a difference when writing to a non SMR disk also, but like that it can be slower even when writing to one.
  8. Never a good sign, and there are some recent issues, if you haven't checked parity for a week or so you should run an extended SMART test.
  9. It wasn't assigned before rebooting, looks like the clear was canceled, so it was never really assigned to the array, I have no idea what could cause this, never seen it before, best to create a bug report, add both diags again.
  10. This is a strange one, re-assign cache, grab diags before rebooting, then reboot in safe mode, if it happens again grab new diags and post both.
  11. JorgeB

    Drive Read errors

    Check/replace both cables.
  12. JorgeB

    Drive Read errors

    Looks more like a connection/power problem, but also make sure you update the LSI firmware to latest, you can do that using Unraid.
  13. JorgeB

    Drive Read errors

    Diagnostics are under Tools -> Diagnostics
  14. Spin down doesn't cause sync errors, running Ryzen with out of spec RAM can, see here.
  15. You can use this to see usable space. That is unrelated, it depends on the settings, use cache must be set "Yes" (or "Prefer") and the minimum free space for both cache and share need to be correctly set.
  16. Updating will fix the wrong available space being reported, it won't fix the pool being full.
  17. If you're using v6.8 it's a known issue, fixed on v6.9, usable space on cache using the default profile will be 250GB.
  18. JorgeB

    Drive Read errors

    Please post the diagnostics after there are errors and before rebooting.
  19. There should be a sticker with the model on the back of the backplane, e.g. BPN-SAS3-826EL1
×
×
  • Create New...