I was a very early user of 9840 (Dec 98) and I did have one hard error. It
was traced to a manufacturing problem at Imation.  They corrected the
problem and recalled cartridges that could have the same error.

I didn't actually lose any data.  The bad volume was a primary which had
been filled by move data commands to move off of 3490 tapes. I still had a
3490 copypool and was able to restore the volume. The error occured while
I was building a 9840 copypool.

I haven't had any serious read errors since then (Jan 99) and I am very
happy with the 9840's.  I am running them in 3490 mode because 3590 mode
wasn't supported at the time we got them.


--
--------------------------
--------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------
In <958FD09B4E43D21199C00020352997F7071F9DB5 AT se001002.rbc1.royalbank DOT 
com>, on 04/28/00
In <958FD09B4E43D21199C00020352997F7071F9DB5 AT se001002.rbc1.royalbank DOT 
com>, on 04/28/00
   at 02:47 PM, "Burton, Robert" <ROBERT.BURTON AT ROYALBANK DOT COM> said:

>We currently are running a 3494 tape library with 12 3590 drives.... We
>are in the process of trying to make a decision on whether to keep with
>our current
>tape media or switch to a STK library with 9840's...
>Recently we have been bitten by 3590 READ errors during our copy pool
>processing which we could not recover with a move data...

>If you would be so kind I would like to get a reply back from 3590 and
>9840 users as to any media problems
>that you have experienced that have caused you to lose data....

>thanks fellow ADSM/TSM'ers
>Robert Burton
>Open Systems Storage Analyst
>Royal Bank of Canada
>(416) 348-3849
>Robert.Burton AT RoyalBank DOT com