Jump to content

trurl

Moderators
  • Posts

    44,353
  • Joined

  • Last visited

  • Days Won

    137

Everything posted by trurl

  1. Do you have Community Applications plugin (the Apps page) installed?
  2. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
  3. Please respond to my post just above yours.
  4. Hey "Advanced Member", I am guessing by "Constructor", you mean me. I don't recall ever saying that. I often advocate for fewer larger disks rather than more smaller disks because each additional disk is an additional point of failure. Ideally, parity operations happen in parallel. If your hardware can't support accessing all disks simultaneously, it will be slower. Do you have a port multiplier?
  5. Go to Windows Control Panel, Credential Manager, and delete any Unraid credentials so they can be renegotiated. Then, be sure to try to access the private share before trying to access any other share. With Windows, you only get one login per network resource and you must make sure that one login is the one needed for the private share. Windows won't use another login even if it prompts you.
  6. What speed is it giving now? I usually expect 2-3 hours per TB of parity.
  7. Is your goal to end up with only 1x8TB parity plus 2x8TB data? Shrinking the array is a little more complicated and some ways may be more efficient than others. How full are your existing disks?
  8. The usual way to upsize disks is to replace and rebuild, one at a time. You will have to start with parity.
  9. If you have dual parity, then if one parity is missing, you are still protected from one failure by the other parity.
  10. I think unclean shutdown parity check is no correct. Syslog will tell if you haven't rebooted. Post Diagnostics if you want us to take a look.
  11. The only way to maintain parity throughout requires another disk
  12. Parity is always "full". Better to not even think of it as "data". It is just a bunch of parity bits and parity check always checks all of them.
  13. Parity2 is known to require more CPU. Was it working OK with dual parity and now it isn't?
  14. Since these are important files I assume you have backups. So why not just keep them on cache?
  15. Is that the full text of the error? Post your docker run as explained at this very first link in the Docker FAQ:
  16. The proper place for your question is in the thread you already posted in. In any case, you shouldn't post in multiple threads about the same problem. How can we coordinate responses when you have multiple threads going? Go back to that other thread and ask again. Locking this one.
  17. I found the other thread you were talking about, but it was never determined what the problem was since we got involved after you had already done some things and we never asked for more information. Bad connections are far, far more common than bad disks. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
×
×
  • Create New...