IBM Magstar MP 3570 C Series, Maintenance Information

Page: 417 / 675

FID FE—Isolate Fault between Media and Hardware
| A FID FE will be generated when the drive experiences an error and cannot determine if the error was
| caused by the tape cartridge or by a problem in the drive hardware. The FID FE is not displayed on the
| drive, but is logged in the sense information that is returned to the host system. If the customer receives
| errors when reading or writing to the drive and there is no FID displayed on the drive, a FID FE was
| probably returned in the sense information to the host. If needed, refer to the MSG section to determine
| how to obtain service information from the host system.
| To determine the cause of the read or write errors, follow the steps below:
| 1. Ensure that the tape drive is not overdue for cleaning. The need for cleaning is determined by the
| tape drive. The tape drive should be cleaned only when indicated by the 3570. Cleaning the drive
| too frequently with the cleaning tape may cause excessive wear of the head assembly and may lead
| to read and write errors.
| a. Model C00 should be cleaned only when the Clean LED indicator on the drive bezel flashes.
| b. Library models should be configured to have automatic cleaning enabled and should have the
| cleaning cartridge loaded into the cleaning cell. The operator should allow the 3570 tape drives to
| clean themselves when necessary.
| c. Inform the operator that the 3570 should not be cleaned unless indicated. Cleaning the drive too
| frequently with the cleaning tape may cause excessive wear of the head assembly and may
| contribute to read and write errors.
| d. If a Model C00, clean if the CLEAN LED is lit.
| e. If a Library Model tape drive, ensure that the AUTO CLEAN option is ON and that a cleaner
| cartridge is installed.
| f. Always avoid excessive cleaning as this will damage the heads.
| 2. Determine which VOLSER #s or cartridges are potential problems:
| a. Ask the customer to note which cartridges (VOLSER #s) fail during the operation. (It is possible to
| have multiple bad cartridges.)
| b. If the customer received MIM Messages at the host, get the “Message Code” and associated
| VOLSER #. Refer to “Message Codes” on page MSG-11 and Figure 67 on page MSG-7.
| Note: VOLSER # is not in MIM if your drive is at microcode level D1I4_xxx.
| c. Examine the FID FE log using the "LOGS" option of the CE Menu on the operator panel. Collect
| both FIDs and associated VOLSER #s. See Figure 128 on page PANEL-26 and “CE FID FE Log
| Menu” on page PANEL-43. The FE log will display entries for up to 10 of the most recent
| occurrences of the FE error. Each entry consists of four lines of information that pertain to the
| error:
| 1) The first line provides an alternate FID number that you can use to isolate the problem.
| 2) The second line displays the first and last FSC's and the microcode link.
| 3) The third line provides a power-on date/time stamp which can be corollated with power-on
| hours in the "Show Statistics Menu", or a “Current Time Stamp” option (if present).
| 4) The fourth line provides VOLSER# of the suspect cartridge.
| Note: VOLSER # is not in MIM if your drive is at microcode level D1I4_xxx.
| d. If the customer received SIM messages at the host, get VOLSER #s from Sense Data which
| accompanied the SIM. Refer to “Obtaining 3570 Drive Error Information at the Host” on
| page MSG-3 and Figure 65 on page MSG-6.
| Note: VOLSER # is not in Sense Data if your drive is at microcode level D1I4_xxx.
PROC
Common Procedures
PROC-89