More Errors

[edsmikem]

Tried to inventory a tape (1 tape) and here is what I got...

----- TapeAlert Events -----

Warning - A severe error occurred while reading or writing data. This job may not have been successfully completed.
Robotic Library: DELL 1
Drive: QUANTUM 0
Slot: 9

Critical - The tape drive needs cleaning:
1. If the operation has stopped, eject the tape and clean the drive.
2. If the operation has not stopped, wait for it to finish and then clean the drive.
Check the tape drive users manual for device specific cleaning instructions.
Robotic Library: DELL 1
Drive: QUANTUM 0
Slot: 9

Critical - The tape is damaged or the drive is faulty. Call the tape supplier helpline.
Robotic Library: DELL 1
Drive: QUANTUM 0
Slot: 9



This JUST started happening and the tape HAS been used before for jobs (as in, was used a few days ago). I've already tried updating drivers, removing Veritas itself, and reinstalling. Nothing seems to work.


Michael Morgan
EDS

personal url:

http://www.corpusmotorsports.com

 

[SQLBill]

Did you clean the tape drive(s)?

-SQLBill

 

[edsmikem]

Yes, all four tape drives have been cleaned and show "Unloaded" currently. Its eating up my cleaning tapes fast too. Went through 2 brand new cleaning tapes over the weekend

Michael Morgan
EDS

personal url:

http://www.corpusmotorsports.com

 

[SQLBill]

After cleaning the tape drive(s), did you try new tapes?
Remember, the old tapes have probably been damaged by a dirty tape drive.

Are you still having the problems?

If so, then it looks like your tape drive is damaged and causing damage to the tapes (including cleaning tapes). Or there is some 'gunk' on the drive that the cleaning tapes cannot get off.

-SQLBill

 

[edsmikem]

I'm actually afraid to use a "Brand New" tape since its labeled all the tapes in the DLT as Bad Media (which equals 26!) so far.

Michael Morgan
EDS

personal url:

http://www.corpusmotorsports.com

 

[edsmikem]

Plus, as I said before, its 4 Drives. All the drives wouldn't just stop working at the same time. Its something I cant figure out and its killing me

Michael Morgan
EDS

personal url:

http://www.corpusmotorsports.com

 

[SQLBill]

Did you make sure the tapes were being checked/used by all drives? Unless you assign a specific drive to the job, Veritas will always use the first one unless it is currently in use.

If you have tried all four and know all four are acting the same way, I suspect something (dirt) got into your library and on all four drives. Has anyone else had access to the library? Could someone (cleaning personnel included) sprayed something into the library? For example, someone sprayed the front of the library with cleaning fluid to make it look nicer. The cleaning fluid could have been sucked into the library and coated the drives. Dirt particles would easily stick to the fluid and damage the tapes and drives. Kinda far-fetched, but it's a possibility.

-SQLBill

 

[edsmikem]

Maybe i'm not explaining as much as I should.

I have disabled the drives one by one, which enabled me to test each drive verifying that they all in fact, had the same result.

Nothing could have been sprayed, sucked, etc into the library because the library is in a very secured area on a government base, along side many other servers, libraries, and the list goes on.

I tried to inventory earlier, and found that it does work, but cleans the drive midway. I tried a catalog of one tape, and it shows "Loading Media" the whole time, but, while watching the actual library in person, A tape is loaded, and then, after a few minutes, is removed, the drive shows "Clean Me", a cleaning tape is inserted, cleans the drive, inserts the tape to be used for the backup, runs for about 5 minutes (while still showing "Unloaded" on the library window and"Loading Media" in Veritas). After a few minutes of trying to use the tape, it then removes it, and reveals "Clean Me".. and this goes on and on. The drives aren't dirty and the tapes are good. Something isn't allowing communication of some sort, whether it be the scsi, the tape drive drivers, the library drivers, etc. I'm just lost and stuck in a rut here.

Michael Morgan
EDS

personal url:

http://www.corpusmotorsports.com

 

[SQLBill]

Okay, let's work on communications (between Veritas and the library)...

I assume you checked all the cables to make sure they are securely attached.

When you installed Veritas, which drivers did you tell it to use; the devices or Veritas'? (if you're not sure, right click on My Computer icon, select Properties, go to Hardware tab, select Device Manager. Expand Tape Devices and right click on a device and select properties.)

