| Title: | MAGNETIC TAPEDRIVES |
| Moderator: | STKHLM::GJOHNSSON |
| Created: | Mon Sep 21 1987 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3775 |
| Total number of notes: | 13147 |
Hello,
i got into contact with a TLZ07-VA experiencing interesting errors
Operating System VAX VMS 6.2
Tape resides in a BA350 connected to a M3190
The original TLZ07-VA ( HW C07, FW 4BQE ) went bad, therefore I replaced it
with a new TLZ07-VA ( HW C07, FW 4BQE )
Customer called me now having errors on initializing some of his 120m-tapes
Those tapes are within a set of tapes which is about one jear old and
used about 16 times.
INIT/MEDIA=COMPACT MKA500: test
Command consumes a lot of time
giving response of PARITY ERROR,
increasing error count by one,
logging an errlog error
Errlog entry:
EXTENDED SENSE DATA RECEIVED
....
NORMAL SUCCESSFUL COMPLETION
WRITE FILEMARKS
CHECK CONDITION
MEDIUM ERROR
EXCESSIVE WRITE ERRORS
....
TESTING one of those tapes I got also another errlog entry
EXTENDED SENSE DATA RECEIVED
....
NORMAL SUCCESSFUL COMPLETION
READ
CHECK CONDITION
MEDIUM ERROR
MEDIUM FORMAT CORRUPTED
....
not seeing PARITY ERROR response
I was able to make backups ( MEDIA=COMPACT ) onto that tape without
further errors
after INIT MKA500: test without error
I initialized INIT/MEDIA=COMPACT MKA500: test without error
On new tapes INIT/MEDIA=COMPACT is O.K.
Questions:
- are those tapes logging errors really worn out ?
- should customer ignore error messages ?
- is backup to those tapes secure ?
- does a new rev. TLZ07 ( HW , FW ) recover such errors ?
Greetings
Bernd Dietrich, Austria
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3653.1 | See 3649 | UTRTSC::VISSER | Thu Feb 13 1997 00:58 | 21 | |
See note 3649.0
Go through it. Follow advices from there and see if you can get control
over the problem. Then give FEEDBACK to that note to share your
experience (did it assist you or not (and why)).
I do NOT expect the tapes to be worn out, EXCEPT if they were in a
drive, which caused scratches on the media OR had a serious load/unload
problem.
NEVER ignore errors. If a TLZ reports an error, it is allmost ALLWAYS
serious.
You can ONLY be sure of your backup, if you VERIFIED (BACKUP/VERIFY)
the backup!
A TLZ has error-recovery implemented. There are a very few error-codes
which indicate a recovered error. MOST errors however are reported by
the TLZ when ge gave up (fatal errors).
Jan
| |||||