drive drive keeps going off line

[tookawhile]

After full backup (copy) job finishes, either as a policy or a manual job, the Quantum Superloader 3 (LTO3) tape library unit appears as off-line - I have to reboot the server for it to come back online (I guess I could restart a service instead?) - and this doesn't always work. I cannot even run inventory.

I've checked what I can, tape drive is the only device on a LSILogic120160 (latest drivesr) HBA, drive is terminated ( there is only one choice!), HBA has no conflicts, has it very own IRQ etc. I've swapped SCSI cables over, changed PCI slots for the HBA. It is set to SCSI ID2.

It appears the tape drive goes into some sort of pause state, if either the media server or the drive is rebooted it seems to come alive again - but of cause, goes off-ilne again after a job complete - really at a loss at the moment.

I've upgraded the firmware for the drive and library and it has made no difference.

It doe seem to be a SCSI issue but I'm at a loss as to what else to try

Job error

Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 33808
Date: 24/04/2007
Time: 10:42:13
User: N/A
Computer: SERVER-MS1
Description:
An error occurred while processing a B2D command.
Changer: Couldn't ReadFMTables/RecoverBKF (D:\server-fs1\B2D000239.bkf). Error=32

For more information, click the following link:

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

Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 34113
Date: 29/04/2007
Time: 03:28:17
User: N/A
Computer: SERVER-MS1
Description:
Backup Exec Alert: Job Failed
(Server: "SERVER-MS1") (Job: "server-fs1-server-fs1 - weekly-Backup Template 0427") server-fs1-server-fs1 - weekly-Backup Template 0427 -- The job failed with the following error: The data being read from the media is inconsistent.


For more information, click the following link:

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

Event Type: Error
Event Source: Backup Exec
Event Category: Devices
Event ID: 33152
Date: 27/04/2007
Time: 11:04:56
User: N/A
Computer: SERVER-MS1
Description:
Adamm Mover Error: Read Failure!
Error = ERROR_IO_DEVICE
Drive = "CERTANCE 1"
{F9740005-13B7-4E13-B661-742793F7A2F6}
Media = "test tape2"
{8BAE1217-BCE5-4B6A-A07B-3398C853EC65}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)
Data:
0000: 00 00 00 00 00 00 00 00 ........
0008: 00 00 00 00 00 00 ......



Event Type: Error
Event Source: halfinchVRTS
Event Category: None
Event ID: 15
Date: 30/04/2007
Time: 17:47:46
User: N/A
Computer: SERVER-MS1
Description:
The device, \Device\Tape0, is not ready for access yet.
Data:
0000: 0f 00 18 00 01 00 76 00 ......v.
0008: 00 00 00 00 0f 00 04 c0 .......À
0010: 04 01 00 00 9d 00 00 c0 ....?..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 00 00 02 00 00 00 ........
0030: 00 00 00 00 00 00 00 00 ........
0038: 00 4a 00 00 00 00 00 00 .J......




======================================================================
Job server: SERVER-MS1
Job name: Backup 00114

Job started: 24 April 2007 at 10:26:54
Job type: Backup
Job Log: BEX_SERVER-MS1_01076.xml
======================================================================

Drive and media mount requested: 24/04/2007 10:26:54

Drive and media information from media mount: 24/04/2007 10:28:19
Robotic Library Name: QUANTUM 1
Drive Name: CERTANCE 1
Slot: 8
Media Label: Full - Set4 - Tape2
Media GUID: {9868decd-e097-4c4a-bf28-843567bd3773}
Overwrite Protected Until: 01/01/1900 00:00:00
Appendable Until: 01/01/1900 00:00:00
Targeted Media Set Name: Weekly Disk2TapeDump - Set4


======================================================================
Job Operation - Backup
Media operation - overwrite.
Hardware compression enabled.
======================================================================

Family Name: "Media created 24/04/2007 10:26:54"
Backup of "D: "
Backup set #1 on storage media #1
Backup set description: "Backup 00114"
Backup Type: Full - Back Up Files - Reset Archive Bit

Backup started on 24/04/2007 at 10:28:35.

Drive and media mount requested: 24/04/2007 14:23:51

