tape keeps ejecting before I can do anything

[yert33]

Got a DDS tape drive that is reported as Archive Python 04106-XXX with firmware version 7550 installed in an IBM Netfinity 5000 running NT4.0 SP6a. Newly configured box.

When I stick a tape cartridge in it, both amber and green LED's light up then the tape ejects. So I can't even run an Inventory on tapes

It's a SCSI drive.

Any ideas?

 

[SQLBill]

Have you tried cleaning it?

How are you adding the tape?
- do you use the IMPORT command?
(go to Devices tab, right click on the device, select IMPORT - you should get a prompt asking you to insert the tape - put the tape into the drive and click OK)

Are there any error messages?
- check the Veritas' Alert tab
- check the job history
- check Windows Event Viewer logs

Lastly, is it the right kind of tape for the tape drive?

-SQLBill

 

[SQLBill]

Another thing to check...every tape has a 'door'/'slider' that makes the tape Write Protected. Is that door/slider in the Write Protected position?

-SQLBill

 

[yert33]

SQLBill - cannot do the IMPORT command because tape will not stay in drive, and no error messages. Tape IS a DDS-4 and the drive is a DDS-3...so I've ordered a DDS-3 tape to test with.

Also, tape is not write-protected.

All jumper and DIP switch settings are in the default position, the drive is the last and only device on the particular SCSI bus and there is a terminator at the end of the SCSI cable.

Both green and amber LED's light up solid the second the tape is inserted, stay lit up solid the whole time the tape is in then ejects itself after about 3 seconds.

From the documentation: Green LED lit steadily means "A cartridge is inserted and does not generate errors". Amber lit steady means "The tape drive is reading or writing to the tape".

I'll post when I get my hands on an actual DDS-3 tape, but I'm guessing this may not be the problem as a cleaning tape (that has no designation other than simply "DDS" on it, acts the same way.

Thanks for your replies.

 

[SQLBill]

In Backup Exec, are there any alerts?
On Active Job tab, is there a job in progress? Failed? If either one, double click the job and select Job History tab. Anything there?

In Windows, check the Event Viewer logs. Any error messages there?

-SQLBill

 

[yert33]

No to all. This was a fresh install of NT Server and Backup Exec. No jobs had ever been defined or run before.

 

[SQLBill]

When you installed Veritas BE, which drivers did you tell it to use?

-SQLBill

 

[SQLBill]

BTW- just a thought...I had a problem with a couple of tapes and a cleaning tape. After talking to the vendor, I found out they weren't compatible with a HP tape drive. I have had to specifically ask for LTO Ultrium 1 tapes for HP tape drives. Anything else doesn't always work.

-SQLBill

 

[yert33]

I told it to use the Veritas drivers. (I think this is identical to how our other machines are set up.)

I'm using the same (brand new) Sony tapes and cleaning tape that I use with my other IBM DDS-4 tape drives.

I called IBM and they said that a defective tape drive will very often exhibit this behavior of "self-ejecting". So I'm going to wait for my DDS-3 tape to arrive after which I will test again. I also have another DDS drive we own being sent back to me from another location.

Thanks for all the feedback, I appreciate it.

 

[SQLBill]

Let us know how it goes. Especially if you find a solution.

-SQLBill

 

[yert33]

Eureka! After doing 2 things, it is now working.
Thing 1: Bought an actual DDS-3 tape
Thing 2: Downloaded and installed Veritas driver for tape drive.

DOn't know if the driver was part of the solution or not.

I had switched out the Archive for a Sony DDS-3 drive and it exhibited the same problem of ejecting the media as soon as it was put in IF I USED A DDS-4 tape...... SO i put the Archive back in, used a DDS-3 tape and voila! all is well.

Thanks for your replies.....

 

[SQLBill]

So glad you found the solution. I would guess it was the tape incompatibility and that the driver wasn't the problem. (Updated drivers don't hurt though).

-SQLBill