06-05-2017 10:11 AM
Hi - Could someone tell me how can i check the drive path of newly replaced drive to reconfigure it.
I could see the drive serial number updated in scan command , however when i run the report_disc it does not report the new device , only missing devices are reporting.
I check in scsi ourput also that doesnot show up the serail number or drivepath.
Linux Redhat
NBU773
Solved! Go to Solution.
06-06-2017 02:50 PM
Thank you for the assistance @Marianne.
Yes , as per the output the new one is not came in the scan output.
But when i look at the cat /proc/scsi/scsi , it list as below from this how can i interrupt wherther the newly added is detected in OS or not .
Because i see below :
Host: scsi4 Channel: 00 Id: 06 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi4 Channel: 00 Id: 07 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi5 Channel: 00 Id: 00 Lun: 00
Vendor: STK Model: SL3000 Rev: 4.31
Type: Medium Changer ANSI SCSI revision: 05
Host: scsi6 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 01 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 02 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 03 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 04 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 05 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 06 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 07 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
06-05-2017 11:05 AM
Hi,
Take a look this part, from NetBackup™ Administrator's Guide Volume I, and let us know of this can help you.
Correlating tape drives and device files on UNIX hosts
If your tape drives do not support device serialization, you may have to determinewhich device file or SCSI address matches the physical drive. You also may have to do so if you add the tape drives manually.
Correlate device files to physical drives when you create the device files for each drive.
To correlate tape drives and device files on UNIX
1 Determine the physical location of each drive within the robotic library. The location usually is shown on the connectors to the drives or in the vendor’s documentation.
2 Physically connect the drives to SCSI adapters in the host.
3 Record the adapter and SCSI addresses to which you connected each drive.
4 Create device files for each drive by using the SCSI addresses of the drives and adapters. Add the device file by using the notes from a previous step to complete the correlation between device files and physical drive location.
5 Configure the robot in NetBackup and then add the drives. When you add the drives, verify that you assign the correct drive address (for example, robot drive number) to each device path.Optionally, use the appropriate NetBackup robotic test utility to verify the configuration. Information about the robotic test utilities is available.
See NetBackup Troubleshooting Guide: http://www.veritas.com/docs/DOC5332
To verify the device correlation on UNIX
1 Stop the NetBackup device daemon (ltid).
2 Start ltid, which starts the Automatic Volume Recognition daemon (avrd). Stop and restart ltid to ensure that the current device configuration is activated. If robotic control is not local to this host, also start the remote robotic controldaemon.
3 Use the robotic test utility to mount a tape on a drive.
4 Use the NetBackup Administration Console Device Monitor to verify that the tape was mounted on the correct robot drive.
UNIX device correlation example On UNIX only.
Assume a TLD robot includes three drives and the operating system includes the following device paths:
Drive 1 /dev/rmt/0cbn
Drive 2 /dev/rmt/1cbn
Drive 3 /dev/rmt/3cbn
Also assume that you requested that the tape be mounted on drive 1. If the device path for the drive is configured correctly, the NetBackup Administration Console Device Monitor shows that the tape is mounted on drive1.
If the Device Monitor shows that the tape is mounted on a different drive, the device path for that drive is not configured correctly. For example, if the Device Monitor shows that the tape is mounted on Drive 2, the device path for drive 1 is incorrect.
Replace the drive 1 device path (/dev/rmt/0cbn) with the correct device path (/dev/rmt/1cbn) for drive 2. You may need to use a temporary device path while you make these changes. You also know that the device path for drive 2 is incorrect. Possibly, the device paths were swapped during configuration.
Use the robotic test utility to unload and unmount the tape from drive 1. Repeat the test for each drive. If the path to the drive where the tape is mounted is not on the host with direct robotic control, you may have to unload the drive with a command from another host or from the drive’s front panel.
06-05-2017 11:17 AM
06-05-2017 11:32 AM
@Marianne - yes ,i could see from scan command output , it shows the correct serial number against the drive number.,
but when i look at the second part which shows details of each drive it still shows the old serail number.
06-05-2017 11:43 AM
Is there any scsi OS command to get the drive path of my new drive ?
06-05-2017 11:47 AM
06-05-2017 11:54 AM
Attached the scan output .
no i didnot rebooted the server , its linux not windows
06-05-2017 12:06 PM
Hi,
Did you already make scan using Device Configuration Wizard?
Regards,
Thiago
06-05-2017 12:49 PM
Hi - No i did not ran yet.
06-05-2017 02:15 PM
06-06-2017 05:22 AM
So, I went through the trouble of matching the robot drives with drives seen at OS level.
I do not see any "old" serial number at OS level.
The robot reports 16 drives. The OS sees 15 drives.
Drive 1 S/N : "10WT027929" Device Name : "/dev/nst11" S/N: "10WT027929"
Drive 2 S/N : "10WT029269" Device Name : "/dev/nst9" S/N: "10WT029269"
Drive 3 S/N : "10WT029128" Device Name : "/dev/nst14" S/N: "10WT029128"
Drive 4 S/N : "10WT041362" Device Name : "/dev/nst4" S/N: "10WT041362"
Drive 5 S/N : "10WT029127" Device Name : "/dev/nst2" S/N: "10WT029127"
Drive 6 S/N : "10WT029281" Device Name : "/dev/nst0" S/N: "10WT029281"
Drive 7 S/N : "10WT047315" Device Name : "/dev/nst14" S/N: "10WT047315"
Drive 8 S/N : "10WT029274" Device Name : "/dev/nst13" S/N: "10WT029274"
Drive 9 S/N : "91WT013900" Device Name : "/dev/nst15" S/N: "91WT013900"
Drive 10 S/N: "10WT027924" Device Name : "/dev/nst10" S/N: "10WT027924"
Drive 11 S/N: "90WT000616" Device Name : "/dev/nst12" S/N: "90WT000616"
Drive 12 S/N: "10WT029142" Device Name : "/dev/nst8" S/N: "10WT029142"
Drive 13 S/N: "10WT029137" Device Name : "/dev/nst6" S/N: "10WT029137"
Drive 14 S/N: "10WT037796"
Drive 15 S/N: "10WT029291" Device Name : "/dev/nst3" S/N: "10WT029291"
Drive 16 S/N: "10WT029270" Device Name : "/dev/nst7" S/N: "10WT029270"
The OS does not see this drive:
Drive 14 S/N: "10WT037796"
To list all drives seen at OS-level, use this command:
cat /proc/scsi/scsi
If the OS does not report the missing/replaced drive, you need to check zoning and ask OS admins to rescan at OS-level.
PS:
Hopefully you are sharing these drives between multiple media servers?
Way too many tape drives for a single media server...
06-06-2017 02:50 PM
Thank you for the assistance @Marianne.
Yes , as per the output the new one is not came in the scan output.
But when i look at the cat /proc/scsi/scsi , it list as below from this how can i interrupt wherther the newly added is detected in OS or not .
Because i see below :
Host: scsi4 Channel: 00 Id: 06 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi4 Channel: 00 Id: 07 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi5 Channel: 00 Id: 00 Lun: 00
Vendor: STK Model: SL3000 Rev: 4.31
Type: Medium Changer ANSI SCSI revision: 05
Host: scsi6 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 01 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 02 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 03 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 04 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 05 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 06 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi6 Channel: 00 Id: 07 Lun: 00
Vendor: IBM Model: ULTRIUM-TD6 Rev: E4J0
Type: Sequential-Access ANSI SCSI revision: 06
06-07-2017 04:39 AM
Hi
You shoudl run at first this:
cat /proc/scsi/scsi > pre_add
then to rescan on OS level you would need to run
echo "- - -" > /sys/class/scsi_host/hostX/scan
where X is the variable - as you can have present there host0, host1, so X=0, X=1 etc...
then rerun
cat /proc/scsi/scsi > post_add
finally
diff pre_add post_add
That should give you newly added devices...
06-07-2017 04:43 AM
I just noticed that in newer linux release there is such script
/usr/bin/rescan-scsi-bus.sh
which is doing bus rescan.... check it out if its installed on your OS.
06-13-2017 10:51 AM
Hi Marrianne - Drives are now detecting after the checking the ports.
06-13-2017 10:54 AM