The semaphore timeout period has expired. (121)
Hi All,
Currently using NetBackup 7.6.0.4, when i try to do a duplicate job the error (86) in activity monitor appear.I already reboot media server and Tape Library, but still error.The detail logs below:
9/3/2015 12:01:59 PM - Info bpbrm(pid=6464) FFOSIEMMA1 is the host to backup data from
9/3/2015 12:01:59 PM - Info bpbrm(pid=6464) reading file list for client
9/3/2015 12:02:01 PM - Info bpbrm(pid=6464) starting bpbkar32 on client
9/3/2015 12:02:02 PM - Info bpbkar32(pid=5184) Backup started
9/3/2015 12:02:02 PM - Info bpbkar32(pid=5184) change time comparison:<disabled>
9/3/2015 12:02:02 PM - Info bpbkar32(pid=5184) archive bit processing:<enabled>
9/3/2015 12:02:02 PM - Info bpbkar32(pid=5184) not using change journal data for <E:\AFKLGR01>: not enabled
9/3/2015 12:02:02 PM - Info bpbkar32(pid=5184) not using change journal data for <E:\AFKLGR02>: not enabled
9/3/2015 12:02:02 PM - Info bptm(pid=4820) start
9/3/2015 12:02:07 PM - Info bptm(pid=4820) using 65536 data buffer size
9/3/2015 12:02:07 PM - Info bptm(pid=4820) setting receive network buffer to 263168 bytes
9/3/2015 12:02:07 PM - Info bptm(pid=4820) using 30 data buffers
9/3/2015 12:02:11 PM - Info bptm(pid=4820) start backup
9/3/2015 12:02:11 PM - Info bptm(pid=4820) backup child process is pid 1864.4624
9/3/2015 12:02:11 PM - Info bptm(pid=4820) Waiting for mount of media id A239L6 (copy 1) on server majsmrma2.
9/3/2015 12:02:11 PM - Info bptm(pid=1864) start
9/3/2015 12:02:53 PM - Info nbjm(pid=14080) starting backup job (jobid=372464) for client FFOSIEMMA1, policy ucust-logfile-ffosiemma1-arcsight, schedule fullbackup
9/3/2015 12:02:53 PM - Info nbjm(pid=14080) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=372464, request id:{14C7AFA5-72D6-484B-8030-A900DC463906})
9/3/2015 12:02:53 PM - requesting resource majsmrma2-hcart2-robot-tld-1
9/3/2015 12:02:53 PM - requesting resource majsmrfa1.NBU_CLIENT.MAXJOBS.FFOSIEMMA1
9/3/2015 12:02:53 PM - requesting resource majsmrfa1.NBU_POLICY.MAXJOBS.ucust-logfile-ffosiemma1-arcsight
9/3/2015 12:02:53 PM - granted resource majsmrfa1.NBU_CLIENT.MAXJOBS.FFOSIEMMA1
9/3/2015 12:02:53 PM - granted resource majsmrfa1.NBU_POLICY.MAXJOBS.ucust-logfile-ffosiemma1-arcsight
9/3/2015 12:02:53 PM - granted resource A239L6
9/3/2015 12:02:53 PM - granted resource HP.ULTRIUM6-SCSI.000
9/3/2015 12:02:53 PM - granted resource majsmrma2-hcart2-robot-tld-1
9/3/2015 12:02:53 PM - started
9/3/2015 12:02:54 PM - estimated 2575203297 Kbytes needed
9/3/2015 12:02:54 PM - Info nbjm(pid=14080) started backup (backupid=FFOSIEMMA1_1441252973) job for client FFOSIEMMA1, policy ucust-logfile-ffosiemma1-arcsight, schedule fullbackup on storage unit majsmrma2-hcart2-robot-tld-1
9/3/2015 12:02:59 PM - started process bpbrm (6464)
9/3/2015 12:03:05 PM - connecting
9/3/2015 12:03:06 PM - connected; connect time: 0:00:01
9/3/2015 12:03:13 PM - Info bptm(pid=4820) media id A239L6 mounted on drive index 0, drivepath {2,0,0,0}, drivename HP.ULTRIUM6-SCSI.000, copy 1
9/3/2015 12:03:16 PM - mounting A239L6
9/3/2015 12:04:00 PM - Warning bptm(pid=4820) cannot locate on drive index 0, The semaphore timeout period has expired.
9/3/2015 12:04:19 PM - mounted; mount time: 0:01:03
9/3/2015 12:04:28 PM - positioning A239L6 to file 2
9/3/2015 12:04:39 PM - Error bptm(pid=4820) ioctl (MTREW) failed on media id A239L6, drive index 0, The semaphore timeout period has expired. (121) (bptm.c.7146)
9/3/2015 12:05:25 PM - Error bptm(pid=4820) ioctl (MTFSF) failed on media id A239L6, drive index 0, The semaphore timeout period has expired. (121) (bptm.c.7358)
9/3/2015 12:05:26 PM - Info bptm(pid=4820) EXITING with status 86 <----------
9/3/2015 12:05:28 PM - Error bpbrm(pid=6464) cannot send mail to
9/3/2015 12:05:29 PM - Info bpbkar32(pid=5184) done. status: 86: media position error
9/3/2015 12:05:42 PM - Info bpbrm(pid=4928) Starting delete snapshot processing
9/3/2015 12:06:34 PM - end writing
media position error(86)
Hi,
It could be either the media or the drive. You can show that by testing, if all media you put into that drives gives and error then there is clearly something wrong with the drive (or maybe the connection to the drive). If you put the different media in and it works then its probably just a media that is not working, and you can throw it away (and hope there is no data on it).
Maybe your hw provider has some utlility to test the drive in more detail, having a green light doesn't mean everything is working.
