Re: [Dump-users] dump spontaneously stopped working

[Jon N. B. <ma...@nv...>]

	Well I just had a terrifying ordeal that may shed some light on
this subject.  When I came in today to try switching SCSI cables on the
tape drive, I got an alarm from the PERC RAID card.  Turns out none of the
drives were bad, it had just gotten confused somehow as to what the
configuration was.  I rebuilt the original offender just to be sure, and
the system is now up and running again with all three drives functioning
in the array.

	I thought that this might have been the source of my problems
dumping to tape, but sadly, the problem persists.  I can issue mt commands
that function until I try them after a failed dump operation.  Then they
no longer work.  Granted, I've only tried rewind, retension and rewoffl,
so it could still be a drive issue.  I plan on calling Dell to see if they
can send me yet another drive to try out, as the one they sent was
refurbished.

	Does anyone have any other ideas for me to try?  Does any of the
above info trigger a red flag for anyone?

Thanks for the help.

~Jon.





On Wed, 14 Jan 2004, Jon N. Brelie wrote:

> 
> 	Ah yes.  Sorry, it was late.  I should bhave been more clear.  mt
> commands only fail *after* a failed dump operation.  If I pop in a fresh
> tape, they work.
> 
> 	The drive came with a Dell PE 1400.  I think Seagate is the
> original manufacturer.  Model number is STD2401LW.  Connection is
> internal SCSI.  I've tried different cables, different channels, checked
> connections and termination...  I'm really stumped.
> 
> 
> 
> 
> On Wed, 14 Jan 2004, Antonios Christofides wrote:
> 
> > Jon N. Brelie wrote:
> > > st0: Error with sense data: Info fld=0x0, Current st09:00: sense key
> > > Medium Error
> > > Additional sense indicates Excessive write errors
> > > st0: Error on write filemark.
> > 
> > (This isn't a dump problem, of course, since mt also has problems; it
> > seems to be a hardware problem).
> > 
> > What model/make is the drive? How is it connected? Is it a SCSI? What
> > model/make is the SCSI interface? Try a different cable, and
> > check/replace SCSI terminators. If this fails, shutdown and switch off
> > the machine and the drive, then switch them on again. If this also
> > fails, you should try a different interface.
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Perforce Software.
> > Perforce is the Fast Software Configuration Management System offering
> > advanced branching capabilities and atomic changes on 50+ platforms.
> > Free Eval! http://www.perforce.com/perforce/loadprog.html
> > _______________________________________________
> > Dump-users mailing list
> > Dum...@li...
> > https://lists.sourceforge.net/lists/listinfo/dump-users
> > 
> 
> 

-- 



*******************************

 Jon N. Brelie
 Information Systems Manager
 NVE Corp.

*******************************