July 17, 201114 yr Can some one please interpret these results and advise if I should use this drive. WDC WD5000AAKS-65TMA0 WD-WCAPW2103990 Disk /dev/sdd has been successfully precleared ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Current_Pending_Sector = 200 194 0 ok 20 Multi_Zone_Error_Rate = 188 188 51 In_the_past 830 No SMART attributes are FAILING_NOW 492 sectors were pending re-allocation before the start of the preclear. 492 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 20 sectors are pending re-allocation at the end of the preclear, a change of -472 in the number of sectors pending re-allocation. 99 sectors had been re-allocated before the start of the preclear. 99 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. SMART overall-health self-assessment test result: PASSED I would not use it. All of the sectors pending re-allocation were re-allocated were apparently re-written in place when the disk was zeroed, BUT 20 more were identified as un-readable in the post read phase. It is possible it is an issue with the power to the disk, but more likely the disk itself. Joe L.
July 19, 201114 yr Is this ok? = Disk Post-Clear-Read completed DONE Disk Temperature: 36C, Elapsed Time: 18:39:50 ========================================================================1.12 == ST31500341AS 9VS922T1 == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 106 112 6 ok 12389767 Spin_Retry_Count = 100 100 97 near_thresh 20 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 1 1 0 near_thresh 253 Airflow_Temperature_Cel = 64 65 45 near_thresh 36 Temperature_Celsius = 36 35 0 ok 36 Hardware_ECC_Recovered = 58 35 0 ok 12389767 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 34 sectors had been re-allocated before the start of the preclear. 34 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. sorry if I should have attached.
July 19, 201114 yr Is this ok? = Disk Post-Clear-Read completed DONE Disk Temperature: 36C, Elapsed Time: 18:39:50 ========================================================================1.12 == ST31500341AS 9VS922T1 == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 106 112 6 ok 12389767 Spin_Retry_Count = 100 100 97 near_thresh 20 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 1 1 0 near_thresh 253 Airflow_Temperature_Cel = 64 65 45 near_thresh 36 Temperature_Celsius = 36 35 0 ok 36 Hardware_ECC_Recovered = 58 35 0 ok 12389767 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 34 sectors had been re-allocated before the start of the preclear. 34 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. sorry if I should have attached. you are fine. Apparently, 34 sectors were re-allocated before you performed the preclear, and the same 34 existed afterwords. In other words, no additional were detected. I'd go ahead and use the drive, but monitor it over the next months/years. I've got several old drives where an initial number of re-allocated sectors does not change, and they work perfectly fine. If you have time, give it another preclear cycle.
July 19, 201114 yr Is this ok? = Disk Post-Clear-Read completed DONE Disk Temperature: 36C, Elapsed Time: 18:39:50 ========================================================================1.12 == ST31500341AS 9VS922T1 == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 106 112 6 ok 12389767 Spin_Retry_Count = 100 100 97 near_thresh 20 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 1 1 0 near_thresh 253 Airflow_Temperature_Cel = 64 65 45 near_thresh 36 Temperature_Celsius = 36 35 0 ok 36 Hardware_ECC_Recovered = 58 35 0 ok 12389767 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 34 sectors had been re-allocated before the start of the preclear. 34 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. sorry if I should have attached. you are fine. Apparently, 34 sectors were re-allocated before you performed the preclear, and the same 34 existed afterwords. In other words, no additional were detected. I'd go ahead and use the drive, but monitor it over the next months/years. I've got several old drives where an initial number of re-allocated sectors does not change, and they work perfectly fine. If you have time, give it another preclear cycle. I hate to ask this but I searched and could find it but what type of errors am I looking for. I have another 10 drives to do and I don't want to keep bugging you. Is there anything special I should be looking at? Or is ok to just post them for someone to take a look at? Thanks for the quick response. jets
July 19, 201114 yr I'd preclear this guy two more times. It is very unusual for a drive with more than a handrul of reallocated sectors to not continue to have more sectors reallocated with most every preclear or parity check cycle. If you can go three times in a row, I'd be satisfied that the drive is solid.
July 19, 201114 yr Is this ok? = Disk Post-Clear-Read completed DONE Disk Temperature: 36C, Elapsed Time: 18:39:50 ========================================================================1.12 == ST31500341AS 9VS922T1 == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 106 112 6 ok 12389767 Spin_Retry_Count = 100 100 97 near_thresh 20 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 1 1 0 near_thresh 253 Airflow_Temperature_Cel = 64 65 45 near_thresh 36 Temperature_Celsius = 36 35 0 ok 36 Hardware_ECC_Recovered = 58 35 0 ok 12389767 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 34 sectors had been re-allocated before the start of the preclear. 34 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. sorry if I should have attached. you are fine. Apparently, 34 sectors were re-allocated before you performed the preclear, and the same 34 existed afterwords. In other words, no additional were detected. I'd go ahead and use the drive, but monitor it over the next months/years. I've got several old drives where an initial number of re-allocated sectors does not change, and they work perfectly fine. If you have time, give it another preclear cycle. I hate to ask this but I searched and could find it but what type of errors am I looking for. I have another 10 drives to do and I don't want to keep bugging you. Is there anything special I should be looking at? Or is ok to just post them for someone to take a look at? Thanks for the quick response. jets look for no change in the reallocated sector count, and no change in those pending re-alllocation, ((preferably zero for both, but a number that does not change after several cycles is ok as long as it is low) and no attributes marked as FAILING_NOW, and a preclear status that says it was successful.
July 20, 201114 yr I have a 3TB Western Digital Green on the way to replace my 2TB parity drive. I'm kind of skeptical using the 1.12 preclear script... I'm pretty much a noob when it comes to this stuff. I've used the script without issues on WD20EADS and WD20EARS (with and without jumpers). So what should I change? I've downloaded 1.12. Now when I put my drive in, do I just run it normally with "/boot/preclear_disk.sh /dev/XXX" or is there some extra command lines I should do? When it's done how can I make sure it was correctly done? Thanks.
July 20, 201114 yr Do I just run it normally with "/boot/preclear_disk.sh /dev/XXX"That's it. or is there some extra command lines I should do?Nothing else needed. When it's done how can I make sure it was correctly done? It will tell you if it was successful.
July 20, 201114 yr I've downloaded 1.12. Now when I put my drive in, do I just run it normally with "/boot/preclear_disk.sh /dev/XXX" Unless you renamed the preclear_disk1.12beta.sh to preclear_disk.sh, then you would run it as "/boot/preclear_disk1.12beta.sh /dev/XXX", otherwise if you have say 1.11 or lower still next to it, you would not be running 1.12, but an older version.
July 23, 201114 yr Does a cache drive need to be precleared? Thanks, Neil No disk needs to be precleared. Preclear does a pretty decent burn in test of any drive. In the end, assuming the preclear works properly, the drive is left with a preclear signature. The preclear signature is ONLY useful if you are adding the disk as an array disk. Having the preclear signature prevents unRAID itself from clearing the disk (a somewhat painful process becuase your array is offline during the lengthy clearing process). So no, it is not necessary to preclear a cache disk, but you should do it anyway. All of its contents will be lost (if it had any), but you will have confidence that the disk is functioning within normal parameters before you start using it.
July 23, 201114 yr Does a cache drive need to be precleared? Thanks, Neil No, not if you trust it to be 100% perfect and do not care if a file written to it cannot be read back and transferred to the protected array. From people posting here, about 1 in 5 drives has issues, do you feel lucky...? ? ?
July 23, 201114 yr Speaking of... UPS delivered a new 2TB WD Green disk yesterday. I took advantage of the recent promo code on newegg. The shipping box contained styrofoam packing peanuts and the OEM box. The OEM box is the one that contains the little plastic end caps the disk and anti-static bag rests in, "floating". I started a preclear this morning using v1.11, my laptop, and an e-sata dock. The same setup as I've done for the last three new disks. I checked the progress a few minutes ago and it was stalled at ~45% on the second step. I did a hard shutdown of the lappy, rebooted, then started the preclear again. This time, Disk /dev/sdb doesn't contain a valid partition. sdb is currently failing SMART tests. Reallocated_sector_ct now 1265. is displayed. :o I think this is my first bad disk. Your thoughts?
July 24, 201114 yr Speaking of... UPS delivered a new 2TB WD Green disk yesterday. I took advantage of the recent promo code on newegg. The shipping box contained styrofoam packing peanuts and the OEM box. The OEM box is the one that contains the little plastic end caps the disk and anti-static bag rests in, "floating". I started a preclear this morning using v1.11, my laptop, and an e-sata dock. The same setup as I've done for the last three new disks. I checked the progress a few minutes ago and it was stalled at ~45% on the second step. I did a hard shutdown of the lappy, rebooted, then started the preclear again. This time, Disk /dev/sdb doesn't contain a valid partition. sdb is currently failing SMART tests. Reallocated_sector_ct now 1265. is displayed. :o I think this is my first bad disk. Your thoughts? Definitely looks like a bad drive. I suggest attempting preclear 2 or 3 more times. If it still fails every time (especially if those reallocated sector counts keep increasing), then RMA it.
July 24, 201114 yr I tried twice more directly after the original attempt, and it stalled after just a couple minutes. I did not notice the sector count. Thanks for the reply.
July 25, 201114 yr just precleared a drive with these results ========================================================================1.11 == invoked as: ./preclear_disk.sh -A /dev/sdh == WDC WD20EARS-00MVWB0 WD-WCAZA0947856 == Disk /dev/sdh has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:50:05 (81 MB/s) == Last Cycle's Zeroing time : 6:05:45 (91 MB/s) == Last Cycle's Post Read Time : 13:36:53 (40 MB/s) == Last Cycle's Total Time : 26:33:44 == == Total Elapsed Time 26:33:44 == == Disk Start Temperature: 25C == == Current Disk Temperature: 33C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 200 199 51 ok 20 Temperature_Celsius = 117 125 0 ok 33 No SMART attributes are FAILING_NOW 3 sectors were pending re-allocation before the start of the preclear. 3 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, a change of -3 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================
July 25, 201114 yr I would run another cycle on the drive. The 3 pending before start and then 3 pending after completion is a little odd. I would check all power and data cables before starting the next preclear.
July 25, 201114 yr I would run another cycle on the drive. The 3 pending before start and then 3 pending after completion is a little odd. I would check all power and data cables before starting the next preclear. Three after the PRE-READ was expected. Reading would never re-allocate sectors. Zero re-allocations after writing indicates all the un-readable sectors were processed in place. Zero re-allocated after the POST-READ indicates all three sectors were able to be written in their original locations, and did not need to be re-allocated. The drive is working pretty decently. (You can still keep an eye on it, but it was able to handle the 3 sectors initially marked as un-readable.) Joe L.
July 25, 201114 yr I would run another cycle on the drive. The 3 pending before start and then 3 pending after completion is a little odd. I would check all power and data cables before starting the next preclear. Three after the PRE-READ was expected. Reading would never re-allocate sectors. Zero re-allocations after writing indicates all the un-readable sectors were processes. Zero re-allocated after the POST-READ indicates all three sectors were able to be written in their original locations, and did not need to be re-allocated. The drive is working pretty decently. (You can still keep an eye on it, but it was able to handle the 3 sectors initially marked as un-readable.) Joe L. You are correct, that's what I get for skimming over the report. Been looking at so many of those this weekend with nothing reported that I did the same when I looked at the one posted above.
July 25, 201114 yr so is it safe to add to array or should i preclear again? It is safe, though I would probably still run another preclear.
July 25, 201114 yr When did the initial 3 un-readable sectors get detected? Was the disk previously used?
July 25, 201114 yr When did the initial 3 un-readable sectors get detected? Was the disk previously used? about a hour ago when it preclear finished , yes was used before to store movies in windows
July 25, 201114 yr was clearing 3 drives one was pefect 2nd one was the one above the third one just returned this ========================================================================1.11 == invoked as: ./preclear_disk.sh -A /dev/sda == WDC WD20EARS-00S8B1 WD-WCAVY4344551 == Disk /dev/sda has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:24:13 (75 MB/s) == Last Cycle's Zeroing time : 7:00:03 (79 MB/s) == Last Cycle's Post Read Time : 14:12:42 (39 MB/s) == Last Cycle's Total Time : 28:37:58 == == Total Elapsed Time 28:37:58 == == Disk Start Temperature: 27C == == Current Disk Temperature: 36C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 100 200 0 ok 0 Temperature_Celsius = 116 125 0 ok 36 No SMART attributes are FAILING_NOW 19 sectors were pending re-allocation before the start of the preclear. 19 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, a change of -19 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.