Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TapeAlerts\s+on\s+LTO2\s+drives\,\s+tapes\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TapeAlerts\s+on\s+LTO2\s+drives\,\s+tapes\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: TapeAlerts on LTO2 drives, tapes (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Wed, 28 Jun 2006 14:23:33 -0400; Robin - Don't forget to formulate a tracking Subject title for postings. I invented an indicative name for this thread. We haven't heard from LTO customers on this, so I'll throw in some hypothetical; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-06/msg00377.html (14,786 bytes)
2. Re: TapeAlerts on LTO2 drives, tapes (score: 1): Author: Jurjen Oskam <jurjen AT STUPENDOUS DOT ORG>; Date: Thu, 29 Jun 2006 09:48:38 +0200; Back in 2005 we also had problems with our IBM LTO2 drives in a 3584 library. In the end we found out that these were all microcode-related. After upgrading to a fixed microcode level, we still kept; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-06/msg00380.html (11,633 bytes)
3. Re: TapeAlerts on LTO2 drives, tapes (score: 1): Author: Robin Sharpe <Robin_Sharpe AT BERLEX DOT COM>; Date: Thu, 29 Jun 2006 10:23:33 -0400; Thanks Jurjen and Richard, Sorry for omitting the subject.. I forgot to mention in my original post that STK guy upgraded all drives to the latest firmware a couple of weeks ago... we are now at 53Y2; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-06/msg00400.html (13,557 bytes)

Current List: 1 - 3
Page: [1]