Video Screencast Help

tape drives going down on and off

Created: 18 Sep 2012 • Updated: 19 Sep 2012 | 9 comments

We have 8 LTO4 tape drives.

Master/Media: HP-UX.

NBU: 6.5.6.

Can someone please help me identify if these are the bad tapes or the bad drives causing the problem? what log directories need to be created. arleady looked at the bptm log and the syslog.log, it doesn't seem like a hardware issue to me, but consistensy of one particular drive going down does makes it obvious that its faulty. No idea about zoning and stuff. HELP...

Comments 9 CommentsJump to latest comment

16ris10's picture

Here are a few command outputs. Please note I wrote 8 drives above. they're actually eff-ive only. i have doctored few serial numbers and everything for my job security..

 

as1# ./vmoprcmd -shmdrive
/dev/rmt/c85 K4 HP.ULTRIUM4-SCSI.001 HP~~~~~~Ultrium~4-SCSI~~H64S

/dev/rmt/c86 A6 HP.ULTRIUM4-SCSI.000 HP~~~~~~Ultrium~4-SCSI~~H64S

/dev/rmt/c89 82 HP.ULTRIUM4-SCSI.002 HP~~~~~~Ultrium~4-SCSI~~H64S

/dev/rmt/c82 B1 HP.ULTRIUM4-SCSI.003 HP~~~~~~Ultrium~4-SCSI~~H64S

/dev/rmt/c83 J0 HP.ULTRIUM4-SCSI.004 HP~~~~~~Ultrium~4-SCSI~~H64S

 

as1# ./vmoprcmd -autoconfig -t
TPAC60 HP      Ultrium 4-SCSI  H64S K4 -1 -1 -1 -1 /dev/rmt/c85 - -
TPAC60 HP      Ultrium 4-SCSI  H64S 82 -1 -1 -1 -1 /dev/rmt/c89 - -
TPAC60 HP      Ultrium 4-SCSI  H64S B1 -1 -1 -1 -1 /dev/rmt/c82 - -

 

as1# ./vmglob -listall -b
device
type    device name           serial number             host name
------------------------------------------------------------------------
robot   ROBOT0                77                as1
drive   HP.ULTRIUM4-SCSI.004  J0                as1
drive   HP.ULTRIUM4-SCSI.003  B1                as1
drive   HP.ULTRIUM4-SCSI.002  82                as1
drive   HP.ULTRIUM4-SCSI.000  A6                as1
drive   HP.ULTRIUM4-SCSI.001  K4                as1
drive   -                     16              -
drive   -                     90              -
drive   -                     09                -
drive   -                     91                -
as1#

 

as1# ./tpautoconf -report_disc
======================= Missing Device (Drive) =======================
 Drive Name = HP.ULTRIUM4-SCSI.000
 Drive Path = /dev/rmt/c86
 Inquiry = "HP      Ultrium 4-SCSI  H64S"
 Serial Number = A6
 TLD(0) definition Drive = 1
 Hosts configured for this device:
  Host = as1
======================= Missing Device (Drive) =======================
 Drive Name = HP.ULTRIUM4-SCSI.004
 Drive Path = /dev/rmt/c83
 Inquiry = "HP      Ultrium 4-SCSI  H64S"
 Serial Number = J0
 TLD(0) definition Drive = 4
 Hosts configured for this device:
  Host = as1

16ris10's picture

as1# pwd
/usr/openv/netbackup/logs/bptm

as1# cat log.091712 | grep "<16>"
10:47:18.610 [26283] <16> catch_signal: media manager suspended by interrupt (SIGINT)
10:47:18.747 [26168] <16> catch_signal: media manager suspended by interrupt (SIGINT)
10:47:19.084 [25336] <16> catch_signal: media manager suspended by interrupt (SIGINT)
10:47:19.459 [25070] <16> catch_signal: media manager suspended by interrupt (SIGINT)
10:47:19.854 [22758] <16> catch_signal: media manager suspended by interrupt (SIGINT)
10:47:20.228 [19575] <16> catch_signal: media manager suspended by interrupt (SIGINT)
11:22:54.708 [25557] <16> mount_open_media: error requesting media, TpErrno = Robot operation failed
11:39:25.567 [26626] <16> really_tpunmount: error unloading media, TpErrno = Robot operation failed
11:40:12.541 [25557] <16> mount_open_media: error requesting media, TpErrno = Request terminated because media is write protected
11:40:12.549 [25557] <16> write_backup: FREEZING media id XX0413, it is write protected and cannot be used for backups
11:41:34.354 [25557] <16> mount_open_media: error requesting media, TpErrno = Request terminated because media is write protected
11:41:34.362 [25557] <16> write_backup: FREEZING media id XX0626, it is write protected and cannot be used for backups
11:56:37.803 [28126] <16> really_tpunmount: error unloading media, TpErrno = Robot operation failed

