luxjack

I have since (following suggestions here - tks johnnie & snicky) copied files to different disks, using different controllers, and all copies were corrupt. I then hooked up another unraid box and found that it too had the same issues. Moving the system from my basement to the study (still connecting to same LAN) cured the issue: so now I must assume that the problem is in a segment of my LAN .. . . :-(

Thank you itimpi. Following your suggestion I ran memtest for 22 hours and 22 passes but no errors found.

Hello to all. I am a long-time user of unraid in a very simple config (just using it as a file server, no dockers, vms etc which are too technical for me). Before transferring files (which I do in a non-automated way using either Teracopy or Windows explorer) from my Windows PC to Unraid I create checksums for each file and occasionally check these on the unraid shares. I recently noticed that checksum verification shows errors on all files I have transferred recently. Files I transferred on 16/06 are god but files transferred on 30/09 and since are corrupted it seems. I am running v6.7.2 but I cannot say if the problem is related to the version as I do not know when I updated. I have tried using Teracopy to do the transfers, with the verify setting ticked, and it also fails the verification test. Would be very grateful for any possible assistance. unraid-schr-diagnostics-20191110-1947.zip

Thanks. I see we have the same zeroing speed, but the difference arises on the read phases - yours are much faster indeed. What I am surprised at is to see you got almost the same post-read speed as pre-read speed. In my experience, post-read is usually about half pre-read speed. But perhaps thats the different script - I use the standard version.

Hi, I regularly preclear 4TB drives - WD Reds/Greens - and this is my first HGST 4 TB 7200 RPM Deskstar. (Heretic posted a similar issue using the NAS version of this drive - sorry I cannot see how to quote it here). I too have had unusually slow pre-read times - essentially a 1-cycle preclear for this HGST drive takes as long as a WD 4TB 2-cycle preclear. I tried it on two different configs but similar results each time. I have no real worry about the drive - the post preclear smart looks fine but I add this here in case somebody is curious or interested to see why so slow. (Not a regular poster so apologies if I make errors - not sure how to reply and quote). invoked as: ./preclear_disk.sh -A /dev/sdb == HGSTHDS724040ALE640 PK2301PCHME5PB == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 21:31:26 (51 MB/s) == Last Cycle's Zeroing time : 8:36:10 (129 MB/s) == Last Cycle's Post Read Time : 42:20:43 (26 MB/s) == Last Cycle's Total Time : 72:29:26 == == Total Elapsed Time 72:29:26 == == Disk Start Temperature: 34C == == Current Disk Temperature: -->43<--C, Preclear_Reports_HGST_4TB.txt

Hi folks, I also ran into this same issue recently and was happy to find the explanation here (thanks to all you knowledgeable people who share your experiences and provide so much help to the rest of us). Just in case this may help other technically-challenged users like myself, the problem was I had a "&" character in the share name. Editing (via unraid web) the name and removing the offending character solved the problem. Acceptable characters as declared in the wiki are "a-z, A-Z, 0-9, - (dash), and . (dot)". So as it stands the system allows one to create a share name with non-allowed characters - and it works fines seemingly except for the Compute. Also noticed when editing share name to correct the problem, that when the change was applied I got the message saying the old share name was "deleted" - it would be less alarming if it says "renamed" :-) (I am not an experienced poster or forum user so apologies in advance if I have inadvertently breeched forum etiquette in replying to this old message).

Upgraded to rc12a and now all is working again - thank you

rc11 working fine, but with rc12 cannot access server - presumably also due to my NIC Realtek 8111E