Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,884

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    You could try a different OS to rule out any driver issues.
  2. JorgeB
    If you can now see the NICs in the GUI and they work you can ignore the error.
  3. JorgeB
    If you assign it to an Unraid pool it will start using v2, then it's a good idea to delete v1 cache again.
  4. JorgeB
    Yep.
  5. JorgeB
    It's a strong possibility.
  6. JorgeB
    And don't expect 500MB/s, 300MB/s would be a good result, possibly more depending on the rest of the hardware.
  7. JorgeB
    Should be about the same, if using identical devices.
  8. JorgeB
    MX500 and 870EVO are good options, Samsung should be slightly faster.
  9. JorgeB
    Because you are are using Kingston SA400, which are some of the slowest SSDs available, not all SSDs can sustain 500MB/s writes, if fact most can't, unfortunately I missed that your array also won't be very fast since there's a 1TB disk, but pretty sure you are seeing low speeds due to device limits, that's why it starts reasonably fast, while it's being cached to RAM then it slows down when it's limited by the device write speed.
  10. JorgeB
    Looks like it stalled, pleas post new diags to confirm.
  11. JorgeB
    Not familiar, might be easier to update using a Windows desktop, if you have one available.
  12. JorgeB
    Look like it's not correct since it's removing that line from the diags and emttp is still not starting, extract the default go file from a download zip and use that one.
  13. JorgeB
    Your go file is incomplete, add to the beginning: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & And reboot
  14. JorgeB
    That might just be a device limitation, enable turbo write and transfer directly to the array, you should get >100MB/s
  15. JorgeB
    Please post the diagnostics, you can get them from the console.
  16. JorgeB
    That should be reported in the existing plugin support thread: https://forums.unraid.net/topic/97351-plugin-spin-down-sas-drives/
  17. JorgeB
    Update the LSI firmware to 20.00.07.00, all other p20 releases have known issues.
  18. JorgeB
    Look for a firmware update for the NICs.
  19. JorgeB
    Doesn't look like a disk problem, reboot and post new diags after array start.
  20. JorgeB
    Rebooting and starting the array is not a high stress operation, parity dropped offline, check/replace cables and post new diags after array start.
  21. JorgeB
    Looks like this isse:
  22. JorgeB
    Nothing relevant logged, this usually points to a hardware issue, start by running memtes, if you have a different PSU you could test with it might also be a good idea.
  23. JorgeB
    Looks like a drive problem, it's producing a corrupt SMART report.
  24. JorgeB
    Leaving a browser window opened on an Android device is known to cause issues, when the device is sleeping.
  25. JorgeB
    I would recommend deleting and recreating the docker image, very easy to do and it can make a difference.
×
×
  • Create New...