[Solved] Disk Error Advice

[dstark4]

Hello, I am experiencing issues with a new server. It has put a disk in an error twice so far, with (Dec 21 20:36:32 Tower kernel: print_req_error: critical target error, dev sde, sector 6442451176). This harddrive is passing smart tests and I have attached the smart report. It is attached to an lsi 9300 hba.

 

Any suggestions are greatly appreciated.

tower-smart-20201221-2108.zip

 

 

edit: Updating the hba appears to have stopped this error from occurring again

Edited January 2, 2021 by dstark4

[trurl]

If possible before rebooting and preferably with the array started
Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

[dstark4]

Here's the diagnostics, I believe I have not rebooted between error coming up again. (Lack of sleep on my end)tower-diagnostics-20201222-1213.zip

[trurl]

On 12/21/2020 at 9:21 PM, dstark4 said:

Dec 21 20:36:32 Tower kernel: print_req_error: critical target error, dev sde, sector 6442451176

This doesn't appear in syslog in your diagnostics so you rebooted after that. There were probably some other lines in syslog that went with that one that might have given more information. Don't see anything wrong with disk and nothing in syslog indicating a problem now.

 

Is your controller using IT Mode? I notice it isn't identifying the disks by serial number.

 

Looks like rebuild was working without issue when you took those diagnostics. I suspect it hasn't complete yet since it is 10TB. Is it still rebuilding OK?

[dstark4]

13 hours ago, trurl said:

This doesn't appear in syslog in your diagnostics so you rebooted after that. There were probably some other lines in syslog that went with that one that might have given more information. Don't see anything wrong with disk and nothing in syslog indicating a problem now.

 

Is your controller using IT Mode? I notice it isn't identifying the disks by serial number.

 

Looks like rebuild was working without issue when you took those diagnostics. I suspect it hasn't complete yet since it is 10TB. Is it still rebuilding OK?

Yes it is in IT Mode, could the diagnostics being anonymized be why it does not show up?

It was rebuilding at the time I uploaded. Yes it takes ~14hrs, it was the second time rebuilding because of that particular drive putting the array in error state.

 

Model Family:     Seagate Enterprise Capacity 3.5 HDD
Device Model:     ST10000NM0086-2AA101
Serial Number:    ZA2CNXB7

 

[dstark4]

Well it did it again. Attached diagnostics, and below this appears to be the relevant info from the log for the drive.

 

I am going to go ahead and update the LSI 9300 firmware, but to me this seems to be a harddrive problem.

 

If there a large number of bad sectors should it not fail smart tests? I'd like to gather the info to warranty return the drive.

 

Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 Sense Key : 0x5 [current]
Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 ASC=0x20 ASCQ=0x0
Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 CDB: opcode=0x88 88 00 00 00 00 04 03 84 5c 28 00 00 01 00 00 00
Dec 25 02:01:23 Tower kernel: print_req_error: critical target error, dev sde, sector 17238875176
Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 Sense Key : 0x5 [current]
Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 ASC=0x20 ASCQ=0x0
Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 CDB: opcode=0x8a 8a 00 00 00 00 04 03 84 5c 28 00 00 01 00 00 00
Dec 25 02:01:23 Tower kernel: print_req_error: critical target error, dev sde, sector 17238875176

tower-diagnostics-20201225-1015.zip

[JorgeB]

Disk looks fine on SMART, I would recommend updating the firmware first, since it's very old and has known issues, you can easily do it inside Unraid.

[JorgeB]

Note that you'll need to do  a new config after the update because the disk's ID will change, one of the known issues with that old firmware.