as1# cat log.091712 | grep "<8>"
11:22:54.718 [25557] <8> write_backup: media id XX0413 load operation reported an error
12:17:33.874 [1395] <8> io_read_block: read error on media id 004106, drive index 1 reading header block, No space left on device

16ris10's picture

as1# pwd
/usr/adm/syslog

as1# cat syslog.log | grep ltid

Sep 17 09:22:09 as1 ltid[13000]: Operator/EMM server has UP'ed drive HP.ULTRIUM4-SCSI.001 (device 0)
Sep 17 10:33:38 as1 ltid[13000]: Operator/EMM server has UP'ed drive HP.ULTRIUM4-SCSI.002 (device 2)
Sep 17 10:43:55 as1 ltid[13000]: Sending shutdown to tldcd daemon...
Sep 17 10:44:13 as1 ltid[21742]: Received Type=2 message from TLD(0), RobotConnect continuing
Sep 17 10:48:51 as1 ltid[21742]: Sending shutdown to tldcd daemon...
Sep 17 10:49:58 as1 ltid[23419]: Received Type=2 message from TLD(0), RobotConnect continuing
Sep 17 11:14:49 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 17 11:22:54 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=2, Param2=0
Sep 17 11:23:00 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=2
Sep 17 11:39:27 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 17 11:39:28 as1 ltid[23419]: Operator/EMM server has DOWN'ed drive HP.ULTRIUM4-SCSI.002 (device 2)
Sep 17 11:40:12 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=1, Param2=0
Sep 17 11:40:13 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=2
Sep 17 11:40:17 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=1
Sep 17 11:40:49 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 17 11:41:33 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=3, Param2=0
Sep 17 11:41:38 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=3
Sep 17 11:42:07 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 17 11:42:09 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=1
Sep 17 11:43:03 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=4, Param2=0
Sep 17 11:43:05 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=2
Sep 17 11:43:17 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=1, Param2=1
Sep 17 11:44:01 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=2
Sep 17 11:45:09 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=1
Sep 17 12:00:34 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=1
Sep 17 12:01:30 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=3, Param2=1
Sep 17 12:05:18 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=3
Sep 17 12:11:48 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=0
Sep 17 12:15:29 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=1
Sep 17 12:15:30 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=2
Sep 17 12:15:31 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=3
Sep 17 12:16:27 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=3, Param2=1
Sep 17 12:16:41 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=2
Sep 17 12:16:54 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=1, Param2=3

... [same thing on repeat]

