ehrw Posted January 24, 2021 Share Posted January 24, 2021 I have a 6tb WD red drive (WD60EFRX) that's acting up. I've just replaced it as a parity drive and it has from time to time given errors during parity check. After googling the errors some have suggested it could be a bad cable. I've switched cable twitch and also used another sata port on the motherboard. Seemed like the read errors got lower after that but it still occur. I'm now running a preclear on it and it is on the last stage, the Post-Read stage. I'll update this thread when it's finished but I suspect it won't give any errors. First, let's have a look at the disk log. Starting with me removing the old xfs partition Jan 23 01:36:35 Server unassigned.devices: Adding disk '/dev/sdg1'... Jan 23 01:36:35 Server unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdg1' '/mnt/disks/WDC_WD60EFRX-68L0BN1_WD-WX11D86J1UNN' Jan 23 01:36:35 Server kernel: XFS (sdg1): Mounting V5 Filesystem Jan 23 01:36:35 Server kernel: XFS (sdg1): Log inconsistent (didn't find previous header) Jan 23 01:36:35 Server kernel: XFS (sdg1): failed to find log head Jan 23 01:36:35 Server kernel: XFS (sdg1): log mount/recovery failed: error -117 Jan 23 01:36:35 Server kernel: XFS (sdg1): log mount failed Jan 23 01:36:36 Server unassigned.devices: Mount of '/dev/sdg1' failed. Error message: mount: /mnt/disks/WDC_WD60EFRX-XXXXXXX_WD-XXXXXXXXXXXXX: mount(2) system call failed: Structure needs cleaning. Jan 23 11:35:57 Server unassigned.devices: Removing partition '1' from disk '/dev/sdg'. Jan 23 11:36:03 Server kernel: sdg: Jan 23 11:36:26 Server preclear_disk_WD-XX[16328]: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 5 --frequency 1 --cycles 1 --no-prompt /dev/sdg Jan 23 11:36:28 Server preclear_disk_WD-XX[16328]: Pre-Read: dd if=/dev/sdg of=/dev/null bs=2097152 skip=0 count=6001175126016 conv=noerror iflag=nocache,count_bytes,skip_bytes Jan 23 16:36:33 Server kernel: ata6.00: exception Emask 0x0 SAct 0x1e00004a SErr 0x0 action 0x0 Jan 23 16:36:33 Server kernel: ata6.00: irq_stat 0x40000008 Jan 23 16:36:33 Server kernel: ata6.00: failed command: READ FPDMA QUEUED Jan 23 16:36:33 Server kernel: ata6.00: cmd 60/40:c8:00:64:cc/05:00:4f:01:00/40 tag 25 ncq dma 688128 in Jan 23 16:36:33 Server kernel: ata6.00: status: { DRDY ERR } Jan 23 16:36:33 Server kernel: ata6.00: error: { UNC } Jan 23 16:36:33 Server kernel: ata6.00: configured for UDMA/133 Jan 23 16:36:33 Server kernel: sd 6:0:0:0: [sdg] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=7s Jan 23 16:36:33 Server kernel: sd 6:0:0:0: [sdg] tag#25 Sense Key : 0x3 [current] Jan 23 16:36:33 Server kernel: sd 6:0:0:0: [sdg] tag#25 ASC=0x11 ASCQ=0x4 Jan 23 16:36:33 Server kernel: sd 6:0:0:0: [sdg] tag#25 CDB: opcode=0x88 88 00 00 00 00 01 4f cc 64 00 00 00 05 40 00 00 Jan 23 16:36:33 Server kernel: blk_update_request: I/O error, dev sdg, sector 5633762304 op 0x0:(READ) flags 0x84700 phys_seg 168 prio class 0 Jan 23 16:36:33 Server kernel: ata6: EH complete Jan 23 21:46:21 Server kernel: ata6.00: exception Emask 0x0 SAct 0x207f080 SErr 0x0 action 0x0 Jan 23 21:46:21 Server kernel: ata6.00: irq_stat 0x40000008 Jan 23 21:46:21 Server kernel: ata6.00: failed command: READ FPDMA QUEUED Jan 23 21:46:21 Server kernel: ata6.00: cmd 60/40:70:00:aa:53/05:00:54:02:00/40 tag 14 ncq dma 688128 in Jan 23 21:46:21 Server kernel: ata6.00: status: { DRDY ERR } Jan 23 21:46:21 Server kernel: ata6.00: error: { UNC } Jan 23 21:46:21 Server kernel: ata6.00: configured for UDMA/133 Jan 23 21:46:21 Server kernel: sd 6:0:0:0: [sdg] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=7s Jan 23 21:46:21 Server kernel: sd 6:0:0:0: [sdg] tag#14 Sense Key : 0x3 [current] Jan 23 21:46:21 Server kernel: sd 6:0:0:0: [sdg] tag#14 ASC=0x11 ASCQ=0x4 Jan 23 21:46:21 Server kernel: sd 6:0:0:0: [sdg] tag#14 CDB: opcode=0x88 88 00 00 00 00 02 54 53 aa 00 00 00 05 40 00 00 Jan 23 21:46:21 Server kernel: blk_update_request: I/O error, dev sdg, sector 10004703744 op 0x0:(READ) flags 0x84700 phys_seg 168 prio class 0 Jan 23 21:46:21 Server kernel: ata6: EH complete Jan 23 21:47:19 Server kernel: ata6.00: exception Emask 0x0 SAct 0x7c1010c0 SErr 0x0 action 0x0 Jan 23 21:47:19 Server kernel: ata6.00: irq_stat 0x40000008 Jan 23 21:47:19 Server kernel: ata6.00: failed command: READ FPDMA QUEUED Jan 23 21:47:19 Server kernel: ata6.00: cmd 60/40:d0:00:04:7b/05:00:54:02:00/40 tag 26 ncq dma 688128 in Jan 23 21:47:19 Server kernel: ata6.00: status: { DRDY ERR } Jan 23 21:47:19 Server kernel: ata6.00: error: { UNC } Jan 23 21:47:19 Server kernel: ata6.00: configured for UDMA/133 Jan 23 21:47:19 Server kernel: sd 6:0:0:0: [sdg] tag#26 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=8s Jan 23 21:47:19 Server kernel: sd 6:0:0:0: [sdg] tag#26 Sense Key : 0x3 [current] Jan 23 21:47:19 Server kernel: sd 6:0:0:0: [sdg] tag#26 ASC=0x11 ASCQ=0x4 Jan 23 21:47:19 Server kernel: sd 6:0:0:0: [sdg] tag#26 CDB: opcode=0x88 88 00 00 00 00 02 54 7b 04 00 00 00 05 40 00 00 Jan 23 21:47:19 Server kernel: blk_update_request: I/O error, dev sdg, sector 10007282688 op 0x0:(READ) flags 0x84700 phys_seg 168 prio class 0 Jan 23 21:47:19 Server kernel: ata6: EH complete Jan 23 23:52:02 Server kernel: ata6.00: exception Emask 0x0 SAct 0xde10 SErr 0x0 action 0x0 Jan 23 23:52:02 Server kernel: ata6.00: irq_stat 0x40000008 Jan 23 23:52:02 Server kernel: ata6.00: failed command: READ FPDMA QUEUED Jan 23 23:52:02 Server kernel: ata6.00: cmd 60/40:48:00:14:8b/05:00:a2:02:00/40 tag 9 ncq dma 688128 in Jan 23 23:52:02 Server kernel: ata6.00: status: { DRDY ERR } Jan 23 23:52:02 Server kernel: ata6.00: error: { UNC } Jan 23 23:52:02 Server kernel: ata6.00: configured for UDMA/133 Jan 23 23:52:02 Server kernel: sd 6:0:0:0: [sdg] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=9s Jan 23 23:52:02 Server kernel: sd 6:0:0:0: [sdg] tag#9 Sense Key : 0x3 [current] Jan 23 23:52:02 Server kernel: sd 6:0:0:0: [sdg] tag#9 ASC=0x11 ASCQ=0x4 Jan 23 23:52:02 Server kernel: sd 6:0:0:0: [sdg] tag#9 CDB: opcode=0x88 88 00 00 00 00 02 a2 8b 14 00 00 00 05 40 00 00 Jan 23 23:52:02 Server kernel: blk_update_request: I/O error, dev sdg, sector 11316958208 op 0x0:(READ) flags 0x84700 phys_seg 168 prio class 0 Jan 23 23:52:02 Server kernel: ata6: EH complete Jan 24 00:32:40 Server preclear_disk_WD-WX11D86J1UNN[16328]: Zeroing: dd if=/dev/zero of=/dev/sdg bs=2097152 seek=2097152 count=6001173028864 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes Jan 24 13:15:21 Server preclear_disk_WD-WX11D86J1UNN[16328]: Post-Read: cmp /tmp/.preclear/sdg/fifo /dev/zero Jan 24 13:15:21 Server preclear_disk_WD-WX11D86J1UNN[16328]: Post-Read: dd if=/dev/sdg of=/tmp/.preclear/sdg/fifo count=2096640 skip=512 iflag=nocache,count_bytes,skip_bytes Jan 24 13:15:22 Server preclear_disk_WD-WX11D86J1UNN[16328]: Post-Read: cmp /tmp/.preclear/sdg/fifo /dev/zero Jan 24 13:15:22 Server preclear_disk_WD-WX11D86J1UNN[16328]: Post-Read: dd if=/dev/sdg of=/tmp/.preclear/sdg/fifo bs=2097152 skip=2097152 count=6001173028864 iflag=nocache,count_bytes,skip_bytes Second, here's the Preclear current progress on Step 5. So far the first two steps seems to be okay even though these errors have occurred. ############################################################################################################################ # # # unRAID Server Preclear of disk WD-XX # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [12:56:11 @ 128 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [12:42:40 @ 131 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 in progress: (25% Done) # # # # # # # # # # # # ** Time elapsed: 2:29:17 | Current speed: 164 MB/s | Average speed: 170 MB/s # # # ############################################################################################################################ # Cycle elapsed time: 28:08:11 | Total elapsed time: 28:08:12 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status (device type: default) # # # # # # ATTRIBUTE INITIAL STATUS # # Reallocated_Sector_Ct 0 - # # Power_On_Hours 34630 - # # Temperature_Celsius 31 - # # Reallocated_Event_Count 0 - # # Current_Pending_Sector 0 - # # Offline_Uncorrectable 0 - # # UDMA_CRC_Error_Count 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ Anyone else with similar experiences and how likely would this drive be to start breaking soon? Quote Link to comment
ehrw Posted January 25, 2021 Author Share Posted January 25, 2021 (edited) Update from the preclear finishing ############################################################################################################################ # # # unRAID Server Preclear of disk WD-XX # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [12:56:11 @ 128 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [12:42:40 @ 131 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: [12:21:40 @ 134 MB/s] SUCCESS # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 38:00:34 | Total elapsed time: 38:00:35 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status (device type: default) # # # # # # ATTRIBUTE INITIAL CYCLE 1 STATUS # # Reallocated_Sector_Ct 0 0 - # # Power_On_Hours 34630 34668 Up 38 # # Temperature_Celsius 31 33 Up 2 # # Reallocated_Event_Count 0 0 - # # Current_Pending_Sector 0 0 - # # Offline_Uncorrectable 0 0 - # # UDMA_CRC_Error_Count 0 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear Finished Successfully!. Says it's fine and also check the smart report above. Which doesn't contain any errors? Full Smart Results shows a few errors though Edited January 25, 2021 by ehrw Adding full smart info Quote Link to comment
JorgeB Posted January 25, 2021 Share Posted January 25, 2021 SMART is showing some issues, it will likely fail again in future, but difficult to guess if it will be tomorrow or a year from now. Quote Link to comment
Recommended Posts
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.