HAL resource allocation retry count : 0
Flash f/w update count : 0
No resource to ACK count : 0
No resource to process Device event count : 0
No resource to process PHY event count : 0
Reply frame bounds error count : 0
Reply frame offset error count : 0
Stale tag count : 0
Context Reply for non-IO count : 0
Tag bounds check fail count : 0
Heart Beat bad reply status count : 0
Internal reply bad status count : 0
Bad device page 0 status count : 0
Internal request timeout count : 0
No resource for heartbeat count : 0
Discovery error. Loop detected : 0
Discovery error. Unaddressed device found : 0
Discovery error. Duplicate SAS address found : 0
Discovery error. Expander error : 0
Discovery error. SMP timeout : 0
Discovery error. Expander route table OOF entries : 0
Discovery error. Non-existing route table indices : 0
Discovery error. SMP function failed : 0
Discovery error. SMP CRC error : 0
Discovery error. XLE subtractive found : 0
Discovery error. Table to Table : 0
Discovery error. XLE paths found : 0
Discovery error. Max no. of SATA targets reached : 0
No. of Unknown Events received : 0
Probe Statistics
No. of ioscans : 1
No. of ioscan failures : 0
No. of times Chip went offline of ioscans : 0
No. of times Chip went to Trans state : 20
No. of HAL query successes : 0
No. of HAL query failures : 0
No. of times times HAL returned busy : 0
No. of times memory allocation failed : 0
No. of devices that timed out : 0
No. of times Target opens was sent : 5
No. of times open failed : 0
No. of times close was sent : 5
No. of open attempts : 0
No. of times Inquiry was sent : 5
No. of times Inquiry failed : 0
No. of times Report LUN was sent : 0
No. of times Report LUNs failed : 0
Target Statistics
No. of Domain discoveries done : 2
No. of Implicit discoveries done : 0
You can use the following command to trace the origin of a disk problem. The following command
will display PHY status and history for the controller with the device file /dev/sasd0. In this
example, the field “No. of times PHY went Down” indicates failures on PHY 5 and PHY 6, and
the field “Time PHY went Down” lists the time that the problem occurred:
# sasmgr get_stat -D /dev/sasd0 -q phy=all
Tue Dec 12 03:00:02 2006
Statistics for PHY ID : 0
No. of times PHY came UP : 1
Time PHY came UP : Wed Dec 31 19:00:00
62
Configuring and Troubleshooting the Controller Online