You have a DELL library, which kind? Does it have an LCD window on the front? Does it show a scsi connection (computer icon with a key under it)?

I don't see anywhere that you rebooted the library. If you haven't, follow these steps:

Stop BackupExec services.
Take Library offline
Power Library off
Wait a short while
Power Library on
Start BE services.

-SQLBill

 

[edsmikem]

Thanks for all your patience by the way SQLBill.

I have checked all cables and made sure everything was in its place.

When I installed Veritas (i've done this a few times now), and each time, I chose a different driver. First time, I did the recommended and let Veritas Drivers be used. The second time, I chose to allow Microsoft drivers. Same results occured with either or.

I have a Dell PowerVault 130T which includes 4 drives, 26 slots, a LCD screen on the door, etc. As for a scsi connection icon, I see nothing of the sort. I got off the phone not too long ago with Veritas Tech Support. Ran through driver updates, patches, etc. Shut down the computer, shut down the dlt, waited a minute or so, booted dlt, made sure it came up correctly. Then, then booted windows.

I'm seeing this in the event viewer now:

Application LOG>>

Adamm Mover Error: Read Failure!
Error = 0x0000048D
Drive = "QUANTUM 2"
{822023C3-5EB2-4CA9-81E5-728748AAC2E2}
Media = ""
{00000006-0000-0000-0000-000000000000}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)

SYSTEM LOG >>

The device, \Device\Scsi\aic78xx1, did not respond within the timeout period.

The device, \Device\Tape2, has a bad block.

RSM could not load media in drive Drive 1 of library DELL 130T.





Michael Morgan
EDS

personal url:

http://www.corpusmotorsports.com

 

[SQLBill]

Which drivers are you using now?

If you are using Veritas' drivers, you should be seeing the computer icon above a key icon on the left side of the lcd window on the library.

Since you aren't seeing it, that indicates the SCSI connection is 'broken'.

I noticed in your comments above that you never say you stopped the Backup Exec services. Please follow these directions (if you have and just skipped over saying so, I apologize):


Stop BackupExec services.
Take Library offline
Power Library off
Wait a short while
Power Library on
Start BE services

If you follow steps and still don't have the SCSI icons this has also worked for me:

Insert the Veritas Backup Exec disk and select the option for REPAIR.

-SQLBill

 

[edsmikem]

Drivers I'm using:

Dell (TM) PowerVault (TM) 130T Tape Library
Driver Files: C:\WINNT\System32\DRIVERS\Dell130.sys
Provider: Dell
File Version: 1.0.0.0
Driver Date: Not Available
Driver Version: 1.0.0.0


Adaptec AHA-2944UW PCI SCSI Controller
Driver Files: C:\WINNT\System32\DRIVERS\aic78xx.sys
Provider: Microsoft Corporation
File Version: v2.20b
Driver Date: 11/14/1999
Driver Version: 5.0.2183.1

Quantum DLTtape(tm) DLT7000 Drive
Driver Files: C:\WINNT\System32\DRIVERS\0dlttape.sys
Provider: VERITAS Software
File Version: 5.00
Driver Date: 6/17/2003
Driver Version: 5.0.1.1


Yesterday, I shutdown the server and 130T, pulled my SCSI card from the server and booted back up without SCSI or DLT. As for the items showing up in the Device Manager, they did not of course, since they were not actually connected. I then shut down again, put the SCSI card back in, powered up the DLT, then booted the server. Came up and the drives went through a test where the arm starts at drive 0, and engages the lever for about 10 seconds, then, disengages it, and moves to the next. After it does that, my event viewer shows:


Adamm Mover Error: Unlock Device Retry!
Error = ERROR_IO_DEVICE
Drive = "QUANTUM 4"

Adamm Mover Error: Unlock Device Retry!
Error = ERROR_IO_DEVICE
Drive = "QUANTUM 3"

Adamm Mover Error: Unlock Device Retry!
Error = ERROR_IO_DEVICE
Drive = "QUANTUM 2"

Adamm Mover Error: Unlock Device Retry!
Error = ERROR_IO_DEVICE
Drive = "QUANTUM 1"


Then, it moves on to Adamm Mover Error: Unlock Device Failure! for each drive.




Michael Morgan

http://www.eds.com