How I determine what drive is "ata1.00" on my array.

[deaerator]

How I determine what drive is "ata1.00" on my array.

 

I noticed this is my syslog.

Jan 21 10:04:51 Tower kernel: ata1.00: exception Emask 0x10 SAct 0xc0000 SErr 0x280100 action 0x6 frozen
Jan 21 10:04:51 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error
Jan 21 10:04:51 Tower kernel: ata1: SError: { UnrecovData 10B8B BadCRC }
Jan 21 10:04:51 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED
Jan 21 10:04:51 Tower kernel: ata1.00: cmd 60/80:90:00:d6:e6/00:00:09:00:00/40 tag 18 ncq dma 65536 in
Jan 21 10:04:51 Tower kernel:         res 40/00:98:18:11:b7/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
Jan 21 10:04:51 Tower kernel: ata1.00: status: { DRDY }
Jan 21 10:04:51 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED
Jan 21 10:04:51 Tower kernel: ata1.00: cmd 60/08:98:18:11:b7/00:00:01:00:00/40 tag 19 ncq dma 4096 in
Jan 21 10:04:51 Tower kernel:         res 40/00:98:18:11:b7/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
Jan 21 10:04:51 Tower kernel: ata1.00: status: { DRDY }
Jan 21 10:04:51 Tower kernel: ata1: hard resetting link
Jan 21 10:04:52 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 21 10:04:52 Tower kernel: ata1.00: supports DRM functions and may not be fully accessible
Jan 21 10:04:52 Tower kernel: ata1.00: NCQ Send/Recv Log not supported
Jan 21 10:04:52 Tower kernel: ata1.00: supports DRM functions and may not be fully accessible
Jan 21 10:04:52 Tower kernel: ata1.00: NCQ Send/Recv Log not supported
Jan 21 10:04:52 Tower kernel: ata1.00: configured for UDMA/133
Jan 21 10:04:52 Tower kernel: ata1: EH complete

 

tower-diagnostics-20180122-1050.zip

[trurl]

Search the syslog for "ata1.00". You should find a line that shows its serial number. Search the syslog for that serial number. You should find what disk that serial number is assigned to.

 

You can also look in your diagnostics in system/vars.txt for the serial number to see what disk it is assigned to.

 

There may be other ways but those are what I have found.

 

Looks like it is cache according to your diagnostics.

[bonienl]

You can also click on the blue disk icon of each disk on the Main page. It will show the log entries belonging to the disk, including the ata reference.

 

[trurl]

1 hour ago, bonienl said:

You can also click on the blue disk icon of each disk on the Main page. It will show the log entries belonging to the disk, including the ata reference.

 

I figured there was an easier way these days. Probably added some time since I first did it the hard way by searching the syslog. No doubt other "easter eggs" I haven't discovered in the webUI.