July 6, 201115 yr Just precleaered 2 green western digital 2tb one has 10 sectors are pending re-allocation the other one has one has 124 sectors are pending re-allocation What does this mean can i fix ??
July 6, 201115 yr Just precleaered 2 green western digital 2tb one has 10 sectors are pending pre allocation the other one has one has 124 sectors are pending re-allocation What does this mean can i fix ?? It indicates you need to perform a subsequent preclear_disk.sh on each of those disks. Pending re-allocation is worse than already re-allocated since it infers they were detected in the post-read. If you are not sure, post the actual preclear results. Joe L.
July 6, 201115 yr Author ========================================================================1.11 == invoked as: ./preclear_disk.sh /dev/sda == == Disk /dev/sda has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:44:29 (82 MB/s) == Last Cycle's Zeroing time : 6:50:52 (81 MB/s) == Last Cycle's Post Read Time : 14:42:41 (37 MB/s) == Last Cycle's Total Time : 28:19:09 == == Total Elapsed Time 28:19:09 == == Disk Start Temperature: 34C == == Current Disk Temperature: 34C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 199 200 51 ok 108 Spin_Up_Time = 253 185 21 ok 1241 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. 10 sectors are pending re-allocation at the end of the preclear, a change of 10 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. ============================================================================ and ========================================================================1.11 == invoked as: ./preclear_disk.sh /dev/sdb == WDC WD20EARS-00MVWB0 WD-WCAZA7708298 == Disk /dev/sdb has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:00:34 (79 MB/s) == Last Cycle's Zeroing time : 8:22:11 (66 MB/s) == Last Cycle's Post Read Time : 19:07:24 (29 MB/s) == Last Cycle's Total Time : 34:31:15 == == Total Elapsed Time 34:31:15 == == Disk Start Temperature: 33C == == Current Disk Temperature: 33C, == ============================================================================ ** 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 = 191 200 51 ok 972 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. 124 sectors are pending re-allocation at the end of the preclear, a change of 124 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 6, 201115 yr Author Just precleaered 2 green western digital 2tb one has 10 sectors are pending pre allocation the other one has one has 124 sectors are pending re-allocation What does this mean can i fix ?? It indicates you need to perform a subsequent preclear_disk.sh on each of those disks. Pending re-allocation is worse than already re-allocated since it infers they were detected in the post-read. If you are not sure, post the actual preclear results. Joe L. they are both pending re-allocation my mistake
July 6, 201115 yr Preclear them again. You could try different ports/cables/power supply connectors if possible. A few people have reported pending sectors going away without be reallocated, and there is no real explanation but the suspect cause is something to do with the connection or poor power. RMA the drives if the pending sectors do not return and stay at zero and the reallocated sectors do not stabilize. The preferred is to have both at 0 but a disk with some reallocated sectors that never increases can still perform fine. If the numbers change every preclear then keep it going until they die which will make it easier to return them. They will accept the drives no questions asked if they show the drive has failed in the SMART report. Peter
July 7, 201115 yr I wouldn't trust either drive with data unless they can pass preclear with no errors or pending reallocations. I don't see a model number for the first drive, but the second is a WDEARS that you precleared at sector 63. If you have a jumper installed already, then this is the proper thing to do. If not, then the drive should be precleared starting at sector 64 (using the -A flag in preclear).
July 7, 201114 yr I wouldn't trust either drive with data unless they can pass preclear with no errors or pending reallocations. I didn't post this before but if I saw those errors I'd expect the drive to pass 2 or 3 consecutive preclears without issue before trusting it again. Peter
July 10, 201114 yr Author I wouldn't trust either drive with data unless they can pass preclear with no errors or pending reallocations. I don't see a model number for the first drive, but the second is a WDEARS that you precleared at sector 63. If you have a jumper installed already, then this is the proper thing to do. If not, then the drive should be precleared starting at sector 64 (using the -A flag in preclear). ive tried preclearing on sector 64 with -A flag now it gets past stage 1 and it stops and says segmentation fault
Archived
This topic is now archived and is closed to further replies.