Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

GFS job with error E3719, E3712

Status
Not open for further replies.

pakilaci

IS-IT--Management
Jan 21, 2005
57
HU
MULTIPLEXING [JOB 2]
SUBJOB 2
E3719 Unable to write to media. (MEDIA=M-GFSJOB1-SAT- 2/19/05 [S/N: 123ABCD0], EC=Hardware Error)
E3712 Unable to close session. (EC=Hardware Error)

SUBJOB 1,3,5
E3719 Unable to write to media. (MEDIA=M-GFSJOB1-SAT- 2/19/05 [S/N: 123ABCD0] EC=DEVICE ALREADY OPEN

Could it be that SubJob 2 filled the media and it was unable to continue on a new tape? If I use Rotation Scheme, where to set Additional Backup Media options?Help me please, why this error occured!
(Win2k SP4, BAB 11.1 SP1, IBM 3583 Library)
 
The Additional Backup Media options are not used for a rotation job. Rotation and GFS jobs follow the configuratin of the Media Pool.

Get the time stamp the errors happened and then check the tape log at that time for the errors there.
 
A lot of "GetMuxLock:: Timeout Occurred." messages in Tape log.
 
02/26 18:11:14 [0160] DRV:6 WriteShots:4
02/26 18:16:56 [0a90] GetMuxLock:: Timeout Occurred.
02/26 18:16:57 [08a8] GetMuxLock:: Timeout Occurred.
02/26 18:16:59 [0388] GetMuxLock:: Timeout Occurred.
...
02/26 18:32:24 [093c] ABSL:4001 SCSICommandRetry: This is MUX media. So NO WRITE RETRIES at this layer. Returning error = 3.
02/26 18:32:24 [093c] Default Tape Block Size for Device [6] is [65536]
02/26 18:32:24 [093c] Current Tape Block Size for Device [6] is [65536]
02/26 18:32:24 [093c] Windows NT SCSI PORT Error [ABSL:4001 CMD<WRITE> MS=121] - No Retry
02/26 18:32:24 [093c] =>ABSL:4001 Error. MS=121 [The semaphore timeout period has expired.]
02/26 18:32:24 [093c] Mux_WriteToTape_New:: Error / EW hit. tapeRetStatus = 0xf104. This MUX chunk started at posOnTape = 453858, iLoop = 0, nLoops = 1, transferFactor = 16, blocksToWrite = 2048, blocksWritten = 2048 -- jID[175], mID[12588671], jTKN[432629765], jNUM@68@, dcb[6], sNUM[4]
02/26 18:32:24 [093c] Mux_WriteToTape_New:: currentPosOnTape = 453870. -- jID[175], mID[12588671], jTKN[432629765], jNUM@68@, dcb[6], sNUM[4]
02/26 18:32:24 [093c] Mux_WriteToTape_New:: SERIOUS ERROR FROM TAPE DRIVE. currentBlockAddress = 453870, calculatedCurrentPos = 453874. Nevertheless Handle this gracefully. -- jID[175], mID[12588671], jTKN[432629765], jNUM@68@, dcb[6], sNUM[4]
02/26 18:32:24 [093c] Mux_WriteToTape_New:: MUX_ERROR. Session 4 grabbed the lock and HAS HIT error = 0xf104. -- jID[175],
...
02/26 18:44:19 [093c] =>ABSL:4001 Command:[SEEK POS ] <Drive>
02/26 18:44:19 [093c] ABSL:4001 Sense Key status: Media Error [03]
02/26 18:44:19 [093c] ABSL:4001 Additional sense: Recorded Entity Not Found [14, 00]
02/26 18:44:19 [093c] Mux_WriteToTape_New:: pfTapeSeekBlock to 453858 failed. error = 0xa5 -- jID[175], mID[12588671], jTKN[432629765], jNUM@68@, dcb[6], sNUM[4]
...
02/26 18:44:19 [0388] Mux_WriteDaemon:: Session = 6 has entered and is an error condition becz some other session = 0 HIT ERROR. -- jID[174], mID[12588671], jTKN[432498218], jNUM@67@, dcb[6], sNUM[6]
 
Here is the heart of the problem:
02/26 18:44:19 [093c] ABSL:4001 Sense Key status: Media Error [03]
02/26 18:44:19 [093c] ABSL:4001 Additional sense: Recorded Entity Not Found [14, 00]

The drive is reporting a media error because it could not read some data that was previously written to tape. This happened when the drive was told to reposition the tape.

It is not clear what the cause of this problem is so now is the time to check for updates to ARCserve, the SCSI controller driver, and the tape drive firmware. Also make sure the tape drives and library (if present) are disabled from within the OS Device Manager. See the faq Which Driver to Use for details.
 
There was a device in Windows called IBM Gateway Module SCSI Array Device. It was not installed (no driver),I have disabled it today. BAB sees it. What is this device exactly, can generate problems like Media Error?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top