Forum Discussion

Imran_Dogar's avatar
10 years ago

io_ioctl: ioctl (MTWEOF) failed on media id DT00xx, drive index 0, I/O error (bptm.c.9796)

Hi...

I m new to this forum... 

We are running Netbackup Veritas 7.6 on solaris 10 sparc... While i initiate a backup it takes a lot of time in mounting of tape into tape drive and i finally get a media error (84) msg.... We are using SL 500 Storagetek tape lib.... I hav searched alot on net but unable to figureout anything sofar... Output from bptm is as uder.....

 

10:25:56.783 [1268] <4> create_tpreq_file: symlink to path /dev/rmt/1cbn
10:25:56.794 [1268] <2> manage_drive_before_load: SCSI RESERVE
10:25:56.797 [1268] <2> manage_drive_before_load: report_attr, fl1 0x00000001, fl2 0x00000000
10:25:56.797 [1268] <4> expandpath: /usr/openv/netbackup/db/media/tpreq/drive_HP.ULTRIUM4-SCSI.000
10:25:57.342 [1268] <2> tapelib: wait_for_ltid, Mount, timeout 0
10:29:57.773 [1268] <2> io_open: SCSI RESERVE
1
10:29:57.979 [1268] <2> io_open: file /usr/openv/netbackup/db/media/tpreq/drive_HP.ULTRIUM4-SCSI.000 successfully opened (mode 2)
10:29:57.979 [1268] <2> write_backup: media id DT0094 mounted on drive index 0, drivepath /dev/rmt/1cbn, drivename HP.ULTRIUM4-SCSI.000, copy 1
10:29:57.979 [1268] <2> set_job_details: Tfile (11): LOG 1436333397 4 bptm 1268 media id DT0094 mounted on drive index 0, drivepath /dev/rmt/1cbn, drivename HP.ULTRIUM4-SCSI.000, copy 1

10:29:57.979 [1268] <2> send_job_file: job ID 11, ftype = 3 msg len = 133, msg = LOG 1436333397 4 bptm 1268 media id DT0094 mounted on drive index 0, drivepath /dev/rmt/1cbn, drivename HP.ULTRIUM4-SCSI.000, copy 1

10:29:57.979 [1268] <4> report_throughput: VBRT 1 1268 1 1 HP.ULTRIUM4-SCSI.000 DT0094 0 1 0 0  0 (bptm.c.18468)
10:29:57.979 [1268] <2> io_read_media_header: drive index 0, reading media header, buflen = 65536, buff = 0x100bf4f10, copy 1
10:29:57.979 [1268] <2> io_ioctl: command (5)MTREW 1 0x0 from (bptm.c.8311) on drive index 0

10:29:57.999 [1268] <2> io_read_media_header: read error on media id DT0094, drive index 0, reading header block, I/O error

10:29:57.999 [1268] <2> io_write_media_header: drive index 0, writing media header
10:29:58.000 [1268] <2> io_close: closing /usr/openv/netbackup/db/media/tpreq/drive_HP.ULTRIUM4-SCSI.000, from bptm.c.9727
10:29:58.000 [1268] <2> io_open: SCSI RESERVE
10:29:58.010 [1268] <2> io_open: file /usr/openv/netbackup/db/media/tpreq/drive_HP.ULTRIUM4-SCSI.000 successfully opened (mode 2)
10:29:58.010 [1268] <2> io_ioctl: command (5)MTREW 1 0x0 from (bptm.c.9732) on drive index 0
10:29:59.068 [1268] <2> io_ioctl: command (0)MTWEOF 1 0x0 from (bptm.c.9796) on drive index 0
10:31:46.606 [1268] <2> set_job_details: Tfile (11): LOG 1436333506 16 bptm 1268 ioctl (MTWEOF) failed on media id DT0094, drive index 0, I/O error (bptm.c.9796)

10:31:46.606 [1268] <2> send_job_file: job ID 11, ftype = 3 msg len = 109, msg = LOG 1436333506 16 bptm 1268 ioctl (MTWEOF) failed on media id DT0094, drive index 0, I/O error (bptm.c.9796)

10:31:46.607 [1268] <16> io_ioctl: ioctl (MTWEOF) failed on media id DT0094, drive index 0, I/O error (bptm.c.9796)

10:31:46.607 [1268] <2> send_MDS_msg: DEVICE_STATUS 1 9 fenbk31 DT0094 4000001 HP.ULTRIUM4-SCSI.000 2000011 WRITE_ERROR 0 0
10:31:46.711 [1268] <2> log_media_error: successfully wrote to error file - 07/08/15 10:31:46 DT0094 0 WRITE_ERROR HP.ULTRIUM4-SCSI.000
10:31:46.711 [1268] <2> check_error_history: just tpunmount: called from bptm line 22614, EXIT_Status = 84
10:31:46.711 [1268] <2> io_close: closing /usr/openv/netbackup/db/media/tpreq/drive_HP.ULTRIUM4-SCSI.000, from bptm.c.16619
10:31:46.711 [1268] <2> drivename_write: Called with mode 1
10:31:46.711 [1268] <2> drivename_unlock: unlocked
10:31:46.711 [1268] <2> drivename_close: Called for file HP.ULTRIUM4-SCSI.000
10:31:46.711 [1268] <2> tpunmount: NOP: MEDIA_DONE 0 11 0 DT0094 4000001 0 {CF5EF6AC-2531-11E5-BA67-00144FB7D13A}
10:31:46.711 [1268] <2> bptm: EXITING with status 84 <----------
10:31:46.711 [1268] <2> set_job_details: Tfile (11): LOG 1436333506 4 bptm 1268 EXITING with status 84 <----------

 

 

 

If anyone can pl help....

 

  • Some tape libraries can require an annual service, and the term for this is PM, or 'Preventative Maintenance' - whereby the mechanical gearing of a library robot arm is cleaned and re-greased, and then re-aligned.  An engineer performing PM shoudl also inspect for worn gears, worn motors, loose drive belts, replace air-filters, and clean any light residual traces of grease, grime and dust from within the inside of the tape library, and clean the bar-code laser and 'eye/lens'.

    Some libraries can be rebooted so that, as part of their reboot process, they use special (hidden from NetBackup) bar-coded points within the library chassis to re-align themselves internally, so that the robot arm lines up correctly with the fromt of teh tape drives - this process is sometimes referred to as 'Library learn' sequence.

    So more modern libraries are more advanced and no longer require any annual PM, as they are self lubricating, and self adjusting.

    .

    Maybe it's been a while since your library was serviced, or had PM.

24 Replies