• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by trurl

  1. When it happens again click the Compute All button as seen in your first screenshot to see how much of each disk each user share is using.
  2. Remove My Servers plugin
  3. This is the wrong way to think about parity. Any bad drive in your array puts data at risk. Parity by itself cannot rebuild anything. Parity PLUS ALL other disks is required to rebuild a failed disk.
  4. Also you might consider doing memtest.
  5. USB connections are often unreliable and if a disk disconnects it will have to be rebuilt. This may be a frequent occurrence. Also, parity operations need to happen in parallel, so if disks are sharing a single connection performance will be severely impacted.
  6. Sounds like a hardware problem. How are your power and cooling?
  8. You can change the Mover schedule, but Mover is intended for idle time. Just write directly to the array and it will already be protected by parity.
  9. 3TB is the correct answer for your configuration: You would need to use Single mode to get full capacity from different sized disks:
  10. It is impossible to move from cache to array as fast as you can write to cache, so if you intend to write more than cache can hold, don't cache.
  11. The Diagnostics are a single ZIP file. Please don't post the contents of the ZIP, just the complete ZIP
  12. Run an extended SMART test on that disk.
  13. Have no idea what you mean here. The user shares are just another view of the disks, there are no pointers involved.
  14. What is doing the moving? Is it moving from another share on cache? You may need to copy to destination share then delete from source share since linux might just be "renaming" to a new path on the same disk instead of actually moving.
  15. What I meant was that a Windows update might have caused the problem, not that it would be expected to fix a problem. Windows is always "adding security". I noticed you didn't have Dynamix Local Master plugin installed. That and other things mentioned in that thread I linked might help.
  16. This is "surprise" scenario #2 mentioned in the post linked below. Make sure you are also aware of "surprise" scenario #1.
  17. You don't want to even run a system that has any memory problems. Everything your system does goes through RAM, your data, the OS, EVERYTHING.