Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,600

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/
  2. JorgeB
    Mellanox ConnectX-3 don't run very hot, still need some cooling over them, or at least a case with good airflow.
  3. JorgeB
    Error appear to always be during spin up, try the fix or see if disabling spin down for that disk helps.
  4. JorgeB
    Yes, and they are usually the most reliable controller you can use with Unriad, other than the onboard Intel SATA ports, but with some specific issues/hardware there can be issues.
  5. JorgeB
    It's been happening for some time but just to a few users, full reason why is still unknown to me, low performing SSDs can exacerbate the issue, and sometimes using faster ones helps, but not always.
  6. JorgeB
    Do the other drives perform normally?
  7. JorgeB
    GUI doesn't currently support SMART tests for SAS devices.
  8. JorgeB
    These are normal, machine checks events are a hardware issue, mcelog might have more info.
  9. JorgeB
    We just need the last diags created automatically by Unraid when you last rebooted, do you which ones are those?
  10. JorgeB
    In my experience Kingston A400 is probably one of the worst SSDs you can buy, they are slow when new and tend to get progressively slower with use, avoid those and any other DRAMless TLC SSD, I would recommend trying with decent SSDs, like the 860/870EVO, MX500, WD Blue or similar.
  11. JorgeB
    Sorry no, not something I need for now, though I might look into that in the future.
  12. JorgeB
    Logs looks clean now, for some reason your hardware is not liking spin down, hough it's not the first time an LSI HBA has some issues with spin down.
  13. JorgeB
    Those don't help to diagnosing an unclean shutdown, the only ones that can help are the diags saved by Unraid in the logs folder.
  14. JorgeB
    Yep, dockers directly manipulating files seems to be one of the reasons for this.
  15. JorgeB
    Try rebooting again, if it keeps happening post on the linked thread, it might help LT get to the bottom of the problem if it's easily repeatable.
  16. JorgeB
    It already happened again, the error you seeing is this issue, though when it happens it usually only happens after hours or days.
  17. JorgeB
    This.
  18. JorgeB
    If the disks are known to be good you can do a new config instead. As for the shares, this was the problem: Apr 15 16:05:20 35Highfield shfs: shfs: ../lib/fuse.c:1451: unlink_node: Assertion `node->nlookup > 1' failed. AFAIK only solution is rebooting.
  19. JorgeB
    There have been other reports of very bad performance with that specific model, just with some, not all, so it's not just because they are SMR, if the other disks are performing nominally you should replace it, or exclude it from writes.
  20. JorgeB
    Default is auto, and since there's no data, disk share is enable.
  21. JorgeB
    Nope.
  22. JorgeB
    Have several of these with the same switch, both single and dual port, they work great with DAC or fiber patch, and are pretty cheap.
  23. JorgeB
    Please start a thread in the general support forum and attach the diagnostics: Tools -> Diagsnotics
  24. JorgeB
    It's possible.
  25. JorgeB
    Reboot, if still issues please post new diags.
×
×
  • Create New...