November 21, 20205 yr I am running preclear (gfjardim's plugin) to test two new drives for use as parity drives. One of the drives has just produced this: ############################################################################################################################ # # # unRAID Server Preclear of disk V9GXAXWL # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [8:28:17 @ 196 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [8:11:26 @ 203 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: FAIL # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 19:58:40 | Total elapsed time: 19:58:40 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status (device type: default) # # # # # # ATTRIBUTE INITIAL STATUS # # 5-Reallocated_Sector_Ct 0 - # # 9-Power_On_Hours 0 - # # 194-Temperature_Celsius 39 - # # 196-Reallocated_Event_Count 0 - # # 197-Current_Pending_Sector 0 - # # 198-Offline_Uncorrectable 0 - # # 199-UDMA_CRC_Error_Count 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> FAIL: Post-Read verification failed. Your drive is not zeroed. Is the system log the only way to get any more information about the failure? I attach extracts from the system log file for all the relevant entries I can find. PreclearLogEntries
November 21, 20205 yr Community Expert Post-read verification failed can be caused by bad RAM. Happened to me.
November 21, 20205 yr Author 8 minutes ago, trurl said: Post-read verification failed can be caused by bad RAM. Happened to me. So, is there any way I can determine what caused the failure? Do I just re-run the Preclear? The other drive is still running the Post-Read, at 58%.
November 21, 20205 yr Author Here's an interesting thought .... Part of the reason for urgent replacement of parity drives is that my Parity2 drive appears to have failed. The parity drive which has failed (a relatively new drive), and this new drive which has failed Preclear are both on the same SATA disk interface card - a two port generic Asmedia device, purchased from China. Perhaps the issue is with the SATA interface? I think I should try moving both of these drives to other SATA ports.
Archived
This topic is now archived and is closed to further replies.