November 20, 200916 yr Got a new WD 1 TB green HD, ran preclear_disk.sh on it, and for first time, saw preclear kick out an error when completed: < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 58c58 < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 12 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 15 67c67 < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 --- > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 ============================================================================ any help from those more knowledgable than I? Thanks c+h
November 20, 200916 yr Got a new WD 1 TB green HD, ran preclear_disk.sh on it, and for first time, saw preclear kick out an error when completed: < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 58c58 < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 12 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 15 67c67 < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 --- > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 ============================================================================ any help from those more knowledgable than I? Thanks c+h None of those are errors and it is not a SMART error report. What you posted is just the differences from the pre-process SMART report produced by the smartctl program and the post-process SMART report produced by the smartctl program. The differences between the two are output by the preclear_disk.sh process. It is an aid to allow you to spot anything that have changed. Many times there will be some changes, especially the very first time a drive is written to when fresh from the factory. At that point the values change from the factory initialized values. (most time they pre-initialize them to 253) For example, it shows the disk heads had previously been loaded 12 times before the process had started and the count was 15 at the end. If the disk heads had not loaded during the pre-clear I doubt anything could have been read or written. So, all you are seeing are the differences... In fact, the drive could have been failing before, and identically failing after, and no line would print since it did not change. As I said, it is just the differences, not an absolute status. The lines in the SMART report that indicate errors you are most interested in are for "reloacated sectors", and "sectors pending relocation." Take a look at the full reports in your syslog and look for re-allocated sector counts increasing between the pre and post report. Even then, most disks these days have thousands of spare sectors to use in re-allocation. To see a small number in the pre report and the exact same number in the post process would indicate the problem sectors were already identified and re-allocated. I've got one drive with 100 relocated sectors... That value has not changed over time since I've been tracking it over the past few years. The drive will probably last for many many years. If the re-allocated sector count value continued to increase each time you pre-cleared it, it would be a reason for concern. Enjoy your new disk. It appears to have been cleared successfully. Joe L.
November 20, 200916 yr Author thanks for the help, joe, as I'm sure you have heard many times by now. I was confused because I never saw anything after running preclear on my previous 3 disks, including another one of the exact same make and model. I went ahead and switched the cable out last night and started preclear again. Guess I didn't need to. Silly me. Will happily add it to the array when it's done. Thanks again, c+h
Archived
This topic is now archived and is closed to further replies.