Sep 18 10:01:08 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=3, Param2=1
Sep 18 10:01:09 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=2
Sep 18 10:02:05 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=2
Sep 18 10:18:48 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=3
Sep 18 10:19:44 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=4, Param2=3
Sep 18 10:35:23 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=3
Sep 18 10:35:24 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=0
Sep 18 10:46:46 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=4
Sep 18 11:15:26 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=1
Sep 18 12:00:31 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 18 12:00:35 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=1
Sep 18 12:01:29 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=0
Sep 18 12:01:42 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=3, Param2=1
Sep 18 12:05:58 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=3
Sep 18 12:07:15 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=1
Sep 18 12:08:17 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=4, Param2=1
Sep 18 12:35:42 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=4
Sep 18 12:35:44 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=0
Sep 18 14:00:33 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 18 14:00:35 as1 ltid[23419]: Request for media ID 003865 is being rejected because mount requests are disabled (reason = robotic daemon going to DOWN state)
Sep 18 14:00:36 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=1, Param2=0
Sep 18 14:00:40 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=1
Sep 18 14:03:00 as1 ltid[23419]: Received Type=2 message from TLD(0), RobotConnect continuing
Sep 18 14:05:41 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 18 14:06:38 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=3, Param2=0
Sep 18 14:07:13 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=1
Sep 18 14:08:11 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=1
Sep 18 14:08:12 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=2
Sep 18 14:09:09 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=4, Param2=2
Sep 18 14:10:24 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=3
Sep 18 14:18:46 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 18 14:18:47 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=3
Sep 18 14:19:43 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=3, Param2=0
Sep 18 14:19:56 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=1, Param2=3
Sep 18 14:38:52 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=0
Sep 18 14:38:53 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=4
Sep 18 15:30:05 as1 ltid[23419]: Operator/EMM server has UP'ed drive HP.ULTRIUM4-SCSI.002 (device 2)
Sep 18 16:00:44 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=1
Sep 18 16:01:42 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=1
Sep 18 16:01:43 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=2
Sep 18 16:02:39 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=4, Param2=2
Sep 18 16:03:20 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=4
Sep 18 16:11:25 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=2, Param2=4
Sep 18 16:11:28 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=2
Sep 18 16:24:45 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=0
Sep 18 16:24:46 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=4
Sep 18 16:24:47 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=1
Sep 18 16:25:35 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=1
Sep 18 16:26:32 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=1, Param2=1
Sep 18 16:27:53 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=2
Sep 18 16:27:54 as1 ltid[23419]: Operator/EMM server has DOWN'ed drive HP.ULTRIUM4-SCSI.002 (device 2)
Sep 18 16:28:50 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=2
Sep 18 16:30:11 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=2
Sep 18 16:32:29 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=0
Sep 18 16:47:02 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=2
Sep 18 16:47:04 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=3
Sep 18 16:47:59 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=4, Param2=2
Sep 18 17:00:42 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 18 17:01:38 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=0
Sep 18 17:01:39 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=3
Sep 18 17:02:36 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=3, Param2=3
Sep 18 17:33:28 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=3
Sep 18 17:33:30 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=0
Sep 18 18:00:47 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 18 12:35:42 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=4
Sep 18 12:35:44 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=0
Sep 18 14:00:33 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 18 14:00:35 as1 ltid[23419]: Request for media ID 003865 is being rejected because mount requests are disabled (reason = robotic daemon going to DOWN state)
Sep 18 14:00:36 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=1, Param2=0
Sep 18 14:00:40 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=1
Sep 18 14:03:00 as1 ltid[23419]: Received Type=2 message from TLD(0), RobotConnect continuing
Sep 18 14:05:41 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 18 14:06:38 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=3, Param2=0
Sep 18 14:07:13 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=1
Sep 18 14:08:11 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=1
Sep 18 14:08:12 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=2
Sep 18 14:09:09 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=4, Param2=2
Sep 18 14:10:24 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=3
Sep 18 14:18:46 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 18 14:18:47 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=3
Sep 18 14:19:43 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=3, Param2=0
Sep 18 14:19:56 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=1, Param2=3
Sep 18 14:38:52 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=0
Sep 18 14:38:53 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=4
Sep 18 15:30:05 as1 ltid[23419]: Operator/EMM server has UP'ed drive HP.ULTRIUM4-SCSI.002 (device 2)
Sep 18 16:00:44 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=1
Sep 18 16:01:42 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=1
Sep 18 16:01:43 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=2
Sep 18 16:02:39 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=4, Param2=2
Sep 18 16:03:20 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=4
Sep 18 16:11:25 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=2, Param2=4
Sep 18 16:11:28 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=2
Sep 18 16:24:45 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=0
Sep 18 16:24:46 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=4
Sep 18 16:24:47 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=1
Sep 18 16:25:35 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=1
Sep 18 16:26:32 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=1, Param2=1
Sep 18 16:27:53 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=2
Sep 18 16:27:54 as1 ltid[23419]: Operator/EMM server has DOWN'ed drive HP.ULTRIUM4-SCSI.002 (device 2)
Sep 18 16:28:50 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=2
Sep 18 16:30:11 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=2
Sep 18 16:32:29 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=0
Sep 18 16:47:02 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=2
Sep 18 16:47:04 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=3
Sep 18 16:47:59 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=4, Param2=2
Sep 18 17:00:42 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 18 17:01:38 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=0
Sep 18 17:01:39 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=3
Sep 18 17:02:36 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=3, Param2=3
Sep 18 17:33:28 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=3
Sep 18 17:33:30 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=0
Sep 18 18:00:47 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0
Sep 18 18:01:44 as1 ltid[23419]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=0, Param2=0
Sep 18 18:05:43 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=3, Param2=0
Sep 18 18:07:22 as1 ltid[23419]: LTID - Sent ROBOTIC request, Type=1, Param2=0

 

Marianne's picture

We need to see the following in context (not just ltid greps)

Sep 18 14:00:35 as1 ltid[23419]: Request for media ID 003865 is being rejected because mount requests are disabled (reason = robotic daemon going to DOWN state)

Please copy entire syslog.log to syslog.txt and upload as file attachment.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

16ris10's picture

syslog:

