Constant DLT-S4 problems

We've been using DLT-S4 for approx 12 months (We're running 2010 R3 tape drivers are Symantec 5.1.25.0)

Last year, around Feb '11 we started getting backup errors and Quantum replaced our unit, this immediately sorted the problem.

2-3 months after the replacement, it started happening again (Nov '11). Again Quantum replaced the unit and this immeditely solved the problem.

Last week it started to happen again

These are the errors from the Server 2003 Application log in Nov '11

[0744] 11/22/11 04:48:04 Adamm Mover Error: DeviceIo: 03:00:06:00 - Device error 1117 on "\\.\Tape0", SCSI cmd 0a, 1 total errors

%2

%3

%4

%5

%6

%7

%8

[0744] 11/22/11 04:53:04 Adamm Mover Error: DeviceIo: 00:00:06:00 - Retry Logic: Retry logic was engaged on device: QUANTUM DLT-S4

%2

%3

%4

%5

%6

%7

%8

[0744] 11/22/11 04:53:04 Adamm Mover Error: DeviceIo: 03:00:06:00 - Refresh handle on "\\.\Tape0", SCSI cmd 00, new handle 5d8, error 1117

%2

%3

%4

%5

%6

%7

%8

[0744] 11/22/11 04:56:50 Adamm Mover Error: DeviceIo: 00:00:06:00 - Retry Logic: Failed to space to end of data on device: QUANTUM DLT-S4

%2

%3

%4

%5

%6

%7

%8

Storage device "QUANTUM DLT-S4" reported an error on a request to write data to media.

Error reported:

The request could not be performed because of an I/O device error.

.

For more information, click the following link:

http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

Adamm Mover Error: Read Failure!

Error = ERROR_CRC

Drive = "QUANTUM DLT-S4"

{1C2EC5DC-66D9-4335-8A0A-C3142A70EC07}

Media = "DLT000117"

{BFDE18A4-F4A6-4F17-852B-A9475AD7BC50}

Read Mode: SingleBlock(0), ScsiPass(0)

Write Mode: SingleBlock(1), ScsiPass(1)

Storage device "QUANTUM DLT-S4" reported an error on a request to read data from media.

Error reported:

0x17.

For more information, click the following link:

http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

Backup Exec Alert: Job Failed

(Server: "TIMOR") (Job: "Daily to SDLT v3 (Full)") Daily to SDLT v3 (Full) -- The job failed with the following error: A hardware error occurred.

 

For more information, click the following link:

http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

These are the errors from the Server 2003 Application log in from the past couple of days.

 

[0656] 01/14/12 01:09:09 Adamm Mover Error: DeviceIo: 03:00:06:00 - Device error 1117 on "\\.\Tape0", SCSI cmd 0a, 1 total errors

%2

%3

%4

%5

%6

%7

%8

 

[0656] 01/14/12 01:14:09 Adamm Mover Error: DeviceIo: 00:00:06:00 - Retry Logic: Retry logic was engaged on device: QUANTUM DLT-S4

%2

%3

%4

%5

%6

%7

%8

[0656] 01/14/12 01:14:09 Adamm Mover Error: DeviceIo: 03:00:06:00 - Refresh handle on "\\.\Tape0", SCSI cmd 00, new handle 6bc, error 1117

%2

%3

%4

%5

%6

%7

%8

[0656] 01/14/12 01:20:10 Adamm Mover Error: DeviceIo: 00:00:06:00 - Retry Logic: Failed to space to end of data on device: QUANTUM DLT-S4

%2

%3

%4

%5

%6

%7

%8

Storage device "QUANTUM DLTS4" reported an error on a request to write data to media.

Error reported:

The request could not be performed because of an I/O device error.

.

For more information, click the following link:

http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

Backup Exec Alert: Tape Alert Error

(Server: "TIMOR") (Job: "Daily to SDLT v3 (Full)") Job 'Daily to SDLT v3 (Full)' has reported Multiple Tape Alerts on Server 'TIMOR'. Please refer to job log BEX_TIMOR_08078.xml for more details.

For more information, click the following link:

http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

We've changed nothing, Servers do not auto update but this is starting to become annoying.

Although the errors seem very similar, here's what BE reported in the log failure for the past three days

Job ended: 16 January 2012 at 08:56:12
Completed status: Failed
Final error: 0xe00084ed - A hardware error occurred.
Final error category: Backup Device Errors

For additional information regarding this error refer to link V-79-57344-34029

Backup- E:
Storage device "QUANTUM DLTS4" reported an error on a request to write data to media.
Error reported:
The request could not be performed because of an I/O device error.
V-79-57344-34029 - A hardware error occurred.
 

 

Backup- KARA
Media mount failed.
User canceled a Physical Volume Library operation.

One thing I did try was to lower the priority of the Agent on the Exchange Server (KARA), but this has had no affect.