Hi all,

 

I am fairly new to Unraid (3 days remaining on my trial installation so still learning my way around). I have set up what I think is a pretty decent server with good hardware and storage (i5 9600k, 32GB RAM, 40TB storage so far). During the past couple of weeks I have been moving files and drives over from my old NAS and have managed to copy about 10TB over the network without any problems. However, suddenly I have started experiencing some odd problems where a file copy from a Windows 2012R2 will suddenly stop and complain that the file being transferred is locked. This can happen after transferring 300GB without issue (most recent example). Looking at the directory through the webUI I can see that the file has been created but I can't tell if the data was actually transferred or not. However, trying to access the folder using Explorer will fail and time out, probably due to a lock of some kind. Further attempts seem to mess up Explorer quite badly. Also, the file systems on the Unraid server seem to get messed up and the 1st time it happened I was forced to do an unclean shutdown because the array got stuck in "Sync file systems" while stopping.

 

I am really puzzled as to why this has started happening. It began after adding the 2 latest drives (am now up to 4 drives + 1 parity) where one of them is reporting 17 "UDMA CRC errors". Those errors should be harmless from what I can gather, and besides I am writing to the other drive so in any case this should have no effect.

 

I have added a diagnostics file, hoping that this will show something useful to someone who actually knows what to look for.

 

Any help on this issue would be greatly appreciated.

 

Best regards,

Symple

thevault-diagnostics-20190605-2205.zip

Have you run a memtest yet?  Also update the BIOS.  Your BIOS version is from before the Initial Release of the mobo

I have to admit that in 20+ years of working with computers I have never identified a bad RAM stick by using MemTest. However, taking your advice I ran it and lo and behold, there were consistent errors in the same test on every pass. So I removed one stick, re-tested, and the error was gone. Put it back in as 2*single channel - no errors. Put it back in its original location as dual channel - still no errors. Apparently, a re-seating of that particular stick was all it took.

 

Have since copied ~4TB in a single session to the drive that was causing trouble without any problems what so ever, so at least for now I believe the error to be fixed. Oh, and also updated the BIOS while I was at it. This was prior to running MemTest though.

 

Thanks a lot for your assistance, @Squid - much appreciated 🙂

 

Best regards