Table of Contents
Advertisement
a. Ask the customer to note which cartridges (VOLSER numbers) fail during the operation. (It is
possible to have multiple bad cartridges.)
b. If the customer received MIM Messages at the host or if you have MIM messages, get the "Message
Code" and associated VOLSER number, if available. See "Message codes" on page 45 and Figure 12
on page 42.
If a bad cartridge cannot be identified at the time of failure, the VOLSER field of the MIM is blank
and the VOLSER Valid Flag is 00; VOLSER not Valid.
c. If the customer received TapeAlerts at the host or you have TapeAlerts, get the TapeAlerts and the
VOLSER number for the suspect cartridge. Complete the action that is stated in "TapeAlert
reporting" on page 12.
d. Examine the FID F2 log by using the "LOGS" option of the CE menu on the service panel. Record
both the FIDs and the associated VOLSER numbers. See "CE FID FE Log menu" on page 135. The
F2 log displays entries for as many as 10 of the most recent occurrences of the F2 error. Each entry
consists of 4 lines of information that pertain to the error:
• The first line provides an alternate FID number that you can use to isolate the problem.
• The second line displays the first and last FSCs and the microcode link.
• The third line provides a power-on date/time stamp that is correlated with power-on hours in the
Show Statistics menu, or a Current Time Stamp option (if available).
• The fourth line provides the VOLSER number of the suspect cartridge, if available.
2. Examine the cartridge for damage. For example, the leader pin might not be attached or the cartridge
might be cracked. If the cartridge is damaged, ask the customer to repair or replace the cartridge.
Note: A repaired cartridge might be used long enough to recover data from that cartridge. When the
data is recovered, the cartridge must be discarded by the customer.
3. Clean the drive by inserting a cleaning cartridge. See "Excessive Clean messages" on page 183.
4. Try the operation again with the suspect drive and the suspect cartridge.
• Job Successful - Problem fixed. Go to "End of call" on page 185.
• Job Failed - If the same drive error code is reported, collect a dump for later use, and go to Step 5. If
a different error code is reported, complete the corrective action for that error code.
5. If extra cartridges or drives are available, you can use either method or both methods to isolate the
problem.
a. If another cartridge is available, try the operation again with the suspect drive.
• Job Successful - The suspect cartridge might be marginal. Go to Step 6a to further isolate.
• Job Failed - If a different drive error code is reported, complete the action that is associated with
that error code. If the same error appears, the drive might be marginal. Go to Step 6b to further
isolate.
b. If another drive is available, try the operation again with the suspect cartridge.
• Job Successful - The drive might be marginal. Go to Step 6b to further isolate.
• Job Failed - If a different drive error code is reported, complete the action that is associated with
that error code. If the same error appears, the media might be marginal. Go to Step 6a to further
isolate.
6. To further isolate, run the necessary diagnostic tests to test the condition of the drive or media.
Attention: The Test Media option overwrites data that is written on the tape. Before
proceeding, have the customer copy data to a known, good cartridge, or otherwise move data
for safe keeping. Use this test only when directed by your next level of support. You also can
run this test when it is requested by the customer after you made the customer aware that data
is lost.
244 IBM 3592 TS1140, TS1150, TS1155, and TS1160 Tape Drives: Maintenance Information
Advertisement
Table of Contents
