Listing Internal Drive on an IA Server

[Nellian]

I know that ioscan -fnc disk gives me the list od Disk drives on the server, but how do I know which ones are internal?
here is the uname -a out put from my server...
# uname -a
HP-UX thorhp67 B.11.23 U ia64 3938847912 unlimited-user license


and here is the ioscan -fnC disk output

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
============================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GMAS3735NC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
/dev/dsk/c2t0d0s1 /dev/rdsk/c2t0d0s1
/dev/dsk/c2t0d0s2 /dev/rdsk/c2t0d0s2
/dev/dsk/c2t0d0s3 /dev/rdsk/c2t0d0s3
disk 2 0/4/1/0.0.0.0.0.0 sdisk CLAIMED DEVICE SEAGATE ST39103F CLAR09
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
/dev/dsk/c5t0d0s1 /dev/rdsk/c5t0d0s1
/dev/dsk/c5t0d0s2 /dev/rdsk/c5t0d0s2
/dev/dsk/c5t0d0s3 /dev/rdsk/c5t0d0s3
disk 4 0/4/1/0.0.2.0.0.0 sdisk CLAIMED DEVICE SEAGATE ST39103F CLAR09
/dev/dsk/c7t0d0 /dev/rdsk/c7t0d0
disk 5 0/4/1/0.0.3.0.0.0 sdisk CLAIMED DEVICE SEAGATE ST39103F CLAR09
/dev/dsk/c8t0d0 /dev/rdsk/c8t0d0
disk 6 0/4/1/0.0.4.0.0.0 sdisk CLAIMED DEVICE SEAGATE ST39103F CLAR09
/dev/dsk/c9t0d0 /dev/rdsk/c9t0d0
/dev/dsk/c9t0d0s1 /dev/rdsk/c9t0d0s1
/dev/dsk/c9t0d0s2 /dev/rdsk/c9t0d0s2
/dev/dsk/c9t0d0s3 /dev/rdsk/c9t0d0s3
disk 7 0/4/1/0.0.5.0.0.0 sdisk CLAIMED DEVICE SEAGATE ST39103F CLAR09
/dev/dsk/c10t0d0 /dev/rdsk/c10t0d0
disk 8 0/4/1/0.0.6.0.0.0 sdisk CLAIMED DEVICE SEAGATE ST39103F CLAR09
/dev/dsk/c11t0d0 /dev/rdsk/c11t0d0

[TKeller]

It looks that you have the following:

1 DVD internal drive
1 internal disk drive (HP 73.4GMAS3735NC)
6 SAN disk connections (Clarion array of seagate disks)

Without looking anywhere else, that's what I get out of it. We have a similar setup:

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
disk 0 0/0/3/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-B
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
disk 2 0/1/1/1.0.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c3t0d0 /dev/rdsk/c3t0d0
disk 3 0/4/1/0.1.15.0.0.0.0 sdisk CLAIMED DEVICE DGC CX500WDR10
/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
disk 4 0/4/1/0.1.31.0.0.0.0 sdisk CLAIMED DEVICE DGC CX500WDR10
/dev/dsk/c7t0d0 /dev/rdsk/c7t0d0
disk 6 0/4/1/1.22.0.0.0.0.0 sdisk CLAIMED DEVICE DGC CX500WDR10
/dev/dsk/c12t0d0 /dev/rdsk/c12t0d0
disk 5 0/4/1/1.22.10.0.0.0.0 sdisk CLAIMED DEVICE DGC CX500WDR10
/dev/dsk/c13t0d0 /dev/rdsk/c13t0d0


2 internal HP disks, 1 internal DVD, 4 CX500 clarion connections.

[Nellian]

Yeah from the output I could understand that I have one internal drive.. but imagine a situation where my internal and external drives are from the same manufacturer and of the same size... it would be much more difficult to figure out which ones are internal..

[TKeller]

True. I guess it would be a matter of looking at the paths. From what I've seen, internal disks are always on the 0/1/ path. I just checked on our rp4440, a rp3410, and another random server and all had their internal 2 disks as such:

disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GMAU3073NC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GMAU3073NC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0

You're right though, a scenario like the one you put forth would be rather confusing.

[Geoff Wild · Accepted solution]

You can tell by not only looking at ioscan -funC disk but also look at ioscan -funC fc and ext_bus

Then compare those hardware paths to disks - obiviously, the fc ones are fibre attached and ergo not internal.

Rgds...Geoff

[Josiah Henline]

What model system do you have?

Use the "model" command. Different systems have different I/O layouts.

[Josiah Henline]

Most mid-range servers have dedicated internal paths to the disks. That means that that path can only be and internal drive.

[Sandman!]

Hi,

imho...it would be easy to figure out if there was a class such as "int_bus" as opposed to "ext_bus". Moreover if the storage is direct-attached SCSI as opposed to fabric-attached then it makes it even harder to decode from the H/W path. Since fabric-attached storage has the additional 24 bit "domain.area.port" fields in the path, this makes the distinction between internal and external disks easier.

~hope it helps

[Nellian]

Thanks every one...:)

[Nellian]

Thanks every one