June 13, 20179 yr Hi All that read this. A few weeks ago I started replacing my drives to larger ones WD Red 4TB on 2 separate arrays (ur-01 and ur-02) both have the same amount of drives (2 Parity, 6 Data) I ran preclear on every new disk I purchased on another machine which i use as a tester !!! (I'll call this ur-03) everything showed up ok! Process running in parallel :- 1. Run preclear on ur-03 2. Wait 24+ hours complete. 3. After completion remove, then add next drive to be precleared 4. Shutdown ur-01 remove first Parity Disk replace with new precleared disk 5. Start the array, Parity check starts. (8-10Hrs) to finish. 6. When next precleared drive finishes repeat step (3) 7. Shutdown ur-02 remove first Parity Disk replace with new precleared disk 8. See step (5) 9. Did this sequence until the Parity disks had been replaced (4) 10. Replaced smaller disks in the array with the larger ones (4TB) 11. Giving me replacements of 2 Parity and 2 data Drives on each machine. When I replaced the Parity 02 disk on on machine ur-02, started the machine as usual Parity check started. When finished Parity01 showed errors. Checked Diagnostics file which showed UDMA_CRC_error(s) of 134 Rang the company where I bought the drives for a replacement Last Friday (9th June 2017), now awaiting for pickup tomorrow (14th June 2017), at the same time I bought another 4TB drive so that I could have a replace the one being sent back for checking or replacement (whatever the outcome I could add the drive to replace a smaller disk in either machine) The New disk arrived Saturday, did the same procedure with a new disk as normal. Late Sunday evening parity check started. This Morning 13th June 2017 checked the array, now Parity-02 is showing errors, in fact looking at the system log I've never seen so many errors Red Cross X Device is disabled, contents emulated. The said file(s) have been attached .... Hope someone can help thanks Sorry it's been a long winded post and thanks for sticking with it till the end .... respect --- numpkin unraid_tower-02-diagnostics-20170613-0952.zip unraid_tower-02-syslog-20170613-0955.zip Edited June 13, 20179 yr by numpkin missed info
June 13, 20179 yr Many ATA errors for this disk: Jun 12 11:58:04 Unraid_Tower-02 kernel: ata2.00: ATA-10: WDC WD40EFRX-68N32N0, WD-WCC7K7ASK0XC, 82.00A82, max UDMA/133 Including CRC errors: Jun 12 12:24:40 Unraid_Tower-02 kernel: ata2: SError: { UnrecovData 10B8B BadCRC } So probably a bad SATA cable.
June 13, 20179 yr Author Hi johnnie.black, tks for quick reply, when I replace the cable do I have to "parity check" or will it be automatic.. respect --- numpkin
June 13, 20179 yr Didn't see any sync errors, but a non-correct parity is a good idea to see if the problem is solved. Sorry, read the post to fast, parity2 is disabled, so you need do unassign the disk, start the array, stop the array, re-assign the disk, start the array, parity sync will begin. Edited June 13, 20179 yr by johnnie.black
June 13, 20179 yr Author Hi johnnie.black Thanks Started the array unchecked the box "write corrections to parity" check has started ... updated system & diagnostic attached ... After the check do I have to recheck the box again ?? to allow parity to be written to as normal? respect --- numpkin updated_unraid_tower-02-diagnostics-20170613-1321.zip updated_unraid_tower-02-syslog-20170613-1322.zip
June 13, 20179 yr Author Thanks just saw your update .... Do I still have to uncheck the "Start will start Parity-Sync and/or Data-Rebuild" or put back the check?? respect --- numpkin
June 13, 20179 yr 1 minute ago, numpkin said: Do I still have to uncheck the "Start will start Parity-Sync and/or Data-Rebuild" or put back the check?? You have to check it to be able to start the array.
June 13, 20179 yr Author Thank again ..... Now you know why I use the username "numpkin" Keep you informed ... Respect --- numpkin .....
June 14, 20179 yr Author Hi Johnnie.black, Checked this morning, pleased to say everything seems back to normal ......... Many thanks again for your valued help Latest "Diagnostic / System logs attached respect --- numpkin latest_unraid_tower-02-diagnostics-20170614-0831.zip latest_unraid_tower-02-syslog-20170614-0833.zip
Archived
This topic is now archived and is closed to further replies.