Downloading drive log
Edit online
To retrieve a drive log, utilize one of the methods described in the following sections:
Downloading drive log through the host interface
1. Open ITDT-GE.
2. For further instructions, see Dump.
Downloading drive log with the Ethernet port - Service only
Tip: The drive uses a limited version of FTP protocol to communicate on the Ethernet interface. Use a simple, command-line FTP session, such as the DOS command line,
to communicate with the drive.
1. Connect an Ethernet patch cable to the drive's Ethernet interface and to a computer. To meet electromagnetic immunity requirements, a shielded Ethernet cable is
required.
2. Create an FTP session between the drive and the computer. The drive 's IP address: 169.254.0.3
3. At the user prompt, type guest and press Enter.
4. At the password prompt, press Enter. No response is needed.
5. Type bin to set the communication mode to binary.
6. Type mget *.dmp to transfer a drive memory dump to the computer. If a memory dump exists, the drive shows you the memory dump name and ask if you want to
transfer it to the computer. Type y to transfer the existing memory dump or n to skip this dump file. Then, the drive asks if you want a forced memory dump. Type y
to force a memory dump and to transfer the forced memory dump to the computer, or type n to skip forcing a memory dump.
7. Type quit to end the FTP session.
8. Remove Ethernet patch cable from the drive's Ethernet interface and the computer.
Troubleshooting guide
Edit online
Table 1. Tape drive problems
Problem Action
Drive has no power 1. Try a different electrical outlet or power cord.
2. Refer to Pre-call checklist. If this doesn't help, contact IBM technical support.
Cooling fan not working Refer to Pre-call checklist. If this doesn't help, contact IBM technical support.
SCD and fault light indicting
an error
1. See Drive error codes and messages for any possible errors.
2. Update firmware.
3. Refer to Pre-call checklist. If this doesn't help, contact IBM technical support.
Can’t write to or read from
tape
Make sure that the cartridge isn’t a WORM cartridge that was already used.
Make sure that the cartridge is write enabled (move the write-protect switch to the enabled position).
Make sure that the data cartridge is compatible with the drive model. See Media compatibility.
Make sure that you’re using an LTO cartridge that isn’t degaussed.
CAUTION:
Don’t degauss LTO cartridges!
Make sure that the cartridge wasn’t exposed to harsh environmental or electrical conditions and isn’t physically damaged in any
way.
Many backup applications don’t read or write to cartridges that were created with a different backup application. In this case, you
might need to run an erase, format, or label operation on the cartridge.
Make sure that you understand any data protection or overwrite protection schemes that your backup application might be using,
which might prevent you from writing to a specific cartridge.
Retry the operation with a different, known good tape.
Clean the tape drive.
Tape drive not
communicating with the
server
1. Ensure that the communication path between the host and the drive is functioning properly. See Host not communicating with
drive. If your problem is not resolved, go to next step.
2. Refer to Pre-call checklist. If this doesn't help, contact IBM technical support.
Table 2. Cartridge problems
Problem Solution