Niklas

Members
  • Posts

    320
  • Joined

Everything posted by Niklas

  1. I had this now and then before replacing all sata-cables in the server. No increase since.
  2. Thanks for the suggestion. Already ingested that and yes, understanding second parity make my brain hurt.
  3. Yes, i know. I have some deeper understanding when it comes to sectors and how storage devices work. Just not much experience with parity calculation in Unraid. Yet. Found Unraid in nov-oct 2018 and have been reading and watching videos about parity (in unraid) so.. I'm learning as i go.
  4. I know. I was brainstorming about the system TREATING the newly formatted disk as "clear". Not that it IS "clear". I hope that I'm clear about what I was thinking, even if it was wrong. English is not my first language.
  5. I understand, thanks. Never used pre-clear but I have been reading lots about it. Just cant remember that I have seen the disk clearing before and I have added and removed drives several times. The thing is that I could have done it before I added the parity drive. I need to pre-clear my brain I think. Got my original question well answered now. Thanks!
  6. What I mean is that an empty disk (newly formatted) could be seen as clear (all sectors as zeroes). But that is just a theory of mine and how I thought it worked. (without deep knowledge)
  7. I was under the impression that Unraid could use the new drive directly if it was newly formatted (by Unraid, no data = 0). The drive I have added in the past has been unformatted brand new. I started to use Unraid when pre-clear was not a thing anymore. But I also started with no parity and one data drive.
  8. I see. My memory is not what it used to be I think. Thanks.
  9. So, when adding new disk Unraid started disk clearing. Is this new in 6.7 or did this happen with 6.6.x? Can't remember it happening before.
  10. I had 3 encrypted drives (all my stuff still fits on 1 disk, 4TB). Moved everything and formatted the drive without encryption. Moving over to IronWolf so for now, I have 1 unencrypted and 1 encrypted drive.
  11. Btw. Another thing. I am streaming from disk1 but ui shows all disks as spun down. Writing to disk1 show parity and disk1 spun up. My array is not encrypted for the time being. Going to switch back when the problem is fixed.
  12. 20% free ram used for cache. That's why I got full speed until ram cache was full.
  13. Do you use cache? I do so my dockers and data is on ssd cache. Not much writing to array
  14. Unraid caches the transfer in ram (20%). When you stop the transfer, unraid is busy writing the content in ram to array. You can see the write going on for some time after stopping the file transfer. Until ram is empty i guess. Well, to my understanding.
  15. I guess time out can happen if Unraid is busy with writing files to the array. Transferring files using SMB made the Unraid UI and some dockers very slow. Browsing network shares was not possible until the content in ram was written to disk.
  16. My read speed was ok. Don't know if it was normal but not 10-15MB/s. I can't check now. My array is not encrypted until this problem is solved.
  17. My server reported 200 (and more) avg load when writing data. CPU at low usage but yeah, the load was crazy.
  18. You will have two files. To my knowledge, Unraid will use the first file found (on disk1 i guess) when you have two of the same on several disks.
  19. Good to know. This is to encrypted btrfs (SSD). Small dips where ram is writing to disk (i guess). The problem seem to be limited to the array or enc xfs.
  20. My controller is IBM M1015 crossflashed to LSI9211-IT. I don't think it is a controller problem. I'm getting full speed to drives that is unencrypted xfs.