Drive and media information from media mount: 24/04/2007 14:26:26
Robotic Library Name: QUANTUM 1
Drive Name: CERTANCE 1
Slot: 7
Media Label: Full - Set4 - Tape1
Media GUID: {efd0ead3-6192-4bb3-b382-601539f45604}
Overwrite Protected Until: 01/01/1900 00:00:00
Appendable Until: 01/01/1900 00:00:00
Targeted Media Set Name: Weekly Disk2TapeDump - Set4

Backup set #1 on storage media #2

Backup completed on 24/04/2007 at 16:10:11.

Backed up 4 files in 2 directories.
3 items were skipped.
Processed 668913472400 bytes in 5 hours, 38 minutes, and 40 seconds.
Throughput rate: 1884 MB/min
----------------------------------------------------------------------

Family Name: "Media created 24/04/2007 10:26:54"
Backup of "E: "
Backup set #2 on storage media #2
Backup set description: "Backup 00114"
Backup Type: Full - Back Up Files - Reset Archive Bit

Backup started on 24/04/2007 at 16:10:19.
Backup completed on 24/04/2007 at 16:26:17.

Backed up 11 files in 4 directories.
1 item was skipped.
Processed 37,817,964,994 bytes in 15 minutes and 58 seconds.
Throughput rate: 2259 MB/min
----------------------------------------------------------------------

======================================================================
Job Operation - Verify
======================================================================

Drive and media mount requested: 24/04/2007 16:27:41

Drive and media information from media mount: 24/04/2007 16:30:07
Robotic Library Name: QUANTUM 1
Drive Name: CERTANCE 1
Slot: 8
Media Label: Full - Set4 - Tape2
Media GUID: {9868decd-e097-4c4a-bf28-843567bd3773}
Overwrite Protected Until: 01/01/1900 00:00:00
Appendable Until: 01/01/1900 00:00:00


Verify of "D: "
Backup set #1 on storage media #1
Backup set description: "Backup 00114"

Verify started on 24/04/2007 at 16:30:08.
Storage device "CERTANCE 1" reported an error on a request to read data from media.

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

Verify completed on 24/04/2007 at 16:30:15.

Verified 1 file in 2 directories.
0 files were different.
Processed 1,830,934 bytes in 7 seconds.
Throughput rate: 15.0 MB/min
----------------------------------------------------------------------

======================================================================
Job ended: 24 April 2007 at 16:30:21

Completed status: Failed

Final error: 0xe000fe09 - The directory is invalid.

Final error category: Resource Errors
For additional information regarding this error refer to link

http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml?EvtID=V-79-57344-65033

======================================================================


The amount of data backed up to tape appears to be about right, the backup job backs up the B2D folders to tape and is the only backup job running at the time.

The drive as been checked over by a Quantum engineer and be given a clean bill of health.

 

[tookawhile]

I've also ran Quantum's TapeRX and it reports no errors.

 

[LawnBoy]

The library should have a different address than the tape deck. Either they should have different SCSI ID numbers, or they can be on the same ID but different LUNs.

 

[tookawhile]

Both on same SCSI ID but Drive is LUN0, library LUN1.

 

[lockstemz]

I'm having a simlar problem with 11D version 1701 ... all the jobs run perfectly except for 1 the engine shuts down because the job gets stuck on pre-processing this generates and error and the application shuts down the engine if their is no response in a reasonable amount of time ... You can alelviate your issue by configuring the backup engine service to restart after 1st, 2nd and subsequent failures.

 

[tookawhile]

Have tried that, seems to have made no difference.

I've watched it, it completes the backup but as soon as the verification process starts if fails - drive goes off-line.

 

[tookawhile]

For the record, I've had the Quantum Superloader 3 (LTO3) and now all works as one would expect.

It appears the read head was faulty.

 

[LawnBoy]

That's funny, I had a quantum SDLT2 drive die last week... Quantum gave me quite the runaround to replace it, and then it took a week to get.

 

[tookawhile]

I paid for the extra 3 on-site warranty, maybe that helped.

Having said that, replacement loader took 3 days to be delivered. The engineer was very good, phoned up every day chasing the delivery of the replacement, within 2 hours of it being delivered he was on-site and knew what he was doing.

The first engineer who came out (when I first reported a problem) didn't seem to be on the ball as much.

In the UK Quantum sub contract their warranty work out.