cancel
Showing results for 
Search instead for 
Did you mean: 

Drive DrivePath issue.

susindran_surul
Level 6

Hi Folks,

 

I have replaced failed drive in our library and we used to follow below steps.

 

It will show failled after removed failed drive
sudo cfgadm -al

Shake controller which has the failed tape drive
sudo /usr/sbin/cfgadm -c configure c7
 
Do a cleanup of the device files (This will leanup the device files of removed tape drive.
sudo devfsadm -C -c tape -v
 
Fix the drive and shake the controller:
sudo /usr/sbin/cfgadm -c configure c7
 
Check device files created for new drives, if not run a devfsadm and check
ls -lrt /dev/rmt
 
 
But while we are checking ls -lrt /dev/rmt its showing different name..
 
lrwxrwxrwx 1 root root 80 Aug 22 10:24 6cbn -> ../../devices/pci@7c0/pci@0/pci@8/SUNW,qlc@0,1/fp@0,0/st@w500104f0008e3044,0:cbn
 
But device path is different one.
 
$ cd /usr/openv/volmgr/bin
$ sudo ./vmoprcmd
 
HP.ULTRIUM3-SCSI.003     No           No                     No        hcart3
                                  /dev/rmt/10cbn                       DOWN-TLD
 
 
I dont no why its reflecting in /dev/rmt with 6cbn.Please let us know whats exact issue.
 
Below is error message in :-
 
Aug 22 10:49:44 avrd[5712]: [ID 239055 daemon.error] Fatal open error on HP.ULTRIUM3-SCSI.003 (device 3, /dev/rmt/10cbn), errno = 2 (No such file or directory), DOWN'ing it
Aug 22 10:50:30  last message repeated 3 times
Aug 22 10:50:46 avrd[5712]: [ID 239055 daemon.error] Fatal open error on HP.ULTRIUM3-SCSI.003 (device 3, /dev/rmt/10cbn), errno = 2 (No such file or directory), DOWN'ing
 
Thanks,
Susi.S

 

1 ACCEPTED SOLUTION

Accepted Solutions

mph999
Level 6
Employee Accredited

Yes, the replace drive option is one way, the other is just delete the old drive an use the wizard to add the new one, which is the way I generally do it.

martin

View solution in original post

4 REPLIES 4

mph999
Level 6
Employee Accredited

Follow this TN to replace the drive within NBU with the new one

or

Just delete the old drive and run the wizard to add the new.

Simply, Solaris has configured the drive with a different xcbn number, it's not an issue.

martin

susindran_surul
Level 6

Thanks martin..We also did the same after replaced old drive.Below steps i got from here only.

/usr/openv/volmgr/bin/tpautoconf -report_disc

This produces information similar to the following:

======================= New Device (Tape) ============
Inquiry = "QUANTUM DLT7000         245F"
Serial Number = PXA51S3232
Drive Path = /dev/rmt/21cbn
Found as TLD(0), Drive = 1
===================== Missing Device (Drive) =========
Drive Name = QUANTUMDLT70001
Drive Path = /dev/rmt/11cbn
Inquiry = "QUANTUM DLT7000         245F"
Serial Number = PXA51S3587
TLD(0) definition, Drive = 1
Hosts configured for this device:
Host = HOSTA
Host = HOSTB

This reports the discrepancy between the device database and the new device found. Take note of the new Drive Path for the device as this will be needed for the tpautoconf command.  To resolve this, run:

# cd /usr/openv/volmgr/bin
#./tpautoconf -replace_drive QUANTUMDLT70001 -path /dev/rmt/21cbn

mph999
Level 6
Employee Accredited

Yes, the replace drive option is one way, the other is just delete the old drive an use the wizard to add the new one, which is the way I generally do it.

martin

susindran_surul
Level 6

Thanks martin...