On Thu, 19 Jan 2006, Arno Lehmann wrote:
I'm really starting to think I have a bad tape on my hands, since btape
with a different tape succeeds in all respects.
I hadn't realised this was the case. Only one tape failing is very
indicative of it being faulty.
Good for you - replacing one ta
Hello,
On 1/19/2006 10:42 PM, Lance Brown wrote:
Arno Lehmann wrote:
...
BUT I'd suggest that you do the following:
- Check the system log for any tape or SCSI related errors. Use tapeinfo
to see the tape drive's status.
Oh joy I missed this when I looked last time:
Here is a cut of t
Arno Lehmann wrote:
> That said, the question is "Why does the SD need 4 minutes to find that
> there are no file marks on tape?"
>
> I don't know the answer.
>
> BUT I'd suggest that you do the following:
> - Check the system log for any tape or SCSI related errors. Use tapeinfo
> to see the tap
On Thursday 19 January 2006 20:59, Lance Brown wrote:
> Kern Sibbald wrote:
> > Below are a few guesses. They are a large part guesses because you didn't
> > specify enough information: please see the Support page on the web site.
>
> My mistake.
>
> System Information:
>
> Server:Dell PowerEdg
Kern Sibbald wrote:
> Below are a few guesses. They are a large part guesses because you didn't
> specify enough information: please see the Support page on the web site.
My mistake.
System Information:
Server:Dell PowerEdge 2650
OS:CentOS 3.6 (fully updated)
SCSI Card: LSI Logic /
