Veritas-bu

[Veritas-bu] Help with drive being downed during duplication.

2000-04-11 10:10:25
Subject: [Veritas-bu] Help with drive being downed during duplication.
From: Nee, Patrick patrick.nee AT lmco DOT com
Date: Tue, 11 Apr 2000 10:10:25 -0400
> I have a script that repeatedly calls bpduplicate using a list generated
> from bpimagelist.
> 
> Here's a copy of it if you want to look at it. I should mention that if I
> use the GUI to duplicate them, instead of the script, I still get the same
> problem.
> 
        (Left out scripts for mailing list)

>       -----Original Message-----
>       From:   Rob Worman [SMTP:rob AT colltech DOT com]
>       Sent:   Monday, April 10, 2000 2:42 PM
>       To:     Nee, Patrick
>       Subject:        Re: [Veritas-bu] Help with drive being downed during
> duplication.
> 
>       are you using bpvault, or running bpduplicate yourself?
> 
>       >Hi everyone:
>       >
>       >I'm having a problem that seems like a HW config problem, but it
> only
>       >happens when I'm duplicating tapes. All of my backups run fine,
> then during
>       >the day, sometime in my duplication process a drive will be downed.
>       >Duplication will be stopped and xdevadm will have a request
> pending, saying
>       >that a tape needed is in a downed drive. I can't trace the problem
> to a
>       >specific tape, tape drive, drive slot on the robot, or specific
> images. It
>       >doesn't happen consistently either. I might duplicate 100's of
> images and
>       >then stop. I'll manually reset the drive and eject the tape and
> restart the
>       >process and it'll run fine. Some times it'll go for days before it
> stops.
>       >
>       >The resultant problems seems to be a SCSI unload failure. I've
> swapped the
>       >cables, drive order, and SCSI id's and it never fixes it. It seems
> to be a
>       >HW problems but it only comes when I'm doing duplication, never
> with
>       >anything else.
>       >
>       >I've included a snap from my syslog of the error.
>       >
>       >Any help would be really appreciated.
>       >
>       >Thanks
>       >
>       >-
>       >Patrick Nee
>       >
>       >Patrick.Nee AT lmco DOT com
>       >603.885.8634
>       >
>       >Apr 10 07:16:21 sncab1 vmunix:
>       >Apr 10 07:16:21 sncab1 vmunix: SCSI: Request Timeout -- lbolt:
> 170707190,
>       >dev: cd0650c0
>       >Apr 10 07:16:21 sncab1 vmunix:          lbp->state: 60
>       >Apr 10 07:16:21 sncab1 vmunix:          lbp->offset: ffffffff
>       >Apr 10 07:16:21 sncab1 vmunix:          lbp->uPhysScript: f4800000
>       >Apr 10 07:16:21 sncab1 vmunix:  From most recent interrupt:
>       >Apr 10 07:16:21 sncab1 vmunix:          ISTAT: 22, SIST0: 04,
> SIST1: 00,
>       >DSTAT: 80, DSPS: 00000006
>       >Apr 10 07:16:21 sncab1 vmunix:  NCR chip register access history
> (most
>       >recent last): 5222 accesses
>       >Apr 10 07:16:21 sncab1 vmunix:                 1, SCRATCHA:
> ff000080
>       >Apr 10 07:16:21 sncab1 vmunix:                 1, SSID: 84
>       >Apr 10 07:16:21 sncab1 vmunix:                 2, SCRATCHA0<-80
>       >Apr 10 07:16:21 sncab1 vmunix:                 0, SCRATCHA1<-10
>       >Apr 10 07:16:21 sncab1 vmunix:                 0, DSP<-f4800080
>       >Apr 10 07:16:21 sncab1 vmunix:           6855167, ISTAT<-20
>       >Apr 10 07:16:21 sncab1 vmunix:               236, ISTAT: 22
>       >Apr 10 07:16:21 sncab1 vmunix:                 5, SIST0: 04
>       >Apr 10 07:16:21 sncab1 vmunix:                 2, SIST1: 00
>       >Apr 10 07:16:21 sncab1 vmunix:                 2, DSTAT: 80
>       >Apr 10 07:16:21 sncab1 vmunix:                 2, DSPS: 00000006
>       >Apr 10 07:16:21 sncab1 vmunix:                 1, SCRATCHA:
> ff0010a0
>       >Apr 10 07:16:21 sncab1 vmunix:                 3, DSP: f4800058
>       >Apr 10 07:16:21 sncab1 vmunix:                 0, SCRATCHA1<-00
>       >Apr 10 07:16:21 sncab1 vmunix:                 0, CTEST3<-05
>       >Apr 10 07:16:21 sncab1 vmunix:                 0, STEST3<-82
>       >Apr 10 07:16:21 sncab1 vmunix:  lsp: 3bafb80
>       >Apr 10 07:16:21 sncab1 vmunix:          bp->b_dev: cd0650c0
>       >Apr 10 07:16:21 sncab1 vmunix:          scb->io_id: 648224b
>       >Apr 10 07:16:21 sncab1 vmunix:          scb->cdb: 11 01 00 06 71 00
>       >Apr 10 07:16:21 sncab1 vmunix:          lbolt_at_timeout:
> 170647090,
>       >lbolt_at_start: 170647090
>       >Apr 10 07:16:21 sncab1 vmunix:          lsp->state: 10d
>       >Apr 10 07:16:21 sncab1 vmunix:  lbp->owner: 3bafb80
>       >Apr 10 07:16:21 sncab1 vmunix:  scratch_lsp: 0
>       >Apr 10 07:16:21 sncab1 vmunix:  Pre-DSP script dump [f4800030]:
>       >Apr 10 07:16:21 sncab1 vmunix:          7834a000 0000000a 78351000
> 00000000
>       >Apr 10 07:16:21 sncab1 vmunix:          0e000002 f4800500 e0100004
> f48007b4
>       >Apr 10 07:16:21 sncab1 vmunix:  Script dump [f4800050]:
>       >Apr 10 07:16:21 sncab1 vmunix:          9f0b0000 00000006 0a000000
> f4800508
>       >Apr 10 07:16:21 sncab1 vmunix:          721a0000 00000000 e2100004
> f4800580
>       >Apr 10 07:16:21 sncab1 vmunix:
>       >Apr 10 07:16:21 sncab1 vmunix: SCSI: Abort -- lbolt: 170707190,
> dev:
>       >cd0650c0, io_id: 648224b
>       >Apr 10 07:16:21 sncab1 tldd[19961]: TLD(0) unload failed in
> io_open, No such
>       >device or address[6]
>       >Apr 10 07:16:21 sncab1 tldd[10205]: TLD(0) drive 3 (device 0) is
> being
>       >DOWNED, status: Unable to SCSI unload drive
>       >Apr 10 07:16:21 sncab1 tldd[10205]: Check integrity of the drive,
> drive
>       >path, and media
>       >
>       >_______________________________________________
>       >Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>       >http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
>       --
>       Rob Worman, Consultant
>       Collective Technologies           cell: 612/802-6850
>       "The Power of Many Minds"         alpha page: 1-800-946-4646,
> pin=1422494



<Prev in Thread] Current Thread [Next in Thread>