Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,416

  • Joined

  • Last visited

  • Days Won

    705

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    ^This
  2. JorgeB
    Due to cache running out of space the docker image got corrupted, but it's easy to re-create.
  3. JorgeB
    It's normal with recent xfs drives, it uses adicional space for new functions, like reflinking.
  4. JorgeB
    I don't use encryption, it's up to you if you think you need it or not.
  5. JorgeB
    With Windows they should work on the same segment if you prefer.
  6. JorgeB
    Sorry, no idea then, I use multiple connections, but form a single Windows desktop to multiple Unraid servers, and some servers connect to my desktop with one port and to another Unraid server with the other.
  7. JorgeB
    In this case both mirros are corrupt, or it would be automatically fixed. That looks more like corrupt metadata, but any corrupt data can be identified by a scrub, it will also result in an i/o error if you try to read/copy that file.
  8. JorgeB
    Delete/rename network.cfg and network-rules.cfg, both on flash/config, then reconfigure.
  9. JorgeB
    Try to mount the disk with the unassigned devices plugin and then post the diagnostics: Tools -> Diagnostics
  10. JorgeB
    Should work like that, can machine2 access the shares if you connect it to the other port, using machine 3 settings?
  11. JorgeB
    Please use one of the existing Wireguard threads. e.g.:
  12. JorgeB
    Cache is completly full, free up some space.
  13. JorgeB
    Yes, the missing drive needs to be removed. You can try running a scrub, with the pool mounted, but might not work during the balance.
  14. JorgeB
    Sorry, don't understand the question, like mentioned only you can know how much space you'll need on cache depending on what you're planing to use it for.
  15. JorgeB
    No, we'd need to see the diags from when the disk failed, or at lest its SMART report. I would.
  16. JorgeB
    Secondary or primary port, whichever connects to machine 1, but yes.
  17. JorgeB
    Ahh, that makes more sense, in that case flashing should work correctly, and firmware 20.00.00.00 has known issues, though link speed is not one of them. If you can't flash with Windows try booting with a DOS flash drive, or try flashing it in a different board, older boards are better for DOS flashing, Windows flash should work basically everywhere, never had issues.
  18. JorgeB
    Errors are logged as if they are an actual disk problem, but this type of errors can sometimes be intermittent, wait for the extended test to finish, if it fails disk needs to be replaced.
  19. JorgeB
    There's no set recommended size, it just depends on how much space you need on the pool, if it's just for dockers 120GB is plenty enough.
  20. JorgeB
    If it crashes before the rebuild it will almost certainly crash after the rebuild, though I was expecting reiserfsck to find some corruption.
  21. JorgeB
    It's probably not using LSI firmware, which wouldn't surprise me since AFAIK LSI firmware never shows link speed/width at boot, though still likely unrelated to x4 link.
  22. JorgeB
    A redundant cache pool, you need at least 2 devices.
  23. JorgeB
    You can Can't use same network/segment for both, e,g machine 1 - 10.10.20.1 / 10.10.30.1 machine2 connects to machine 1 with 10.10.20.2 machine3 connects to machine 1 with 10.10.30.3
  24. JorgeB
    In that case it's normal that any shares that have data on cache will show as unprotected, i.e., won't survive a device failure.
  25. JorgeB
    Depends on where they are, if you have parity and if the cache is or not a redundant pool.
×
×
  • Create New...