Need help identifying HW Path to Slot on rx6600

[Mike Shisko_1]

I need a hand identifying which slot is the slot reporting this hardware error:
target 100 0/4/1/0.0.0.0 tgt NO_HW DEVICE
disk 1 0/4/1/0.0.0.0.0 sdisk NO_HW DEVICE HP DG072BABCE
/dev/dsk/c1t0d0 /dev/dsk/c1t0d0s2 /dev/rdsk/c1t0d0 /dev/rdsk/c1t0d0s2
/dev/dsk/c1t0d0s1 /dev/dsk/c1t0d0s3 /dev/rdsk/c1t0d0s1 /dev/rdsk/c1t0d0s3

I'm guessing it's slot 1, however there is nothing in the service manual which identifies the slot-to-HW location.
Any help is appreciated. Thanks.

[Steven E. Protter]

Shalom,

If you compare server documentation at http://docs.hp.com to standard ioscan or ioscan -fnC disk output you will get your answer.

I'm already thinking this is a 11.31 system with c1t0d0 disk in standard configuration, one for EFI, one for the hpux boot loader and the last one p2 intended for an OS install.

SEP

[TTr]

http://docs.hp.com/en/5992-1908/ch04s01.html

[Torsten.]

Try

# sasmgr get_info -D /dev/sasd0 -q raid

[Torsten.]

Example output:

# sasmgr get_info -D /dev/sasd0 -q raid


---------- PHYSICAL DRIVES ----------
LUN dsf SAS Address Enclosure Bay Size(MB)

/dev/rdsk/c1t0d0 0x5000c50005dc1234 1 7 140014
/dev/rdsk/c1t1d0 0x5000c50005dc1234 1 8 140014



I think this is exactly what you are looking for.

[TTr]

Yes it is slot #1. Look in page 208 of
http://docs.hp.com/en/AB464-9003C-ed7/AB464-9003C-ed7.pdf

[rick jones]

When/If you should ever be running Linux on Integrity hardware, you can use:

http://pcitop.berlios.de/

to extract information about the PCI slots and such.

[Mike Shisko_1]

Thanks to all who replied.

Torsten's response seemed to have hit the nail on the head with us trying to find the slot number. For whatever reason, Slot 1 had disappeared altogether after running patches on the server. When we ran # sasmgr get_info -D /dev/sasd0 -q raid, it was the only one missing from the output, and the HW patch seemed to match up perfect. We replaced Slot 1, and the disk is working once again. Thanks!

[Mike Shisko_1]

Solution has been found in previous posts.

[R.K. #]

Hi Mike..

It is good to see you found solution.

>Thanks to all who replied.

A humble request:
Kindly assign points to people who spent their time to help you out.


Thanks..

[Torsten.]

What patches did you install? Any SAS driver update or firmware update?


See

http://docs.hp.com/en/14556/sas_fw_update-e3.pdf

[Mike Shisko_1]

Opps. I meant to say the HW path matched up perfect, not patch. I'm not sure what patches were run, it was the customer who was controlling the box in India.