cancel
Showing results for 
Search instead for 
Did you mean: 

Drive Fetch Failure

Thomas_Andrews
Level 2
Hi,
I am having problems with the backups.
We ar currently using 10d backup software with MSL6000 and 2 X 600GB SDLT unit .
I have updated the firmware for MSL6000 tape libary and the unit. I still keep getting the error Event Type:

Error
Event Source:Backup Exec
Event Category:Devices
Event ID:33152
Date:7/08/2006
Time:5:19:27 PM
User:N/A
Computer:
Description:
Adamm Mover Error: Unload Status Failure!
Error = ERROR_NOT_READY
Drive = "HP 4"
{641A9937-C46A-47C3-916F-2FF7B9DB2923}
Media = ""
{00000000-0000-0000-0000-000000000000}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1) .


I have also changed the device drivers to Veritas device drivers.


Also whenever i run a job , and then kicks off a 2nd job, then the job just sits idle.

3013
Drive Fetch Failure
(Loader failed to fetch a cartridge from a drive.) .

Any ideas ?
thomas
5 REPLIES 5

Thomas_Andrews
Level 2
Also I get this error message - A tape drive has an error condition.

padmaja_rajopad
Level 6
Hi,

Does this problem occur with a specific tape drive of the autoloader?

Try initially running an inventory on the tape and verify the results.

Regards
Padmaja

Thomas_Andrews
Level 2
Hi
Seems that the drive fetch loader has gone away however another problem has come up.1st job is kicked off and then immediately its put in queue just after loading media. And then 2nd job kicks off which gets the idle message .

Could it be Software is thinking that the tapes are not ready for overwrite as I've checked in the device partiitions stating tapes are "scratch media" even though its brand new and i have already run the inventory andit is taking ages to complete.

Jim_Bollinger
Level 4
Make sure you are on 5.16 firmware or higher on the MSL Specifically 5.13 has a problem with "Drive Fetch error". If you are on 5.16 or higher, try running the calibration routine, which will reset all the limits for the robotics. What you are experiencing is a robot error, which calibration will solve as long as you are not on 5.13. Please see:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=981956

Deepali_Badave
Level 6
Employee
Hello,

Are you getting any alerts during the backup job?

What are the overwrite protection and append period settings?

Also install the latest drivers.

http://support.veritas.com/docs/284012

Regards,