Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,406

  • Joined

  • Last visited

  • Days Won

    705

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Btrfs error is not a problem, don't know why but it happens sometimes, it's just warning that the mdX and sdX device are the same filesystem. Don't see any reason on the log for the server to be stuck, try rebooting in safe mode with any dockers/VMs also disable.
  2. JorgeB
    Yes
  3. JorgeB
    If the GUI doesn't work you can try getting the diagnostics from the console, by typing "diagnostics"
  4. JorgeB
    Last check was already correct, no next one should find 0 errors.
  5. JorgeB
    Parity is only for the array, so can't be that, I would suggest running a couple of more checks, if there are more errors there's definitely a problem.
  6. JorgeB
    You'd need to provide the diagnostics after updating.
  7. JorgeB
    That's normal, any unclean shutdown since previous check?
  8. JorgeB
    Those errors appear to be normal for that board and likely unrelated to any other issues:
  9. JorgeB
    Only thing I can see in the logs for now is an overheating CPU, fix that then post clean diags.
  10. JorgeB
    Check/replace cables for parity.
  11. JorgeB
    Errors on sda suggests possible flash issues, but unlikely that would make the server crash, that still looks like a hardware problem to me, possibly board/cpu combo.
  12. JorgeB
    You should start by running memtest, also check replace cables on parity2
  13. JorgeB
    Either way works, whatever you prefer. Don't need to, but should, or performance for both things will be very affected.
  14. JorgeB
    Macvlan call traces are usually related to dockers with a custom IP address. But the crashes without anything logged suggest more a hardware issue.
  15. JorgeB
    You could try safe mode without dockers/VMs, if it still crashes it's likely a hardware problem, you can also downgrade back to the last known working release, again if it keeps crashing likely a recent hardware issue. Most call traces on the first syslog are network/NIC related (or at least they mention them), so it might be worth simplifying the lan and/or using another NIC to see if it helps.
  16. JorgeB
    Using another PSU would also be a good idea to rule out power issue.
  17. JorgeB
    Easiest way would be to test with another controller, but you could test that controller on another computer if possible.
  18. JorgeB
    Looks more like a connection/power issue, but it can be the controller.
  19. JorgeB

    Sync Errors

    JorgeB replied to Mogo's topic in General Support

    That's fine and hot hard drives won't make a server reboot, overheating CPU, PSU might. See the PSU thread.
  20. JorgeB
    Shares will already work, except the data on the missing disk will be missing from any share it uses, as well as any share(s) that use that disk only.
  21. JorgeB
    Without old disk3.
  22. JorgeB
    Can't say, whatever happened it happened before this boot, it won't hurt to run memtest.
  23. JorgeB
    Any free RAM on Linux is used for cache, and that's not reflect on that graph.
  24. JorgeB
    Cache filesystem is corrupt, best bet is to backup, re-format and restore the data.
  25. JorgeB
    You'll need to do another new config to reset the array, then post new diags if there are more errors.
×
×
  • Create New...