1838627 Members
3164 Online
110128 Solutions
New Discussion

unable to add lock disk

 
Daniel Lin_2
New Member

unable to add lock disk

Trying to add a lockdisk, I have 2 N4000 upgraded to rp7400 backpane. The lock disk I am trying to add is a external 9GB UWSE LVD (Part# C6402B) drive. The lock disk is connected to both system via external LVD PCI card on both nodes.

The scsi disk ID is 5. ioscan is not picking up the disk on either system. Any ideas? ioscan outputs from both hosts are below:

Host#1:
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 0/0/1/0.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 6x/32x
/dev/dsk/c0t2d0 /dev/rdsk/c0t2d0
disk 1 0/0/2/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST318203LC
/dev/dsk/c1t6d0 /dev/rdsk/c1t6d0
disk 2 0/0/2/1.6.0 sdisk SCAN DEVICE SEAGATE ST318203LC
/dev/dsk/c2t6d0 /dev/rdsk/c2t6d0

# ioscan -funC ctl
Class I H/W Path Driver S/W State H/W Type Description
====================================================================
ctl 0 0/0/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ctl 1 0/0/2/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ctl 2 0/0/2/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
ctl 5 0/4/0/0.6.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t6d0
ctl 6 0/4/0/1.6.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c4t6d0

# ioscan -funC ext_bus
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
ext_bus 0 0/0/1/0 c720 CLAIMED INTERFACE SCSI C895 Ultra Wide Single-Ended
ext_bus 1 0/0/2/0 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
ext_bus 2 0/0/2/1 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
ext_bus 3 0/4/0/0 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide LVD
ext_bus 4 0/4/0/1 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide LVD


host#2:
# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 3 0/0/1/0.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 6x/32x
/dev/dsk/c0t2d0 /dev/rdsk/c0t2d0
disk 0 0/0/2/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST318203LC
/dev/dsk/c1t6d0 /dev/rdsk/c1t6d0
disk 1 0/0/2/1.6.0 sdisk CLAIMED DEVICE SEAGATE ST318203LC
/dev/dsk/c2t6d0 /dev/rdsk/c2t6d0
# ioscan -funC ctl
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
ctl 0 0/0/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ctl 1 0/0/2/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ctl 2 0/0/2/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
ctl 7 0/12/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c9t7d0
ctl 8 0/12/0/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c10t7d0
# ioscan -funC ext_bus
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
ext_bus 0 0/0/1/0 c720 CLAIMED INTERFACE SCSI C895 Ultra Wide Single-Ended
ext_bus 1 0/0/2/0 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
ext_bus 2 0/0/2/1 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
ext_bus 9 0/12/0/0 c720 CLAIMED INTERFACE SCSI C896 Ultra2 Wide LVD
ext_bus 10 0/12/0/1 c720 CLAIMED INTERFACE SCSI C896 Ultra2 Wide LVD



6 REPLIES 6
Sanjay_6
Honored Contributor

Re: unable to add lock disk

Hi Daniel,

Seems like you are using SCSI F/W diff controllers to connect these disks. Make sure that the controller ids are different on the two servers. If one of the controller is at scsi id 7, the other system's scsi controller should be at a different id,say 6 if the two are connected to scsi devices on the shared / same channel.

Hope this helps.

Regds
Rita C Workman
Honored Contributor

Re: unable to add lock disk

On my rp7410, the UWSE LVD show as using drive c8xx....do you have that driver set up in your kernel ???

Rita
Steven E. Protter
Exalted Contributor

Re: unable to add lock disk

It may be scsi id, it may be instance numbering.

What i mean by that is that the ct9xx driver is different because the two systems have had different peripherial practice over the years.

You can renumber peripherals if you wish and are careful.

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&admit=-1335382922+1098718644131+28353475&docId=200000067424466

It woukd be a good idea to make sure the SCSI id is not in conflict.

Also here is a test to check existing disks.

echo "hex id of disk" | adb /dev/dsk/c4t8d0

example

echo "0x2008?4D" | adb /dev/dsk/c4t8d0

This will display LVM header information on the disk. It should allow you to determine which disk has what driver instance name.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Daniel Lin_2
New Member

Re: unable to add lock disk

If I am intepreting the ioscan data correctly, the scsi id are:

host1:
ext_bus path is 0/4
ctl scsi id is 6

host2:
ext_bus path is 0/12
ctl scsi id is 7

I should see additional disks that are added in addition to the 2 HDD on each node. The issue is that ioscan is not seeing the disk.

Once I can see the disk from ioscan, I would also expect to see disk of /dev/rdsk/c4t5d0 and /dev/rdsk/c9t5d0 on host1 and 2 respectively once I do insf.
G. Vrijhoeven
Honored Contributor

Re: unable to add lock disk

Daniel,

I agree with you.
If you are sure about the 0/4 and 0/12 the scsi id = the second number so 6 / 7.

The disk and controllers both are Ultra2 Wide LVD. So that could not be the problem...
If you are sure you connected:
Host A: 0/4/0/1.6.0 to Host B :0/12/0/0.7.0
i agree on the expected scsi id-s.

Could termination be the problem, or could it be an other device on the bus also has scsi id 5?
If not may be you can take a look at the scsi bus using stm on one server.

Regards,

Gideon
Stephen Doud
Honored Contributor

Re: unable to add lock disk

If you are not using "fencing" software, then these reasons are at the root:
- hardware failure of the disk or chassis backplane
- SCSI addressing
- disk driver
- your understanding of the location of the disk.

Can the disk be moved to another position in the chassis and be seen?

PCI SCSI controllers addresses are changed at BCH - before the system is booted.

disk SCSI addresses are either slot-location dependent, or addressed via a switch bank or array software.

If other disks of like type are seen in ioscan, then the driver is not at fault.

Suggest you disconnect the disk bus from one server and do an ioscan on the other server. Run 'insf -e' if the disk is still not present.

Are you certain the disk is on the path you think it is on?

-SD.