- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- unable to add lock disk
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2004 07:19 AM
10-25-2004 07:19 AM
unable to add lock disk
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2004 07:24 AM
10-25-2004 07:24 AM
Re: unable to add lock disk
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2004 07:29 AM
10-25-2004 07:29 AM
Re: unable to add lock disk
Rita
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2004 07:30 AM
10-25-2004 07:30 AM
Re: unable to add lock disk
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
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2004 07:41 AM
10-25-2004 07:41 AM
Re: unable to add lock disk
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2004 08:41 AM
10-25-2004 08:41 AM
Re: unable to add lock disk
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2004 01:51 AM
10-28-2004 01:51 AM
Re: unable to add lock disk
- 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.