Discussion Locked

Tape drive not responding

0 helpful
24 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
At a client site running SBS 4.5, The tape drive SOMETIMES responds with a message something like : "Tape device detected and initialised but not responding. Check cables and connectors". I've done that, and checked termination etc., with no luck. Couldn't find anything on Technet. Anyone else experienced this?

24 replies

by tmaclennan

Had a similar problem. COMPAQ had me update BIOS, drivers, and patches until the problem went away. Some tape drives even can be firmware-upgraded using (you guessed it!) a tape.

by lutzd

Sorry - not a Compaq, and all patches I could find have been applied. It's a new machine and the problem is very intermittant and has been happening from day 1.

Thanks for trying to help

by sfo farmer

It depends on who make the drive- it can be a number of things.
Does the BIOS see the tape during POST? If its a Compaq server look for errors pointing to cpq32fs2.sys on answer#1 response.
Another good source is www.dlttape.com (if you have a dltthey have a SCSI utility you can download). Check with your manufacture of your tape device to see if they have any diag programs.
The other question to ask your client is: has it ever worked before and when did it stop working...what changed (BIOS, new SCSI drivers etc.) Hope this helps ya! SFO

by lutzd

Thanks for trying to help. No, it's not a Compaq (interesting how Compaqs seem to cause a lot of problems, isn't it!?).
It has been like this from day 1 (new system recently installed), so nothing has changed. I first thought it might be a termination problem, but that seems to be OK.

by lutzd

Further to the above, it is a SCSI device and is detected on bootup. I contacted Seagate who pointed me in the direction of drivers, which have been applied. I don't think a BIOS upgrade would be the answer, as the BIOS doesn't talk to it. I have reduced the speed on the device number in the SCSI card setup. HELP!

by lutzd

Further to the above, it is a SCSI device and is detected on bootup. I contacted Seagate who pointed me in the direction of drivers, which have been applied. I don't think a BIOS upgrade would be the answer, as the BIOS doesn't talk to it. I have reduced the speed on the device number in the SCSI card setup. HELP!

by lutzd

Oops! Sorry about the double comment post! And sorry for the rejections so far - all good comments, but not the answer to my problem, I'm afraid!
One thing that might help - I am running up a new NT server at work and accidentally put in a cleaningtape. I then immediately went into NT backup and got exactly the same error message!
Maybe this will help prompt someone to see the answer!
Understandably the customer is rather distressed about this situation, never knowing if the backup is goingto work or not!
Thanks in advance!

by don christner

You don't mention what type of SCSI interface you are running, ie, SCSI 1, 2, 3 etc. I have had trouble with passive terminators, and have had no trouble with active terminators. If you are not using an active terminator, I would get one.

Good luck,
Don

by jcox303

Two questions, what type of tape are they using(dds2/3) and what service pack is installed? On my SBS box, if sp6a installs it's drivers and updates for the tape drive, it will no longer function. Had to reinstall orignal drivers and change them to read only. And, Ive had some problems with DDS3 tapes from time to time.

by Former member

Then it seems more of a media problem than anything else at the moment, unless you have more to add. I think there are different DAT mm tape sizes, such as 4mm or 8mm(?), QIC 40, 80..etc. Check with your tape vendor on the correct tape sizes, then buy a new package of them and try them out, after cleaning the drive. Some tapes dirty the drive right away and it needs immediate cleaning...

You mentioned Seagate, but don't mention whether it's backup exec, or a seagate drive. Do you have the latest patch for the backup program?

Also there are timing issues with SCSI controllers. Some only support a certain MHZ between tape drive controller. Check with your hardware vendor of the SCSI controller and tape drive.

by garoe48

I just had the same problem and went through all the same stuff. The Seagate tech gave up and said the heads were bad even though the drive wasn't that old. I said what the heck, if the heads are bad, they're bad. Then I ran the abrasive cleaning cartridge about 20 or 30 times, literally. It's been working fine ever since. I was upset. If I had to do it over again I'd try swabbing the heads with alcohol first.

Best, Glenn

by garoe48

The fact that a cleaning cartridge gave you the same error means its the heads or the tape. Try a new tape. If that doesn't work, clean the livin' weewee out the drive. A stuck microscopic particle is probably causing all your grief.

Best, Glenn

by jp.

As everyone else has said, I have had a similar problem. Truly.

What I found helped was going to control panel and backup. Remove the backup device driver then install it again (make sure you do not use existing drivers but load on new ones), reboot and it is OK

Hope it helped

by mckaytech

Based on my long and harried experience with tape drives, I think the drive itself has a problem (I don't expect any congratulations from Seagate for reaching that conclusion but it's the voice of experience). I've seen this scenario perhaps a half-dozen times in the past 3 years and in all cases it resolved with a replacement drive.

paul

by redviking

What backup software are you using? The error leads my mind to NT Backup. If using NT Backup and reading the steps taken then try to change the drive. If Veritas Backup Exec upgrade to latest build and use the veritas drivers. But give more information like errors in the event viewer.
Also what SCSI controller are you using? Try an Adaptec 2940 they rock! And set the SCSI ID anywhere between 2 and 5! And disable wide negotioation, and lower the transfer speed to the lowest speed.

by lutzd

Damn! Why didn't I see this before! I've fallen for this one in the past! Yes, lowering the transfer speed was the answer (from 166 to 20!). I feel like such an idiot (but where are you going to get one this time of day?).
Thanks for your help, andespecially thanks to all the others who tried to help. I'm sure that anyone who is having problems with tapes will find the answer in one of the above responses....

This discussion is closed to new replies.