San wwn errors in syslog

[likid0]

Hy,

A couple of days ago I had a powerout, and all my servers crashed, everything is ok again, exect for this messasges i'm gettin in the syslog of vpars(boot from san) in an rx7620:

Feb 16 08:30:02 above message repeats 3 times
Feb 16 08:27:50 vmunix: Convert To h/w path: hw_path = 1/0/4/1/0.6.140.0.0.0.0s
Feb 16 08:33:51 vmunix: Convert To h/w path: = <3a050000, 5005076801104803, 4000000000000000>
Feb 16 08:33:51 vmunix: Convert To h/w path: hw_path = 1/0/4/1/0.6.140.0.0.0.0

this lun is one of the disks in vg00, all lvols are synced and look ok. but when i try to boot from it I get:

vPar "vpa" failed to load the kernel due to: non-bootable boot media; incorrect vPars software installed; or incorrect boot media EFI path in vPars database.
Try using "vparload -p vpa -E 0" to load the vPar.
Error loading "vpa". Shutting down "vpa"...

I did and efi update(vparefiutil -u), but I get the same on the four vpars on the server.

Any idea what the message is about ?

[likid0]

just to share more data, on the servers I have tachylon and fcd cards. the messages are all coming fron the tachylon cards, on the efi when booting I ger this error:

HP XL2 Fibre Channel Driver: Discovery and Configuration of devices might take several minutes....fc_locate FAILED
done

and then the:

Selected boot option: 1/0/2/1/0.5.142.0.0.0.0

Loading.: 1/0/2/1/0.5.142.0.0.0.0

Load of 1/0/2/1/0.5.142.0.0.0.0 failed: Not Found


I have no problem booting from the other fc hba card.

Looks like it can't scan the san disks on boot.


Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
fc 0 1/0/2/1/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
/dev/td0
fc 1 1/0/12/1/0/4/0 fcd CLAIMED INTERFACE HP AD193-60001 PCI/PCI-X Fibre Channel 1-port 4Gb FC/1-port 1000B-T Combo Adapter (FC Port 1)
/dev/fcd1

[Steven E. Protter · Accepted solution]

Shalom,

I think either a fiber card is bad, or there is bad media (fiber cable or network).

Use mstm cstm or xstm and to check all the available hardware. Visually inspect the media.

SEP

[likid0]

What's strange is that I am getting the error on the tachyon Hba.

I have opened a case with HP, i will leave the trhread open, so I can close it with the answer they give me.

Thnx.

[sujit kumar singh]

Hi


do you have some disks attached to the Tachyon card, also can do few things likw.

#fcmsutil /dev/td0
#ioscan -kfnH
#ioscan -fnC disk

IF the disk disconnection/LUN Disconnection us there dd also can be used to read some data from the HDDs /LUNs on /dev/td0.


also once in the EFI you can try by doing:
Shell> reconnect -r
Shell> map -r


or From the MON can also try

MON>scan


Properly boot in npar/vapr mode to have the access to MP etc

regards
sujit