Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,521

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    The Intel SAS controller sometimes has some issues with Linux, unlike the Intel SATA ports which are rock solid, if you can try for example using an LSI HBA instead.
  2. JorgeB
    Looks more network related,try to simplify you lan config as much as possible, also that doesn't show the beginning of the trace, but if using custom IP addresses for docker see here:
  3. JorgeB
    This should definitely be updated, all p20 releases except 20.00.07.00 have known issues.
  4. JorgeB
    Parity swap is not needed for that, just do a standard replacement.
  5. JorgeB
    Yes, I wanted to see a syslog with multiple parity checks, before rebooting, that Marvell controller doesn't usually cause sync errors, but it's a possibility, and like mentioned not recommended anyway.
  6. JorgeB
    You don't need to delete anything, if it's unmountable as cache just format.
  7. JorgeB
    Any controller with SATA port multipliers is not recommended, Marvell controllers are also not recommended, even without port multipliers, if 5 ports are enough you can get a JMB585 based controller, if you need more look for an LSI HBA.
  8. JorgeB
    The extra controller you have is a 2 port Asmedia controller with SATA port multipliers to give the 6 or 10 total ports, these are a known problem and will cause constant timeouts, you should replace it.
  9. JorgeB
    For this last case yes, my issue was without a check running, a fan in a 5in3 cage just stopped.
  10. JorgeB
    That only helps if it's doing a parity check.
  11. JorgeB
    Please post the complete diagnostics instead: Tools -> Diagnostics
  12. JorgeB
    Aah, my first ever request, should be implemented soon™
  13. JorgeB
    This suggests a LAN problem, try different NICs, cables, switch, source computer, etc, you should get very close to line speed with iperf on gigabit.
  14. JorgeB
    It does, but if I do the procedure like you specified above I still get the same result, i.e., "wrong" disk after a reboot and an unmountable damaged partition.
  15. JorgeB
    Constant ATA errors on disk10, looks more like a cable problem, check/replace cables and try again.
  16. JorgeB
    You also add the 2.5GbE IP the the Windows hosts file, if that's the OS you're using.
  17. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  18. JorgeB
    Please post the diagnostics, you can get them by typing "diagnostics" on the console.
  19. JorgeB
    This is a different problem than above, try to format the device in the cache slot, if it fails please post the diagnostics: Tools -> Diagnostics
  20. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  21. JorgeB
    Do you mean 170Mb/s or do you have 10Gb Ethernet?
  22. JorgeB
    Diags are after rebooting so not much to see, if it happens again post new diags before rebooting.
  23. JorgeB
    You didn't post the persistent syslog like asked, thigh might give a clue, if there's nothing there it's likely a hardware problem.
  24. JorgeB
    You could have used this thread but already replied on the other one.
  25. JorgeB
    Run it again without -n or nothing will be done, if it asks for -L use it.
×
×
  • Create New...