Missing Drive Path
Already did
OS can see devices (/dev/rmt entries)
tpconfig -d
Shows
some drives up and
some drives with missing path..
-->cfgadm -al
-->cfgadm -c configure
-----------------------------------------------------
-->Reset HBA
-----------------------------------------------------
-->Hard reset Drives in Library
-----------------------------------------------------
-->mt -t /dev/rmt/## status
output:
no such file or directory
----------------------------------------------------------
Cluster Envir
NBU 7.1
Solaris
Drives SAN attached
You didn't follow my advice (or if you did, apologies, but you have not explained that you did).
As Maianne explained, forget NBU - the cause is not NBU (although it is affected).
You need to prove at the OS level that all the drives are visible.
Do exactly these steps, do not miss any out.
1. Remove the drives from NBU config
2. Remove the /dev/rmt/ files
3. Run devfsadm or reboot server
4. Run cfgadm -al - do you see all the drives, if so, goto 6, if not goto 5
5. Run cfgadm -al -o show_FCP_dev , do you see all the devices
(If any are missing you have an OS / device issue) - if they are all there continue
5b. Confirm all the drives have a device file in /dev/rmt
5c. Confirm all the drives respond to this command
/usr/openv/volmgr/bin/scsi_command -d /dev/rmt/0cbn/usr/openv/volmgr/bin/scsi_command -d /dev/rmt/1cbn/usr/openv/volmgr/bin/scsi_command -d /dev/rmt/2cbn(Substitute in each device file, 0cbnm, 1cbn, 2cbn etc ...)For each drive, the command should give details like this:Inquiry data: removable dev type 1h HP DAT72X6 B6046. Run scan, do you see all the devices, if not rebuild the sgdriver like this
7. (Follow these commands exactly ...)
cd /usr/openv/volmgr/bin/drivercp sg.conf sg.conf.safecp sg.links sg.links.safe../sg.build all (should not need mt /-mt options, drives will be using WWN)modunload -i $(echo $(modinfo |grep "sg (SCSA" |awk '{print $1}'))mv /kernel/drv/sg.conf /kernel/drv/sg.conf.old/usr/openv/volmgr/bin/driver/sg.install8. Run scan - do you see all the devices, if so, configure the drive in NBU - if not you have device issues.
Until scan shows the devices, do not run any other NBU commands.
Martin