actionfreak

If I have an WD EARS drive with the jumper on the back and Unraid 4.7... should i use the -A option?

Also, when I start the preclear, I see this log. Nov 30 07:48:56 Tower preclear_disk-start[4093]: A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

Maybe this should go in the support forum but I figured I would post it here first. I have been seeing a lot of drive errors in my Norco 4220 lately. Two of my recent drives start showing errors as soon as I put them in multiple slots. This last drive has failed at exactly 99% of the preclear disk pre-read. The first time my server froze up and was unresponsive and I had to restart it. It is currently in slot 9 if you count from left to right from top to bottom. I also put it in slot 17 with the same result. I tried to preclear it last night and didn't notice anything wrong but woke up this morning to see this in the syslog followed by 2 gigs of drive error logs. Nov 30 05:30:33 Tower kernel: sas: command 0xecd99540, task 0xceea1540, timed out: BLK_EH_NOT_HANDLED Nov 30 05:30:33 Tower kernel: sas: Enter sas_scsi_recover_host Nov 30 05:30:33 Tower kernel: sas: trying to find task 0xceea1540 Nov 30 05:30:33 Tower kernel: sas: sas_scsi_find_task: aborting task 0xceea1540 Nov 30 05:30:33 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1701:mvs_abort_task:rc= 5 Nov 30 05:30:33 Tower kernel: sas: sas_scsi_find_task: querying task 0xceea1540 Nov 30 05:30:33 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1645:mvs_query_task:rc= 5 Nov 30 05:30:33 Tower kernel: sas: sas_scsi_find_task: task 0xceea1540 failed to abort Nov 30 05:30:33 Tower kernel: sas: task 0xceea1540 is not at LU: I_T recover Nov 30 05:30:33 Tower kernel: sas: I_T nexus reset for dev 0700000000000000 Nov 30 05:30:33 Tower kernel: sas: I_T 0700000000000000 recovered Nov 30 05:30:33 Tower kernel: sas: --- Exit sas_scsi_recover_host Nov 30 05:31:04 Tower kernel: sas: command 0xecd99540, task 0xd0c6d900, timed out: BLK_EH_NOT_HANDLED Nov 30 05:31:04 Tower kernel: sas: Enter sas_scsi_recover_host Nov 30 05:31:04 Tower kernel: sas: trying to find task 0xd0c6d900 Nov 30 05:31:04 Tower kernel: sas: sas_scsi_find_task: aborting task 0xd0c6d900 Nov 30 05:31:04 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1701:mvs_abort_task:rc= 5 Nov 30 05:31:04 Tower kernel: sas: sas_scsi_find_task: querying task 0xd0c6d900 Nov 30 05:31:04 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1645:mvs_query_task:rc= 5 Nov 30 05:31:04 Tower kernel: sas: sas_scsi_find_task: task 0xd0c6d900 failed to abort Nov 30 05:31:04 Tower kernel: sas: task 0xd0c6d900 is not at LU: I_T recover Nov 30 05:31:04 Tower kernel: sas: I_T nexus reset for dev 0700000000000000 Nov 30 05:31:04 Tower kernel: sas: I_T 0700000000000000 recovered Nov 30 05:31:04 Tower kernel: sas: --- Exit sas_scsi_recover_host Nov 30 05:31:35 Tower kernel: sas: command 0xecd99540, task 0xd0c6d900, timed out: BLK_EH_NOT_HANDLED Nov 30 05:31:35 Tower kernel: sas: Enter sas_scsi_recover_host Nov 30 05:31:35 Tower kernel: sas: trying to find task 0xd0c6d900 Nov 30 05:31:35 Tower kernel: sas: sas_scsi_find_task: aborting task 0xd0c6d900 Nov 30 05:31:35 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1701:mvs_abort_task:rc= 5 Nov 30 05:31:35 Tower kernel: sas: sas_scsi_find_task: querying task 0xd0c6d900 Nov 30 05:31:35 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1645:mvs_query_task:rc= 5 Nov 30 05:31:35 Tower kernel: sas: sas_scsi_find_task: task 0xd0c6d900 failed to abort Nov 30 05:31:35 Tower kernel: sas: task 0xd0c6d900 is not at LU: I_T recover Nov 30 05:31:35 Tower kernel: sas: I_T nexus reset for dev 0700000000000000 Nov 30 05:31:35 Tower kernel: sas: I_T 0700000000000000 recovered Nov 30 05:31:35 Tower kernel: sas: --- Exit sas_scsi_recover_host Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5.00: device reported invalid CHS sector 0 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError } Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError } Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError } Nov 30 05:31:58 Tower kernel: sd 2:0:4:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08 Nov 30 05:31:58 Tower kernel: sd 2:0:4:0: [sdf] Sense Key : 0xb [current] [descriptor] Nov 30 05:31:58 Tower kernel: Descriptor sense data with sense descriptors (in hex): Nov 30 05:31:58 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Nov 30 05:31:58 Tower kernel: 00 00 00 f6 Nov 30 05:31:58 Tower kernel: sd 2:0:4:0: [sdf] ASC=0x0 ASCQ=0x0 Nov 30 05:31:58 Tower kernel: sd 2:0:4:0: [sdf] CDB: cdb[0]=0x28: 28 00 e7 30 fe f8 00 02 00 00 Nov 30 05:31:58 Tower kernel: end_request: I/O error, dev sdf, sector 3878747896 Nov 30 05:31:58 Tower kernel: Buffer I/O error on device sdf, logical block 484843487 Nov 30 05:31:58 Tower kernel: Buffer I/O error on device sdf, logical block 484843488 Nov 30 05:31:58 Tower kernel: Buffer I/O error on device sdf, logical block 484843489 Nov 30 05:31:58 Tower kernel: Buffer I/O error on device sdf, logical block 484843490 Nov 30 05:31:58 Tower kernel: Buffer I/O error on device sdf, logical block 484843491 Nov 30 05:31:58 Tower kernel: Buffer I/O error on device sdf, logical block 484843492 Nov 30 05:31:58 Tower kernel: Buffer I/O error on device sdf, logical block 484843493 Nov 30 05:31:58 Tower kernel: Buffer I/O error on device sdf, logical block 484843494 Nov 30 05:31:58 Tower kernel: Buffer I/O error on device sdf, logical block 484843495 Nov 30 05:31:58 Tower kernel: Buffer I/O error on device sdf, logical block 484843496 Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError } Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError } Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError } Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError } Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError } Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError } Nov 30 05:31:58 Tower kernel: sd 2:0:4:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08 Nov 30 05:31:58 Tower kernel: sd 2:0:4:0: [sdf] Sense Key : 0xb [current] [descriptor] Nov 30 05:31:58 Tower kernel: Descriptor sense data with sense descriptors (in hex): Nov 30 05:31:58 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Nov 30 05:31:58 Tower kernel: 00 00 00 f6 Nov 30 05:31:58 Tower kernel: sd 2:0:4:0: [sdf] ASC=0x0 ASCQ=0x0 Nov 30 05:31:58 Tower kernel: sd 2:0:4:0: [sdf] CDB: cdb[0]=0x28: 28 00 e7 30 fe f8 00 00 08 00 Nov 30 05:31:58 Tower kernel: end_request: I/O error, dev sdf, sector 3878747896 Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError } Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError } Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError } Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError } Nov 30 05:31:58 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 30 05:31:58 Tower kernel: ata5: status=0x41 { DriveReady Error } Nov 30 05:31:58 Tower kernel: ata5: error=0x04 { DriveStatusError }

Regarding my above post. I read the thread again and it looks like that is normal.

I just pre-cleared three WD20EARS drives and as far as I can tell everything looks OK except the increment in Load_Cycle_Count. From a previous post, this may be a hardware problem? All three of these drives are in the first row of a new Norco 4220 build. =========================================================================== = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 33C, Elapsed Time: 27:35:02 ============================================================================ == == Disk /dev/sdc has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 19,20c19,20 < Offline data collection status: (0x80) Offline data collection activi < was never started. --- > Offline data collection status: (0x84) Offline data collection activi > was suspended by an interrupting comma from host. 54c54 < 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 - 9 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 10 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 ============================================================================ root@Tower:/boot# =========================================================================== = unRAID server Pre-Clear disk /dev/sdd = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 33C, Elapsed Time: 33:08:43 ============================================================================ == == Disk /dev/sdd has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 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 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 8 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 9 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 ============================================================================ root@Tower:/boot# =========================================================================== = unRAID server Pre-Clear disk /dev/sde = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 33C, Elapsed Time: 32:59:13 ============================================================================ == == Disk /dev/sde has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 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 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 8 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 9 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 ============================================================================ root@Tower:/boot#