Solved: OS AND SCAN LINUX NBU 7.1

Andy2345 · ‎03-14-2013

Hi ALL,

Drives and library are visible in cat /proc/scsi/scsi command(OS LEVEL).

Drive is visible but Library is not visible in SCAN command o/p.

Please suggest.

@linux001bin]$ cat /proc/scsi/scsi

Attached devices:

Host: scsi0 Channel: 00 Id: 06 Lun: 00

Vendor: CERTANCE Model: ULTRIUM 2 Rev: 20134

Type: Sequential-Access ANSI SCSI revision: 03

Host: scsi0 Channel: 00 Id: 06 Lun: 01

Vendor: QUANTUM Model: UHDL Rev: 0061

Type: Medium Changer ANSI SCSI revision: 02

@linux001bin]$ sudo ./scan

************************************************************

*********************** SDT_TAPE ************************

*********************** SDT_CHANGER ************************

************************************************************

------------------------------------------------------------

Device Name : "/dev/nst0"

Passthru Name: "/dev/sg0"

Volume Header: ""

Port: -1; Bus: -1; Target: -1; LUN: -1

Inquiry : "CERTANCEULTRIUM 2 2013"

Vendor ID : "CERTANCE"

Product ID : "ULTRIUM 2 "

Product Rev: "2013"

Serial Number: "ML1234L"

WWN : ""

WWN Id Type : 0

Device Identifier: "CERTANCEULTRIUM 2 ML1234"

Device Type : SDT_TAPE

NetBackup Drive Type: 10

Removable : Yes

Device Supports: SCSI-3

Flags : 0x0

Reason: 0x0

var/adm/messages:

Mar 14 17:15:11 linux001last message repeated 3 times

Mar 14 17:16:11 linux001last message repeated 4 times

Mar 14 17:16:18 linux001tldcd[20213]: TLD(0) [20213] robotic path MISSING_PATH:CJ8BC20136 does not exist

Mar 14 17:16:18 linux001tldd[20209]: TLD(0) unavailable: initialization failed: Unable to open robotic path

Mar 14 17:16:26 linux001avrd[20210]: MTIOCGET failed on CERTANCE.ULTRIUM2.000 (device 0, /dev/nst0) ioctl failed, Input/output error

Mar 14 17:17:11 linux001last message repeated 3 times

Mar 14 17:18:11 linux001last message repeated 4 times

Mar 14 17:18:20 linux001tldcd[20213]: TLD(0) [20213] robotic path MISSING_PATH:CJ8BC20136 does not exist

Mar 14 17:18:20 linux001tldd[20209]: TLD(0) unavailable: initialization failed: Unable to open robotic path

Mar 14 17:18:26 linux001avrd[20210]: MTIOCGET failed on CERTANCE.ULTRIUM2.000 (device 0, /dev/nst0) ioctl failed, Input/output error

Mar 14 17:18:37 linux001SQLAnywhere(nb_linux001): Starting checkpoint of "NBDB" (NBDB.db) at Thu Mar 14 2013 17:18

Mar 14 17:18:37 linux001SQLAnywhere(nb_linux001): Finished checkpoint of "NBDB" (NBDB.db) at Thu Mar 14 2013 17:18

Mar 14 17:18:41 linux001avrd[20210]: MTIOCGET failed on CERTANCE.ULTRIUM2.000 (device 0, /dev/nst0) ioctl failed, Input/output error

Mar 14 17:19:26 linux001last message repeated 3 times

Mar 14 17:20:11 linux001last message repeated 3 times

Mar 14 17:20:14 linux001SQLAnywhere(nb_linux001): Starting checkpoint of "NBAZDB" (NBAZDB.db) at Thu Mar 14 2013 17:20

Mar 14 17:20:14 linux001SQLAnywhere(nb_linux001): Finished checkpoint of "NBAZDB" (NBAZDB.db) at Thu Mar 14 2013 17:20

Mar 14 17:20:22 linux001tldcd[20213]: TLD(0) [20213] robotic path MISSING_PATH:CJ8BC20136 does not exist

Mar 14 17:20:22 linux001tldd[20209]: TLD(0) unavailable: initialization failed: Unable to open robotic path

