SCSI Error - Process to further identify

[sfcredfox]

Hardware listed below.

Security log provided:
hostnameremoved kernel log messages:
> (da6:mps0:0:13:0): READ(10). CDB: 28 00 01 72 01 48 00 00 08 00
> (da6:mps0:0:13:0): CAM status: SCSI Status Error
> (da6:mps0:0:13:0): SCSI status: Check Condition
> (da6:mps0:0:13:0): SCSI sense: RECOVERED ERROR asc:18,2 (Recovered data - data auto-reallocated)
> (da6:mps0:0:13:0): Info: 0x172014b
> (da6:mps0:0:13:0): Actual Retry Count: 3

GUI Shows:
-Both volumes are healthy
-Disk shows online under volume1 (which da6 is a member)
-Smartctl output attached, I don't see an errors posted in the self-test log *SMARTCTL.TXT*
(likely I'm missing something or don't understand something in the output)

Questions
What else should I be checking?
Sit back and wait for the disk to actually fail?
Is this a bad sector error I need to find by running a long test?
How does FreeBSD/FreeNAS present that? Just like this? Some other tell-tail logs?
I run the short test every 12 hours, I was doing it every hour before. Change back? Something else?

Thanks.

 

[dlavigne]

Also post the output of zpool status within code tags. And in Volume Status, what is it saying about the last scrub?

 

[sfcredfox]

Also post the output of zpool status within code tags. And in Volume Status, what is it saying about the last scrub?

Code:

zpool status
pool: tank1
state: ONLINE
scan: scrub repaired 0 in 4h34m with 0 errors on Sun Feb 1 14:35:02 2015
config:

NAME STATE READ WRITE CKSUM
tank1 ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
gptid/31dbce50-3af4-11e4-a5b2-001cc467f92a ONLINE 0 0 0
gptid/327ae548-3af4-11e4-a5b2-001cc467f92a ONLINE 0 0 0
gptid/3319098c-3af4-11e4-a5b2-001cc467f92a ONLINE 0 0 0
gptid/33b02f32-3af4-11e4-a5b2-001cc467f92a ONLINE 0 0 0
gptid/344814a5-3af4-11e4-a5b2-001cc467f92a ONLINE 0 0 0
raidz1-2 ONLINE 0 0 0
gptid/760bf849-3af4-11e4-a5b2-001cc467f92a ONLINE 0 0 0
gptid/76a3b45e-3af4-11e4-a5b2-001cc467f92a ONLINE 0 0 0
gptid/777c9f5a-3af4-11e4-a5b2-001cc467f92a ONLINE 0 0 0
gptid/783edb9e-3af4-11e4-a5b2-001cc467f92a ONLINE 0 0 0
gptid/79194027-3af4-11e4-a5b2-001cc467f92a ONLINE 0 0 0
raidz1-3 ONLINE 0 0 0
gptid/9101fc9b-5ee1-11e4-970c-001b7857b9ca ONLINE 0 0 0
gptid/91d8de61-5ee1-11e4-970c-001b7857b9ca ONLINE 0 0 0
gptid/92affbe0-5ee1-11e4-970c-001b7857b9ca ONLINE 0 0 0
gptid/12f80e9b-603c-11e4-a1e7-001b7857b9ca ONLINE 0 0 0
gptid/942e953c-5ee1-11e4-970c-001b7857b9ca ONLINE 0 0 0
logs
gptid/70ef691f-6b8f-11e4-a62f-001b7857b9ca ONLINE 0 0 0

errors: No known data errors

Appears that there were no errors detected during scrub.
Not sure why I can't find a better cause or set of symptoms of possible bad drive.

 

[dlavigne]

Are those errors continuing in /var/log/messages or was it just a weird one-off event?

 

[sfcredfox]

Looks like it was a one time thing. I've been looking for the commands to filter the output.

**EDIT**

Possible victory - found this command from checking driver related stuff:

Code:

dmesg | grep mps

Code:

Output:
[root@Carmel-SAN ~]# dmesg | grep mps
(da6:mps0:0:13:0): READ(10). CDB: 28 00 01 72 01 48 00 00 08 00
(da6:mps0:0:13:0): CAM status: SCSI Status Error
(da6:mps0:0:13:0): SCSI status: Check Condition
(da6:mps0:0:13:0): SCSI sense: RECOVERED ERROR asc:18,2 (Recovered data - data auto-reallocated)
(da6:mps0:0:13:0): Info: 0x172014b
(da6:mps0:0:13:0): Actual Retry Count: 3

This is the only output from the above command. Hopefully that indicates this was a one time thing.

-I have not noticed any issues since.
-The drives live in an enclosure, so if it was a cable thing, should have effected all drives.
-Could be issue with enclosure, but hasn't happened since.

Weird.

I guess I'll just hope and pray it doesn't come back.