cancel
Showing results for 
Search instead for 
Did you mean: 

Missing Drive Path

A_M_Ash_
Level 6

Hi,

 

i have media server linuxback  connected to STK sl3000 tape library on two drives

but i cannont see any drive on the server

Symantic Product Name: Symantec Netbackup

Product Version: 7.0.1

Operating System: HP-UX 11iv3

- when i do configure storage device scan i cannot see any drives assigned to linux server

- when i restart NetBackup service on all media server it cannot also see any drives

 

any help ??

1 ACCEPTED SOLUTION

Accepted Solutions

A_M_Ash_
Level 6

Hi All,

The last problem with linuxback media server is solved as :

we found that the problem was in the fiber card in the blade connected to the tape library ,We replaced it with a new one and every thing is OK now and do new zoning , i initiated a backup on the that media server and finished successfully

View solution in original post

23 REPLIES 23

A_M_Ash_
Level 6

hi,

how to list device path on linux server

mph999
Level 6
Employee Accredited

Can the operating system see the drives.

cat /proc/scsi/scsi

What does the output of /usr/openv/volmgr/bin/scan show.

Martin

Marianne
Level 6
Partner    VIP    Accredited Certified

You may want to read through the Linux chapter in NBU 7.0 Device Configuration Guide .

See these (and other)  topics:

 

■ Before you begin on Linux
■ About the required Linux SCSI drivers
■ Verifying the Linux drivers
■ Configuring robot and drive control for the Linux 2.6 kernel
■ Verifying the device configuration
......
.....

A_M_Ash_
Level 6

hi,

 

1- i have checked zoning of drives 12 ,13 with server linuxback and it is correctly zoned !

2- i zone other two drives 14 , 16 to the same server but cannot see them ..  it is linux server ,,so how to scan or see them?

 

3- this is the output of the commands you ask about  :

 

[root@linuxback ~]# tpconfig -l
Device Robot Drive       Robot                    Drive       Device                           Second
Type     Num Index  Type DrNum Status  Comment    Name        Path                             Device Path
robot      3    -    TLD    -       -  -          -           m4
  drive    -    0  hcart   12    DOWN  -          sl3k_m4_12  MISSING_PATH:2:0:2:0:HU184642YF
  drive    -    1  hcart   13    DOWN  -          sl3k_m4_13  MISSING_PATH:2:0:1:0:HU1848495R

 

 

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

 

[root@linuxback ~]# cd /usr/openv/volmgr/bin/
[root@linuxback bin]# scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************
[root@linuxback bin]#

 

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

 

[root@linuxback bin]# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: STEC    M8PSB1   Rev: 0405
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: ATA      Model: STEC    M8PSB1   Rev: 0405
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi0 Channel: 01 Id: 01 Lun: 00
  Vendor: LSILOGIC Model: Logical Volume   Rev: 3000
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 00 Lun: 01
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 00 Lun: 05
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 00 Lun: 06
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 00 Lun: 07
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 00 Lun: 08
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 00 Lun: 09
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 00 Lun: 10
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 00 Lun: 11
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 00 Lun: 12
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 01 Lun: 01
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 01 Lun: 05
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 01 Lun: 06
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 01 Lun: 07
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 01 Lun: 08
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 01 Lun: 09
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 01 Lun: 10
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 01 Lun: 11
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 01 Lun: 12
  Vendor: EMC      Model: SYMMETRIX        Rev: 5874
  Type:   Direct-Access                    ANSI SCSI revision: 04
[root@linuxback bin]#
[root@linuxback bin]#

 

 

-----

 

any help is  appreciated ..   thnx

 

Marianne
Level 6
Partner    VIP    Accredited Certified

Please use the steps listed in Device Config Guide to troubleshoot at OS level.

Nothing can be done from NBU side.

 

**** EDIT ****

You may also want to check HBA utilities (e.g SanSurfer for QLogic HBA).

A_M_Ash_
Level 6

hi,

 

i have checked the zoning of media servers ..  and working with the operating system level  ,, but i want to know

how to verify in the var logs / system log messages if we have any errors related to robot.  ??

Marianne
Level 6
Partner    VIP    Accredited Certified

This is no longer related to your opening post, right?

Your output of 'cat /proc/scsi/scsi' shows that OS can NOT see the tape drives. 

/var/log/messages file might help to find out when and why devices disappeared. There may be errors in in messages file related to hba going offline and/or other device-related errors.

To ensure that NBU media manager also logs actions/errors to messages file, add VERBOSE entry to /usr/openv/volmgr/vm.conf and restart NBU on media server.
You will now see that output of 'bpps -x' on media server shows Media Manager processes running in verbose mode (-v).

 

mph999
Level 6
Employee Accredited

I agree with Marianne, the OS is not seeing the drives, else they would appear in proc/scsi/scsi

Try a reboot ...

Martin

A_M_Ash_
Level 6

hi,

can you please give me commands indetails that help to find out when and why devices disappeared ?

thanks

A_M_Ash_
Level 6

hi,

i have do  the steps listed in Device Config Guide to troubleshoot at OS level

and restart NB service on servers and reboot the linuxback server but still cannot see the devices

Marianne
Level 6
Partner    VIP    Accredited Certified

Have you tried to check messages file? Depending on how long ago this happened, it may be in a backup file  - messages file is copied to a backup file once a week - example on our lab server:

 

-rw------- 1 root root   37139 Aug  6 05:04 messages
-rw------- 1 root root  347614 Aug  5 03:44 messages.1
-rw------- 1 root root 3954993 Jul 29 03:43 messages.2
-rw------- 1 root root 2465730 Jul 22 04:02 messages.3
-rw------- 1 root root 1054056 Jul 15 03:45 messages.4
 
If you do not know how to read these files or what to look for, you need assistance from your Linux support team.
 
I have also suggested that you use HBA tools to verify devices are seen by HBA. 
Do you know what make/model HBA is used for tape connection?
Your EMC disk and tape drives should be on different HBAs.
 
 

A_M_Ash_
Level 6

hi,

 

related to our case i want command to scan the devices connected or zoned to the :

 

1- linux server

 

2-aix server

mph999
Level 6
Employee Accredited

1.  Try lspci then modprobe 

2. Aix

 

lsdev

look for rmt's

 

 

A_M_Ash_
Level 6

Hi All,

 

for aixback connected to data domain   we solved the case as follow :

1- check zoning .

2-run cfgmgr command on aixback server to scan all connected devices .

3-restart NetBackup Service on media server .

4-rescan   : using configure storage devices 

5-the backup is initiated successfully  now it is running.

 

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

 

for linuxback  connected to  STK SL3000 tape library  we still have aproblem :

 

1- i need a command such as cfgmgr  to re scan devices connected to server linuxback " linux redhat "

 

thanks

Marianne
Level 6
Partner    VIP    Accredited Certified

If a reboot does not work, I cannot see that any command will fix it.

When system starts up, the OS will automatically scan for new devices.

Check zoning again..........

mph999
Level 6
Employee Accredited

"When system starts up, the OS will automatically scan for new devices"

Correct - if the zoning really is correct, you'll have to get RH to have a look.

M

A_M_Ash_
Level 6

hi,

but i think linux redhat is special case  ..  may be server needs manually configuration plus reboot i don not know .. what is your recommendation ?

Marianne
Level 6
Partner    VIP    Accredited Certified

We have RHEL in our office. We did not need to do anything 'special' to see the devices.
The hardware team zoned the devices, we rebooted and the robot and tape drive were visible at OS level.

mph999
Level 6
Employee Accredited

Recommendation is to x2 check the zoning and if it is correct, speak to RedHat.

Martin