SMART Errors on SAS/SCSI Drive

[Jaybau]

I'm getting SMART errors on SAS/SCSI disks.  

I also have the same problem with a different SAS/SCSI drive.

There's also some drive intermittent drive buzzing noise that seems related to accessing the GUI self-test web page.  I also think I get disk temperature warnings from this web page/screen too.

 

This is an unmounted disk, no data, zero'd.

 

I've run pre-clear, and there's no reported errors.

 

I'm new to SAS/SCSI, so I don't know what normal should be.  I don't see the same same kind of SMART information on SATA drives.

 

The "Errors Corrected by ECC" are very concerning to me, but I don't know if that's bad, normal, an uncorrectable problem.

 

 

 

####################################################################################################
#                           Unraid Server Preclear of disk 5000c500863f5d47                        #
#                            Cycle 1 of 1, partition start on sector 64.                           #
#                                                                                                  #
#   Step 1 of 5 - Pre-read verification:                   [9:12:23 @ 181 MB/s] SUCCESS            #
#   Step 2 of 5 - Zeroing the disk:                        [9:12:41 @ 181 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:                  [9:12:11 @ 181 MB/s] SUCCESS            #
#                                                                                                  #
#                                                                                                  #
#                                                                                                  #
####################################################################################################
#       Cycle elapsed time: 27:37:23 | Total elapsed time: 27:37:23                                #
####################################################################################################

--> RESULT: Preclear Finished Successfully!.

 

 

 

tower-diagnostics-20220520-0719.zip

[JorgeB]

28 minutes ago, Jaybau said:

normal,

It's normal, SAS SMART is very different from ATA SMART, from my experience, which is not much with SAS, you wan to monitor "Elements in grown defect list" and "total uncorrected errors" which should both stay 0.

[Jaybau]

Might "blk_update_request: protection error" or "Buffer I/O error" be a problem?

 

May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] Enabling DIF Type 2 protection
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] 4096-byte physical blocks
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] Write Protect is off
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] Mode Sense: db 00 10 08
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] Write cache: disabled, read cache: enabled, supports DPO and FUA
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] tag#1685 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=DRIVER_OK cmd_age=0s
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] tag#1685 Sense Key : 0x5 [current]
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] tag#1685 ASC=0x10 ASCQ=0x3
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] tag#1685 CDB: opcode=0x7f, sa=0x9
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] tag#1685 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] tag#1685 CDB[10]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08
May 20 13:00:10 Tower kernel: blk_update_request: protection error, dev sdf, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
May 20 13:00:10 Tower kernel: Buffer I/O error on dev sdf, logical block 0, async page read
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] tag#1686 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=DRIVER_OK cmd_age=0s
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] tag#1686 Sense Key : 0x5 [current]
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] tag#1686 ASC=0x10 ASCQ=0x3
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] tag#1686 CDB: opcode=0x7f, sa=0x9
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] tag#1686 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00
May 20 13:00:10 Tower kernel: sd 6:0:0:0: [sdf] tag#1686 CDB[10]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08
May 20 13:00:33 Tower kernel: blk_update_request: protection error, dev sdf, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
May 20 13:00:33 Tower kernel: Buffer I/O error on dev sdf, logical block 0, async page read
...
May 20 13:00:37 Tower emhttpd: ST6000NM0095_ZAD3Q4NJ0000C829A6YY_35000c50095310bef (sdf) 512 11721045168
May 20 13:00:37 Tower emhttpd: read SMART /dev/sdf
May 20 13:01:01 Tower kernel: sd 6:0:0:0: [sdf] tag#1714 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=DRIVER_OK cmd_age=0s
May 20 13:01:01 Tower kernel: sd 6:0:0:0: [sdf] tag#1714 Sense Key : 0x5 [current]
May 20 13:01:01 Tower kernel: sd 6:0:0:0: [sdf] tag#1714 ASC=0x10 ASCQ=0x3
May 20 13:01:01 Tower kernel: sd 6:0:0:0: [sdf] tag#1714 CDB: opcode=0x7f, sa=0x9
May 20 13:01:01 Tower kernel: sd 6:0:0:0: [sdf] tag#1714 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 02
May 20 13:01:01 Tower kernel: sd 6:0:0:0: [sdf] tag#1714 CDB[10]: ba a0 f4 a0 ba a0 f4 a0 00 00 00 00 00 00 00 08

 

[JorgeB]

Problem yes, but not necessarily a disk problem.