Certance Tape drive problem on Windows NT Sever

G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.misc (More info?)

I have a STD224000N-SB, that is hooked up to a Adaptec 2906, it worked for a
few days then it started giving me an error message whenever I go to kick
off a backup, the message is "A tape device has been detected, and a tape
driver started. However, the tape device is not responding. Check that tape
device power is on and cables are properly connected.", it also gives an
Event ID:11 in the event viewer. I have already rebooted with no tape in
the drive, checked cables, and made sure termination is correct. One thing
that just popped into my mind is the cable has to connectors on it and I
have the tape drive on the end cable due to lack of length. The drive is
less than a month old and I have a new one sitting here, but am unsure if a
new tape drive is the answer. Unfortunately I am not at the location that
the tape drive is at but will be there next week. Any help would be
appreciated.
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.misc (More info?)

Hi

A few years ago i had same message on a seagate internal tape drive.
It worked two three times after cold booting the server and halted
agin with this same message and so on ...

Tape drive power had to be off until it works again couple of times.

After I configured from the drive dip switches the Hadware compression
off it begun working ok.

I think that if tehere are both harware compression and software compression
(ntbackup /hc:eek:n) on, some (seagate) drives wont work well.

jouko


"Eric Graham" <egraham22@yahoo.com> kirjoitti viestissä
news:emcZZPUrEHA.2580@TK2MSFTNGP15.phx.gbl...
> I have a STD224000N-SB, that is hooked up to a Adaptec 2906, it worked for
a
> few days then it started giving me an error message whenever I go to kick
> off a backup, the message is "A tape device has been detected, and a tape
> driver started. However, the tape device is not responding. Check that
tape
> device power is on and cables are properly connected.", it also gives an
> Event ID:11 in the event viewer. I have already rebooted with no tape in
> the drive, checked cables, and made sure termination is correct. One
thing
> that just popped into my mind is the cable has to connectors on it and I
> have the tape drive on the end cable due to lack of length. The drive is
> less than a month old and I have a new one sitting here, but am unsure if
a
> new tape drive is the answer. Unfortunately I am not at the location that
> the tape drive is at but will be there next week. Any help would be
> appreciated.
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.misc (More info?)

Thank you so much for the reply. I am unable to change the dip switches at
this point sue to the fact that the drive is at another location. I am
taking the /hc:eek:n out of the script that runs the backup and checking to see
if this does the trick. If not I will check the dip switches when I am at
the location later this week. I will post my results at the end of the
week. Thanks again for the post.


Eric


"Jouko" <jouko ormanto@pp inet fi...> wrote in message
news:0jP9d.140$W_3.129@read3.inet.fi...
> Hi
>
> A few years ago i had same message on a seagate internal tape drive.
> It worked two three times after cold booting the server and halted
> agin with this same message and so on ...
>
> Tape drive power had to be off until it works again couple of times.
>
> After I configured from the drive dip switches the Hadware compression
> off it begun working ok.
>
> I think that if tehere are both harware compression and software
compression
> (ntbackup /hc:eek:n) on, some (seagate) drives wont work well.
>
> jouko
>
>
> "Eric Graham" <egraham22@yahoo.com> kirjoitti viestissä
> news:emcZZPUrEHA.2580@TK2MSFTNGP15.phx.gbl...
> > I have a STD224000N-SB, that is hooked up to a Adaptec 2906, it worked
for
> a
> > few days then it started giving me an error message whenever I go to
kick
> > off a backup, the message is "A tape device has been detected, and a
tape
> > driver started. However, the tape device is not responding. Check that
> tape
> > device power is on and cables are properly connected.", it also gives an
> > Event ID:11 in the event viewer. I have already rebooted with no tape
in
> > the drive, checked cables, and made sure termination is correct. One
> thing
> > that just popped into my mind is the cable has to connectors on it and I
> > have the tape drive on the end cable due to lack of length. The drive
is
> > less than a month old and I have a new one sitting here, but am unsure
if
> a
> > new tape drive is the answer. Unfortunately I am not at the location
that
> > the tape drive is at but will be there next week. Any help would be
> > appreciated.
> >
> >
>
>
 

TRENDING THREADS