Mar 14 17:20:26 linux001avrd[20210]: MTIOCGET failed on CERTANCE.ULTRIUM2.000 (device 0, /dev/nst0) ioctl failed, Input/output error

Mar 14 17:21:11 linux001last message repeated 3 times

Mar 14 17:22:11 linux001last message repeated 4 times

Mar 14 17:22:24 linux001tldcd[20213]: TLD(0) [20213] robotic path MISSING_PATH:CJ8BC20136 does not exist

Mar 14 17:22:24 linux001tldd[20209]: TLD(0) unavailable: initialization failed: Unable to open robotic path

Mar 14 17:22:26 linux001avrd[20210]: MTIOCGET failed on CERTANCE.ULTRIUM2.000 (device 0, /dev/nst0) ioctl failed, Input/output error

Mar 14 17:23:11 linux001last message repeated 3 times

Mar 14 17:24:11 linux001last message repeated 4 times

Mar 14 17:24:26 linux001tldcd[20213]: TLD(0) [20213] robotic path MISSING_PATH:CJ8BC20136 does not exist

Mar 14 17:24:26 linux001tldd[20209]: TLD(0) unavailable: initialization failed: Unable to open robotic path

Mar 14 17:24:26 linux001avrd[20210]: MTIOCGET failed on CERTANCE.ULTRIUM2.000 (device 0, /dev/nst0) ioctl failed, Input/output error

Mar 14 17:25:11 linux001last message repeated 3 times

Mar 14 17:26:12 linux001last message repeated 4 times

Mar 14 17:26:27 linux001avrd[20210]: MTIOCGET failed on CERTANCE.ULTRIUM2.000 (device 0, /dev/nst0) ioctl failed, Input/output error

Mar 14 17:26:28 linux001tldcd[20213]: TLD(0) [20213] robotic path MISSING_PATH:CJ8BC20136 does not exist

Mar 14 17:26:28 linux001tldd[20209]: TLD(0) unavailable: initialization failed: Unable to open robotic path

Mar 14 17:26:42 linux001avrd[20210]: MTIOCGET failed on CERTANCE.ULTRIUM2.000 (device 0, /dev/nst0) ioctl failed, Input/output error

Mar 14 17:27:27 linux001last message repeated 3 times

Mar 14 17:28:27 linux001last message repeated 4 times

Mar 14 17:28:30 linux001tldcd[20213]: TLD(0) [20213] robotic path MISSING_PATH:CJ8BC20136 does not exist

Mar 14 17:28:30 linux001tldd[20209]: TLD(0) unavailable: initialization failed: Unable to open robotic path

Mar 14 17:28:42 linux001avrd[20210]: MTIOCGET failed on CERTANCE.ULTRIUM2.000 (device 0, /dev/nst0) ioctl failed, Input/output error

Mar 14 17:29:27 linux001last message repeated 3 times

Mar 14 17:30:27 linux001last message repeated 4 times

Mar 14 17:30:32 linux001tldcd[20213]: TLD(0) [20213] robotic path MISSING_PATH:CJ8BC20136 does not exist

Mar 14 17:30:32 linux001tldd[20209]: TLD(0) unavailable: initialization failed: Unable to open robotic path

Mar 14 17:30:42 linux001avrd[20210]: MTIOCGET failed on CERTANCE.ULTRIUM2.000 (device 0, /dev/nst0) ioctl failed, Input/output error

Mar 14 17:31:27 linux001last message repeated 3 times

Mar 14 17:32:27 linux001last message repeated 4 times

Mar 14 17:32:34 linux001tldcd[20213]: TLD(0) [20213] robotic path MISSING_PATH:CJ8BC20136 does not exist

Mar 14 17:32:34 linux001tldd[20209]: TLD(0) unavailable: initialization failed: Unable to open robotic path

Mar 14 17:32:42 linux001avrd[20210]: MTIOCGET failed on CERTANCE.ULTRIUM2.000 (device 0, /dev/nst0) ioctl failed, Input/output error

Mar 14 19:31:10 linux001last message repeated 4 times

Mar 14 19:31:15 linux001tldcd[20760]: TLD(0) [20760] robotic path MISSING_PATH:CJ8BC20136 does not exist