Sep 18 20:00:06 as1 tldd[820]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:00:12 as1 tldd[1333]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:00:21 as1 tldd[820]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:00:27 as1 tldd[1333]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:12:48 as1 tldd[3373]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:12:56 as1 tldd[3422]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:13:01 as1 tldd[3438]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:13:46 as1 tldd[3554]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:17:55 as1 tldd[4360]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:19:02 as1 tldd[2630]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:21:14 as1 tldd[5057]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:27:04 as1 tldd[5861]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:27:14 as1 tldd[4693]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:35:33 as1 tldd[4693]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:46:59 as1 tldd[10757]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:47:03 as1 tldd[10770]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:47:14 as1 tldd[10757]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:47:19 as1 tldd[10770]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:47:44 as1 tldd[11166]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:51:27 as1 tldd[8805]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:57:02 as1 tldd[12497]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:57:03 as1 tldd[12513]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:57:03 as1 tldd[12514]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:57:04 as1 tldd[12522]: TLD(0) open failed in io_open, No such device or address
Sep 18 20:59:46 as1 tldd[8805]: TLD(0) open failed in io_open, No such device or address

16ris10's picture

I made someone technical see the logs, and he identified it as robot issue initally. here's the robot log.

19:54:04.581 [29332] <4> io_open:  Drive Path = /dev/rmt/c83
19:55:09.288 [29725] <4> io_open:  Drive Path = /dev/rmt/c86
20:00:05.884 [820] <4> io_open:  Drive Path = /dev/rmt/c86
20:00:06.400 [820] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:00:11.848 [1333] <4> io_open:  Drive Path = /dev/rmt/c83
20:00:12.360 [1333] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:00:21.925 [820] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:00:27.880 [1333] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:10:58.683 [2630] <4> io_open:  Drive Path = /dev/rmt/c89
20:12:48.332 [3373] <4> io_open:  Drive Path = /dev/rmt/c82
20:12:48.853 [3373] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:12:56.417 [3422] <4> io_open:  Drive Path = /dev/rmt/c83
20:12:56.932 [3422] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:13:01.472 [3438] <4> io_open:  Drive Path = /dev/rmt/c86
20:13:01.982 [3438] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:13:46.118 [3554] <4> io_open:  Drive Path = /dev/rmt/c85
20:13:46.633 [3554] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:17:01.691 [4126] <4> io_open:  Drive Path = /dev/rmt/c83
20:17:55.441 [4360] <4> io_open:  Drive Path = /dev/rmt/c83
20:17:55.953 [4360] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:19:02.373 [2630] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:19:11.315 [4693] <4> io_open:  Drive Path = /dev/rmt/c89
20:19:28.639 [4748] <4> io_open:  Drive Path = /dev/rmt/c86
20:21:13.822 [5057] <4> io_open:  Drive Path = /dev/rmt/c86
20:21:14.334 [5057] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:25:28.589 [5507] <4> io_open:  Drive Path = /dev/rmt/c86
20:27:03.896 [5861] <4> io_open:  Drive Path = /dev/rmt/c86
20:27:04.405 [5861] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:27:14.909 [4693] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:35:33.577 [4693] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:43:24.330 [8805] <4> io_open:  Drive Path = /dev/rmt/c89
20:43:30.484 [8825] <4> io_open:  Drive Path = /dev/rmt/c85
20:43:32.649 [8830] <4> io_open:  Drive Path = /dev/rmt/c82
20:46:58.966 [10757] <4> io_open:  Drive Path = /dev/rmt/c82
20:46:59.478 [10757] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:47:01.076 [10761] <4> io_open:  Drive Path = /dev/rmt/c83
20:47:02.176 [10765] <4> io_open:  Drive Path = /dev/rmt/c86
20:47:03.276 [10770] <4> io_open:  Drive Path = /dev/rmt/c85
20:47:03.788 [10770] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:47:14.998 [10757] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:47:19.308 [10770] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:47:43.772 [11166] <4> io_open:  Drive Path = /dev/rmt/c82
20:47:44.278 [11166] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:51:27.946 [8805] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:52:41.116 [11898] <4> io_open:  Drive Path = /dev/rmt/c82
20:57:02.275 [12497] <4> io_open:  Drive Path = /dev/rmt/c86
20:57:02.790 [12497] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:57:03.274 [12513] <4> io_open:  Drive Path = /dev/rmt/c85
20:57:03.277 [12514] <4> io_open:  Drive Path = /dev/rmt/c83
20:57:03.780 [12513] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:57:03.790 [12514] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:57:04.298 [12522] <4> io_open:  Drive Path = /dev/rmt/c82
20:57:04.810 [12522] <5> io_open: TLD(0) open failed in io_open, No such device or address
20:59:46.695 [8805] <5> io_open: TLD(0) open failed in io_open, No such device or address

16ris10's picture

after reviewing both of these logs, he was of conclusions that OS is not able to see the devices on and off. so may be this is a firmware, san sqwitch, hba, cable issue. now the problem is, how to check these things?

Marianne's picture

Sorry, not a NBU problem.
Get your SAN management/support team to investigate.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links