adrian ballard

Members
  • Posts

    54
  • Joined

  • Last visited

Everything posted by adrian ballard

  1. Fresh 6TB drive, formatted to XFS, new share built. Wrote 5.75TB to drive in 2 different ways: straight to drive - D13\Omega through the share - Omega Both worked without incident so it looks like the old share had indeed become corrupted. Thanks for all the help...
  2. renamed the share to 'butter'. tried to copy 40+ GB file to d12\butter and it failed. I'm going to load a fresh 6TB drive (formatted to XFS) and setup a new share. Then I'm going to try a move 5TB of data to it to see what happens. This may take a while so I'll post back with my results as soon as it finishes.
  3. So I went ahead a copied another 40+ GB file to 'test share' and it copied no problem. Then I tried to copy the same file to d12\Movies - ISO again and it triggered the error.
  4. Correct on all points except my share name is 'Movies - ISO'. Every copy attempt has been to the same share. Created 'test share' as instructed and the 40+ GB file copies just fine if I just dump it to the share AS WELL AS copying to D12\test share (tried it both ways). Copy speeds even look good @ 100+ MB/s. I was totally shocked as I fully expected it to fail. Is it possible this has something to do with the name of my share? And, yes, this is extremely frustrating but at the very least we know a work-around.
  5. MemTest ran for 10+ hours and reported 0 errors. Tried to copy a file to D12\Movies - ISO that is 5.78 MB and got the same error as previously with the large file.
  6. Triple checked. It's set to split level 1, High-water, 100GB min free space. I'll run memtest tonight.
  7. 1.49TB Attempt to add an additional file to D12\Movies - ISO that failed previously fails with the same error. Disabled user shares and attempted to add additional file to D12\Movies - ISO. It fails with same error.
  8. This worked with no issues. And then I was able to move it to the share with no issue.
  9. Out of town for a couple of days but I will try and post results as soon as I return. Thanks
  10. Please note that the issue is with D12 [it was with D13 prior to me removing the 'old' D12 and then moving D13 to the D12 slot]. However, both drives exhibited the same behavior. Is the following attachment what you require?
  11. My apologies for my last comment. I was trying to make you aware of what I had done so far. To recap: - Completed a clean install to unRAID 6.0rc3 - Prior to enabling share, attempted to write to D13 (which had 4TB+ of data) and could not - Removed D12 from array (so i can convert it to XFS) - Moved D13 to D12's old slot (so D12 is now the disk in question - note that both 6TB drives exhibit same behavior) All drives in array are currently RFS. All requested info (updated) is below. Thank you syslog.txt
  12. And it gets more interesting... Frustrated, I went ahead and did a clean install to unRAID 6 rc3. Prior to re-creating my shares, I tested trying to write additional data to Disk 13. Same results as before. This leads me to believe it is definitely not a share issue. I have since swapped D12 & D13 locations. The 'new' D13 is currently not part of the array so I can transition it to XFS. The 'new' D12 [currently with 4.46TB of data on it] will not accept any further data writes. So where do I go from here?
  13. That is correct in that it will not allow further writes. I first noticed this on error on Disk 12. Thinking it might be the disk, I migrated everything to 13. That's why 12 is showing empty.
  14. I disagree. I'm writing directly to Disk 13 (Movies-ISO) folder. I am not adding to the share folder.