Identify Hard Disks

[Alan Garner]

I have 6 physical disks installed in slots 3-8 on my rx3600 running v31...

If I know the device file is c0t0d0 and the hardware path is 0/4/1/0.0.0.0.0 how do I translate that into the actual drive slot that disk resides?

I hope I made sense!

Thanks.

[A. Clay Stephenson · Accepted solution]

Probably the easist method that works independent of hardware is the "winky-blinky" test.

dd if=/dev/rdsk/c0t0d0 bs=1k count=5000 of=/dev/null

and watch for the flashing LED on the drive.

[Alan Garner]

Thank you. That did the trick. Now about the results...

All 6 disks responded to the "ping" if you will but that means there is no cxtxdx file for my DVD drive. That's wierd because I just used it to cold instll the system this morning! It worked to install the system but now there is no device file for it so therefore I mount it for use! I ran an insf -e to regenerate all the device files to no avail.

Any other suggestions?

[A. Clay Stephenson]

Do this:

ioscan -fn
insf
ioscan -fn -C disk and see if your CD/DVD drive isn't now listed.

[Alan Garner]

No dice! What else can I try?

[Tim Nelson]

running 'ioscan -kfnC disk' should show you the disks and DVD

[A. Clay Stephenson]

Post the output of "ioscan -fn".

[Alan Garner]

Class I H/W Path Driver S/W State H/W Type Description
===================================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (4030)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
tty 0 0/0/1/0 rmp3f01 CLAIMED INTERFACE PCI class(255,0) (103c1303)
tty 1 0/0/1/1 rmp3f01 CLAIMED INTERFACE PCI SimpleComm (103c1302)
tty 2 0/0/1/2 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/diag/mux2 /dev/mux2 /dev/tty2p0
OO 0 0/0/2/0 UsbOhci CLAIMED INTERFACE PCI SerialBus (10330035)
OO 1 0/0/2/1 UsbOhci CLAIMED INTERFACE PCI SerialBus (10330035)
OO 3 0/0/2/1.0 UsbMiniBus CLAIMED INTERFACE OO Device Driver
OO 5 0/0/2/1.0.0 UsbBulkOnlyMS CLAIMED DEVICE OO Device Driver
disk 1 0/0/2/1.0.16 UsbScsiAdaptor CLAIMED DEVICE OO Device Driver
/dev/deviceFileSystem/Usb/MassStorage/dsk/disk@hp-1008+294=A60020000001
/dev/deviceFileSystem/Usb/MassStorage/rdsk/disk@hp-1008+294=A60020000001
OO 6 0/0/2/2 UsbEhci CLAIMED INTERFACE PCI SerialBus (103300e0)
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
slot 0 0/1/1 pci_slot CLAIMED SLOT PCI Slot
slot 1 0/1/2 pci_slot CLAIMED SLOT PCI Slot
ba 2 0/2 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
slot 2 0/2/1 pci_slot CLAIMED SLOT PCI Slot
ba 3 0/3 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
slot 3 0/3/1 pci_slot CLAIMED SLOT PCI Slot
lan 0 0/3/1/0 iether CLAIMED INTERFACE HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
lan 1 0/3/1/1 iether CLAIMED INTERFACE HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
ba 4 0/4 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
slot 4 0/4/1 pci_slot CLAIMED SLOT PCI Slot
escsi_ctlr 0 0/4/1/0 sasd CLAIMED INTERFACE HP PCI/PCI-X SAS MPT Adapter
/dev/sasd0
ext_bus 0 0/4/1/0.0.0 sasd_vbus CLAIMED INTERFACE SAS Device Interface
target 0 0/4/1/0.0.0.0 tgt CLAIMED DEVICE
disk 8 0/4/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DG146ABAB4
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
target 2 0/4/1/0.0.0.1 tgt CLAIMED DEVICE
disk 2 0/4/1/0.0.0.1.0 sdisk CLAIMED DEVICE HP DG146ABAB4
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
target 5 0/4/1/0.0.0.2 tgt CLAIMED DEVICE
disk 4 0/4/1/0.0.0.2.0 sdisk CLAIMED DEVICE HP DG146ABAB4
/dev/dsk/c0t2d0 /dev/dsk/c0t2d0s2 /dev/rdsk/c0t2d0 /dev/rdsk/c0t2d0s2
/dev/dsk/c0t2d0s1 /dev/dsk/c0t2d0s3 /dev/rdsk/c0t2d0s1 /dev/rdsk/c0t2d0s3
target 4 0/4/1/0.0.0.3 tgt CLAIMED DEVICE
disk 3 0/4/1/0.0.0.3.0 sdisk CLAIMED DEVICE HP DG146ABAB4
/dev/dsk/c0t3d0 /dev/rdsk/c0t3d0
target 1 0/4/1/0.0.0.4 tgt CLAIMED DEVICE
disk 7 0/4/1/0.0.0.4.0 sdisk CLAIMED DEVICE HP DG146ABAB4
/dev/dsk/c0t4d0 /dev/rdsk/c0t4d0
target 3 0/4/1/0.0.0.5 tgt CLAIMED DEVICE
disk 5 0/4/1/0.0.0.5.0 sdisk CLAIMED DEVICE HP DG146ABAB4
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
target 6 0/4/1/0.0.0.6 tgt CLAIMED DEVICE
disk 6 0/4/1/0.0.0.6.0 sdisk CLAIMED DEVICE HP IR Volume
/dev/dsk/c0t6d0 /dev/dsk/c0t6d0s2 /dev/rdsk/c0t6d0 /dev/rdsk/c0t6d0s2
/dev/dsk/c0t6d0s1 /dev/dsk/c0t6d0s3 /dev/rdsk/c0t6d0s1 /dev/rdsk/c0t6d0s3
slot 5 0/4/2 pci_slot CLAIMED SLOT PCI Slot
lan 2 0/4/2/0 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
lan 3 0/4/2/1 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
ba 5 0/5 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
slot 6 0/5/1 pci_slot CLAIMED SLOT PCI Slot
slot 7 0/5/2 pci_slot CLAIMED SLOT PCI Slot
ba 6 0/6 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
slot 8 0/6/1 pci_slot CLAIMED SLOT PCI Slot
ba 7 0/7 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
slot 9 0/7/1 pci_slot CLAIMED SLOT PCI Slot
lan 4 0/7/1/0 iether CLAIMED INTERFACE HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
lan 5 0/7/1/1 iether CLAIMED INTERFACE HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
processor 0 120 processor CLAIMED PROCESSOR Processor
processor 1 121 processor CLAIMED PROCESSOR Processor
ba 8 250 pdh CLAIMED BUS_NEXUS Core I/O Adapter
ipmi 0 250/0 ipmi CLAIMED INTERFACE IPMI Controller
/dev/ipmi
tty 3 250/1 asio0 CLAIMED INTERFACE Built-in RS232C
/dev/diag/mux3 /dev/mux3 /dev/tty3p0
acpi_node 0 250/2 acpi_node CLAIMED INTERFACE Acpi Hardware