Mar 14 19:31:15 linux001tldd[20756]: TLD(0) unavailable: initialization failed: Unable to open robotic path

Mar 14 19:31:25 linux001avrd[20757]: MTIOCGET failed on CERTANCE.ULTRIUM2.000 (device 0, /dev/nst0) ioctl failed, Input/output error

mph999 · ‎03-15-2013

scan does not discover anythng ever ...

It sends a scsi command to the devices seen by the os, if there is a device missing (in scan output) that can be seen by the OS, it means the device (library in this case) did not respond to the scsi command, or if it did, the result never made it back to 'scan'.

scan is not a netbackup command, and it does not run any netbackup commands, and there is nothing that can be down in netbackup to fix this.

You are on linux, that is good because you can run this :

/usr/openv/volmgr/bin/scsi_command -d <os path to library>

This should provide the output of the scsi 'inquiry string' - I'm going to bet this fails as well.

So what will be at fault, most obvious guess would be either a hardware fault or firmware issue on the library.

If not this, then next I would suspect the HBA, again either fault or firmware issue - and yes, I have seen HBAs cause faults such as this.

The one thing it cannot be, is NetBackup.

Martin

View solution in original post

Marianne · ‎03-14-2013

I'm sure you understand that this is not a NetBackup issue?

You need to work with server owner and SAN administrator - check physical connections, check robot console for errors, check switch logs... everything except NBU.

NBU will be fine once OS can see all devices.

Handy NetBackup Links

Andy2345 · ‎03-14-2013

I just wanna know If OS can detect the drives and library.(proc/scsi/scsi) then why not scan?

Scan discovers what OS can see.

Anshu_Pathak · ‎03-14-2013

Scan discovers what OS can see. --- Not always

NetBackup device configuration starts with "scan" process and if devices are not getting listed in scan there is nothing that you can do from NetBackup side.

One reason for device not getting detected in "scan" is --- an existing scsi reserve on the device.

Standard steps that you can try in this situations are

1. Reboot Library

2. Reboot Media server

3. Check SCSI / Fiber cables

4. Check the SCSI / HBA card

5. Reseat SCSI / HBA card

6. Reconfigure drivers

7. Contact hardware vendor

Andy2345 · ‎03-15-2013

Thanks Anshu.

But if OS is detecting then why not NBU is?

Will_Restore · ‎03-15-2013

unplug the library

cat /proc/scsi/scsi

is Quantum still listed?

Andy2345 · ‎03-15-2013

NO.

mph999 · ‎03-15-2013

scan does not discover anythng ever ...

It sends a scsi command to the devices seen by the os, if there is a device missing (in scan output) that can be seen by the OS, it means the device (library in this case) did not respond to the scsi command, or if it did, the result never made it back to 'scan'.

scan is not a netbackup command, and it does not run any netbackup commands, and there is nothing that can be down in netbackup to fix this.

You are on linux, that is good because you can run this :

/usr/openv/volmgr/bin/scsi_command -d <os path to library>

This should provide the output of the scsi 'inquiry string' - I'm going to bet this fails as well.

So what will be at fault, most obvious guess would be either a hardware fault or firmware issue on the library.

If not this, then next I would suspect the HBA, again either fault or firmware issue - and yes, I have seen HBAs cause faults such as this.

The one thing it cannot be, is NetBackup.

Martin

mph999 · ‎03-15-2013

From here :

sg3_utils-1.35-1.src.rpm

I downloaded the sg3_utils-1.35-1.src.rpm package.

Copied this to my Linux server and created and placed in the directory

mkdir -p /usr/src/redhat/SOURCES

Then I installed it ...

rpm -i sg3_utils-1.35-1.src.rpm

This installs many sg* commands, which can be used to run the same sort of commands as scan, or in other words, think of these as a totally non symantec version of scan ...

There are many example shown in the page :

http://sg.danny.cz/sg/sg3_utils.html#mozTocId479511

More details here

http://linux.die.net/man/8/sg3_utils

sg_inq looks good ...

Try sq_inq -d <device file to library>

Does this give any output ?

VOX

OS AND SCAN LINUX NBU 7.1