[Bill Hassell]

Since ioscan can't see the DVD, the drive has malfunctioned. Did you connect another SCSI device onto the system without checking for overlapping addresses?

As far as installing, the ability to boot off the DVD has nothing to do with HP-UX and it's ability to see the drive. When cold-installing, you are using only the processor ROMs. Once HP-UX is running, then insf and ioscan will probe all addresses for devices and create the necessary device files. If ioscan does not report a CD/DVD drive then you have a hardware problem. I am ASSUMING that this is a standard HP SCSI CD/DVD that came with the system and not an add-on connected with USB or some other interface.

[Alan Garner]

That is correct...nothing new, just orginal hardware. Now that I think of it, maybe its a version issue. The server came with v2 and the DVD was present as c0t0d0 and had a description of TEAC. I then mounted it and used it to UPGRADE to v3. That was last week. I ve not had the need to use it so I don't know if it was present after the upgrade or not!

I guess I'll spend the rest of the day on the phone with HP!

Thank you for all your help and quick response!

[Torsten.]

OK, this is 11.31.

Your DVD is here:

disk 1 0/0/2/1.0.16 UsbScsiAdaptor CLAIMED DEVICE OO Device Driver
/dev/deviceFileSystem/Usb/MassStorage/dsk/disk@hp-1008+294=A60020000001
/dev/deviceFileSystem/Usb/MassStorage/rdsk/disk@hp-1008+294=A60020000001

I would siggest to create a shortcut (link) to this device.

The naming is due to the fact this is an USB drive.




To get more info about your disks run

$ sasmgr get_info -D /dev/sasd0

$ sasmgr get_info -D /dev/sasd0 -q lun=all -q lun_locate

More info is here:
man sasmgr

(how to switch "blink on" the disk)

[Torsten.]

Try to do something like this:

ln -s dev/deviceFileSystem/Usb/MassStorage/dsk/disk@hp-1008+294=A60020000001 /dev/cdrom

Now you can do

mount /dev/cdrom /mount_point


What else you can get from this ioscan?

For example this:

Your disks are mirrored:

disk 6 0/4/1/0.0.0.6.0 sdisk CLAIMED DEVICE HP IR Volume

(IR = integrated RAID)

[Torsten.]

@Bill:

"I am ASSUMING that this is a standard HP SCSI CD/DVD that came with the system and not an add-on connected with USB or some other interface."


This is *standard* but USB in this model.

[Alan Garner]

Did as suggested...no dice! Output to follow:

root@hpuxtest [ /root ]# mount /dev/cdrom /cdrom
mount: /dev/cdrom: No such file or directory
root@hpuxtest [ /root ]# find / -name cdrom
/dev/cdrom
/cdrom

...and...I know its there because...

root@hpuxtest [ /root ]# ll /dev/cd*
lrwxrwxrwx 1 root sys 70 Jun 27 15:37 /dev/cdrom -> dev/deviceFileSystem/Usb/MassStorage/dsk/disk@hp-1008+294=A60020000001


I have a open support case with HP. They are "researching" the issue and will call me back...that was an hour ago. They mentioned something about a firmware issue???

[Torsten.]

one point to add here:

It is a new server model running a new OS version - there MUST be something different ;-)




You will find this useful:

http://docs.hp.com/en/J6369-90045/index.html
HP 8 Internal Port SAS Controller Users Guide: HP-UX 11i v2, 11i v3

----

Regarding the disk locator:

info about disks

# sasmgr get_info -D /dev/sasd0 -q lun=all -q lun_locate

turn on blinking for disk c1t1d0

# sasmgr set_attr -D /dev/sasd0 -q lun=/dev/rdsk/c1t1d0 -q locate_led=on

[Torsten.]

Is your link wrong?

dev/deviceFileSystem/Usb/MassStorage/dsk/disk@hp-1008+294=A60020000001

(missing / at the beginning)

[Alan Garner]

OK now were gettin' somewhere!

That seemed to have worked. It mounted and if I ls /cdrom (my mount point) then I can see the contents of the Applications DVD. Thank you very much. Funny how HP hardware and software tech support did not see this!

[Torsten.]

Fine!

Sometimes you simply cannot see every single character and you will miss the most important one ...

Say some greetings to the support people ...

;-)

Have fun!

[Alan Garner]

Solution found. Apearently the server sees the DVD device as a USB device. Following the instructions (from Torsten above) to make a symbolic link to the block device file worked.

Thanks to all that helped!