From owner-freebsd-scsi Tue Oct 23 21:41:52 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 509E337B401 for ; Tue, 23 Oct 2001 21:41:50 -0700 (PDT) Received: (from tim@localhost) by shell.futuresouth.com (8.11.6/8.11.1) id f9O4fne30680 for freebsd-scsi@FreeBSD.ORG; Tue, 23 Oct 2001 23:41:49 -0500 (CDT) Date: Tue, 23 Oct 2001 23:41:49 -0500 From: Tim To: freebsd-scsi@FreeBSD.ORG Subject: Exabyte EXB-210 tape changer Message-ID: <20011023234149.A29746@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Does anybody have an Exabyte EXB-210 tape changer working with FreeBSD 4.x? I get the following with chio. It doesn't look like chio.c or scsi_ch.c has been changed recently so I don't think updating the OS would help. Thanks, Tim % uname -a FreeBSD hades.number8.net 4.4-PRERELEASE FreeBSD 4.4-PRERELEASE #1: Thu Aug 16 19:04:26 CDT 2001 root@hades.number8.net:/usr/src/sys/compile/BACKUP i386 % dmesg [..] sa0 at ahc0 bus 0 target 1 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit) Mounting root from ufs:/dev/ad0s1a ch0 at ahc0 bus 0 target 0 lun 0 ch0: Removable Changer SCSI-2 device ch0: 3.300MB/s transfers ch0: 7 slots, 1 drive, 1 picker, 0 portals (ch0:ahc0:0:0:0): MOVE MEDIUM. CDB: a5 0 0 56 0 52 0 1 0 0 0 0 (ch0:ahc0:0:0:0): NOT READY asc:4,8e (ch0:ahc0:0:0:0): Vendor Specific ASCQ (ch0:ahc0:0:0:0): MOVE MEDIUM. CDB: a5 0 0 56 0 52 0 1 0 0 0 0 (ch0:ahc0:0:0:0): NOT READY asc:4,8e (ch0:ahc0:0:0:0): Vendor Specific ASCQ (ch0:ahc0:0:0:0): MOVE MEDIUM. CDB: a5 0 0 56 0 2 0 52 0 0 0 0 (ch0:ahc0:0:0:0): NOT READY asc:4,8e (ch0:ahc0:0:0:0): Vendor Specific ASCQ (ch0:ahc0:0:0:0): MOVE MEDIUM. CDB: a5 0 0 56 0 52 0 1 0 0 0 0 (ch0:ahc0:0:0:0): NOT READY asc:4,8e (ch0:ahc0:0:0:0): Vendor Specific ASCQ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 23 22:10:13 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id A525737B403 for ; Tue, 23 Oct 2001 22:10:07 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id f9O59d632601; Tue, 23 Oct 2001 23:09:39 -0600 (MDT) (envelope-from ken) Date: Tue, 23 Oct 2001 23:09:39 -0600 From: "Kenneth D. Merry" To: Tim Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Exabyte EXB-210 tape changer Message-ID: <20011023230939.A32580@panzer.kdm.org> References: <20011023234149.A29746@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20011023234149.A29746@futuresouth.com>; from tim@futuresouth.com on Tue, Oct 23, 2001 at 11:41:49PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Oct 23, 2001 at 23:41:49 -0500, Tim wrote: > Does anybody have an Exabyte EXB-210 tape changer working with FreeBSD > 4.x? I get the following with chio. It doesn't look like chio.c or > scsi_ch.c has been changed recently so I don't think updating the OS would > help. Try using 'chio ielem' before you try to move things around. It may be that the changer doesn't know where things are without being prompted to look. > % uname -a > FreeBSD hades.number8.net 4.4-PRERELEASE FreeBSD 4.4-PRERELEASE #1: Thu Aug 16 19:04:26 CDT 2001 root@hades.number8.net:/usr/src/sys/compile/BACKUP i386 > % dmesg > [..] > sa0 at ahc0 bus 0 target 1 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit) > Mounting root from ufs:/dev/ad0s1a > ch0 at ahc0 bus 0 target 0 lun 0 > ch0: Removable Changer SCSI-2 device > ch0: 3.300MB/s transfers > ch0: 7 slots, 1 drive, 1 picker, 0 portals > (ch0:ahc0:0:0:0): MOVE MEDIUM. CDB: a5 0 0 56 0 52 0 1 0 0 0 0 > (ch0:ahc0:0:0:0): NOT READY asc:4,8e > (ch0:ahc0:0:0:0): Vendor Specific ASCQ > (ch0:ahc0:0:0:0): MOVE MEDIUM. CDB: a5 0 0 56 0 52 0 1 0 0 0 0 > (ch0:ahc0:0:0:0): NOT READY asc:4,8e > (ch0:ahc0:0:0:0): Vendor Specific ASCQ > (ch0:ahc0:0:0:0): MOVE MEDIUM. CDB: a5 0 0 56 0 2 0 52 0 0 0 0 > (ch0:ahc0:0:0:0): NOT READY asc:4,8e > (ch0:ahc0:0:0:0): Vendor Specific ASCQ > (ch0:ahc0:0:0:0): MOVE MEDIUM. CDB: a5 0 0 56 0 52 0 1 0 0 0 0 > (ch0:ahc0:0:0:0): NOT READY asc:4,8e > (ch0:ahc0:0:0:0): Vendor Specific ASCQ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 23 22:18:14 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id B656337B405 for ; Tue, 23 Oct 2001 22:18:11 -0700 (PDT) Received: (from tim@localhost) by shell.futuresouth.com (8.11.6/8.11.1) id f9O5I5A34055; Wed, 24 Oct 2001 00:18:05 -0500 (CDT) Date: Wed, 24 Oct 2001 00:18:05 -0500 From: Tim To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Exabyte EXB-210 tape changer Message-ID: <20011024001805.A33779@futuresouth.com> References: <20011023234149.A29746@futuresouth.com> <20011023230939.A32580@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011023230939.A32580@panzer.kdm.org>; from ken@kdm.org on Tue, Oct 23, 2001 at 11:09:39PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Oct 23, 2001 at 11:09:39PM -0600, Kenneth D. Merry wrote: > Try using 'chio ielem' before you try to move things around. That gives me this (along with chio: /dev/ch0: CHIOELEM: Input/output error): (ch0:ahc0:0:0:0): INITIALIZE ELEMENT STATUS. CDB: 7 0 0 0 0 0 (ch0:ahc0:0:0:0): NOT READY asc:4,8e (ch0:ahc0:0:0:0): Vendor Specific ASCQ chio status works. mt offline works. Thanks! Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 23 22:23:59 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 65FEE37B401 for ; Tue, 23 Oct 2001 22:23:56 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id f9O5NrD32740; Tue, 23 Oct 2001 23:23:53 -0600 (MDT) (envelope-from ken) Date: Tue, 23 Oct 2001 23:23:53 -0600 From: "Kenneth D. Merry" To: Tim Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Exabyte EXB-210 tape changer Message-ID: <20011023232353.A32726@panzer.kdm.org> References: <20011023234149.A29746@futuresouth.com> <20011023230939.A32580@panzer.kdm.org> <20011024001805.A33779@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20011024001805.A33779@futuresouth.com>; from tim@futuresouth.com on Wed, Oct 24, 2001 at 12:18:05AM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Oct 24, 2001 at 00:18:05 -0500, Tim wrote: > > On Tue, Oct 23, 2001 at 11:09:39PM -0600, Kenneth D. Merry wrote: > > Try using 'chio ielem' before you try to move things around. > > That gives me this (along with chio: /dev/ch0: CHIOELEM: Input/output > error): > > (ch0:ahc0:0:0:0): INITIALIZE ELEMENT STATUS. CDB: 7 0 0 0 0 0 > (ch0:ahc0:0:0:0): NOT READY asc:4,8e > (ch0:ahc0:0:0:0): Vendor Specific ASCQ > > chio status works. > mt offline works. Odd that it would return an error but chio status would suddenly start working. Oh well, go figure. :) Can you move tapes around now? Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 23 22:28:38 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id A791F37B401 for ; Tue, 23 Oct 2001 22:28:35 -0700 (PDT) Received: (from tim@localhost) by shell.futuresouth.com (8.11.6/8.11.1) id f9O5SYx35121; Wed, 24 Oct 2001 00:28:34 -0500 (CDT) Date: Wed, 24 Oct 2001 00:28:34 -0500 From: Tim To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Exabyte EXB-210 tape changer Message-ID: <20011024002834.A34923@futuresouth.com> References: <20011023234149.A29746@futuresouth.com> <20011023230939.A32580@panzer.kdm.org> <20011024001805.A33779@futuresouth.com> <20011023232353.A32726@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011023232353.A32726@panzer.kdm.org>; from ken@kdm.org on Tue, Oct 23, 2001 at 11:23:53PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > On Tue, Oct 23, 2001 at 11:09:39PM -0600, Kenneth D. Merry wrote: > > > Try using 'chio ielem' before you try to move things around. > > > > That gives me this (along with chio: /dev/ch0: CHIOELEM: Input/output > > error): > > > > (ch0:ahc0:0:0:0): INITIALIZE ELEMENT STATUS. CDB: 7 0 0 0 0 0 > > (ch0:ahc0:0:0:0): NOT READY asc:4,8e > > (ch0:ahc0:0:0:0): Vendor Specific ASCQ > > > > chio status works. > > mt offline works. > > Odd that it would return an error but chio status would suddenly start > working. Sorry, I didn't make it clear. chio status has always worked. chio move didn't and still doesn't. So I still can not move the tapes. Right now somebody manually pushes the button every day to move to the next tape. Thanks, Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 23 22:29:50 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id F278B37B405 for ; Tue, 23 Oct 2001 22:29:47 -0700 (PDT) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f9O5TdH01429; Tue, 23 Oct 2001 22:29:39 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Tue, 23 Oct 2001 22:29:39 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Tim Cc: "Kenneth D. Merry" , freebsd-scsi@FreeBSD.ORG Subject: Re: Exabyte EXB-210 tape changer In-Reply-To: <20011024002834.A34923@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org make sure the 210 is configured in changer as opposed to stacker mode and that it's configured to accept SCSI commands (I vaguely recall something deep in the LCD screens about that) On Wed, 24 Oct 2001, Tim wrote: > > > On Tue, Oct 23, 2001 at 11:09:39PM -0600, Kenneth D. Merry wrote: > > > > Try using 'chio ielem' before you try to move things around. > > > > > > That gives me this (along with chio: /dev/ch0: CHIOELEM: Input/output > > > error): > > > > > > (ch0:ahc0:0:0:0): INITIALIZE ELEMENT STATUS. CDB: 7 0 0 0 0 0 > > > (ch0:ahc0:0:0:0): NOT READY asc:4,8e > > > (ch0:ahc0:0:0:0): Vendor Specific ASCQ > > > > > > chio status works. > > > mt offline works. > > > > Odd that it would return an error but chio status would suddenly start > > working. > > Sorry, I didn't make it clear. chio status has always worked. chio > move didn't and still doesn't. So I still can not move the tapes. > > Right now somebody manually pushes the button every day to move to the > next tape. > > Thanks, > > Tim > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 24 9:59:41 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cybernetics.com (cyborg.cybernetics.com [206.246.200.18]) by hub.freebsd.org (Postfix) with ESMTP id 2455437B401 for ; Wed, 24 Oct 2001 09:59:36 -0700 (PDT) Received: by cyborg.cybernetics.com id <119047>; Wed, 24 Oct 2001 12:59:21 -0400 Message-Id: <01Oct24.125921edt.119047@cyborg.cybernetics.com> X-Sender: martin@cybernetics.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 24 Oct 2001 12:49:52 -0400 To: freebsd-scsi@FreeBSD.ORG From: Martin Aherron Subject: Re: Exabyte EXB-210 tape changer In-Reply-To: References: <20011024002834.A34923@futuresouth.com> Mime-Version: 1.0 Content-Type: text/html; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 01:29 AM 10/24/2001, you wrote:
make sure the 210 is configured in changer as opposed to stacker mode and that
it's configured to accept SCSI commands (I vaguely recall something deep in
the LCD screens about that)


On Wed, 24 Oct 2001, Tim wrote:

> > > On Tue, Oct 23, 2001 at 11:09:39PM -0600, Kenneth D. Merry wrote:
> > > > Try using 'chio ielem' before you try to move things around.
> > >
> > >   That gives me this (along with chio: /dev/ch0: CHIOELEM: Input/output
> > > error):
> > >
> > >   (ch0:ahc0:0:0:0): INITIALIZE ELEMENT STATUS. CDB: 7 0 0 0 0 0
> > >   (ch0:ahc0:0:0:0): NOT READY asc:4,8e
> > >   (ch0:ahc0:0:0:0): Vendor Specific ASCQ
> > >
> > >   chio status works.
> > >   mt offline works.
> >

Matt has the right answer I think. From the 210 manual...


ASC             ASCQ
(byte 12)   (byte 13)         Description
04h             01h The library is performing an initialization after a reset or the door was
                     closed.
                83h The front door is open.
                84h The library is executing ROM boot code and cannot execute the
                    command.
                89h The library is in serial port mode.
                8Dh The library is in LCD Interface mode.
                8Eh The library is in sequential mode.

Table D-1   ASC and ASCQ values for the Not Ready (2h) sense key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 24 14:21:20 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 9C60C37B43D for ; Wed, 24 Oct 2001 14:21:02 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id XAA01068; Wed, 24 Oct 2001 23:21:01 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id f9OL1Zj36339; Wed, 24 Oct 2001 23:01:35 +0200 (MET DST) (envelope-from j) Date: Wed, 24 Oct 2001 23:01:35 +0200 (MET DST) Message-Id: <200110242101.f9OL1Zj36339@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <20011023234149.A29746@futuresouth.com> From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: Exabyte EXB-210 tape changer X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Cc: Tim Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Tim wrote: > Does anybody have an Exabyte EXB-210 tape changer working with > FreeBSD 4.x? I once had an EXB-220 at a FreeBSD system in order to verify it's functionality, before it eventually moved to a Sun running Legato^WSolstice Backup. > I get the following with chio. It doesn't look like chio.c or > scsi_ch.c has been changed recently so I don't think updating the OS > would help. > ch0: 7 slots, 1 drive, 1 picker, 0 portals > (ch0:ahc0:0:0:0): MOVE MEDIUM. CDB: a5 0 0 56 0 52 0 1 0 0 0 0 > (ch0:ahc0:0:0:0): NOT READY asc:4,8e > (ch0:ahc0:0:0:0): Vendor Specific ASCQ Well, go to the vendor, and ask for their specific ASCQ. ;-) The SCSI reference is available for download at Exabyte, and it tells at page D-1: [...] Table D-1 lists Not Ready (2h) error conditions. ASC ASCQ (byte 12) (byte 13) Description 04h 01h The library is performing an initialization after a reset or the door was closed. 83h The front door is open. 84h The library is executing ROM boot code and cannot execute the command. 89h The library is in serial port mode. 8Dh The library is in LCD Interface mode. 8Eh The library is in sequential mode. Table D-1 ASC and ASCQ values for the Not Ready (2h) sense key So it seems you have configured your library to accept medium changer commands along the serial port (as opposed to SCSI commands). Don't feel bad, it once hit me likewise, but my library has been in LCD interface mode. That's been the reason for me to download the manual. :) -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Oct 26 3:20:19 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id 2CBA937B401 for ; Fri, 26 Oct 2001 03:20:03 -0700 (PDT) Received: from [194.97.50.135] (helo=mx2.freenet.de) by mout1.freenet.de with esmtp (Exim 3.33 #1) id 15x45m-0002Zg-00 for scsi@freebsd.org; Fri, 26 Oct 2001 12:19:58 +0200 Received: from b854e.pppool.de ([213.7.133.78] helo=Magelan.Leidinger.net) by mx2.freenet.de with esmtp (Exim 3.33 #3) id 15x45l-0006MT-00 for scsi@freebsd.org; Fri, 26 Oct 2001 12:19:58 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.6/8.11.6) with ESMTP id f9QALvR02396 for ; Fri, 26 Oct 2001 12:21:58 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200110261021.f9QALvR02396@Magelan.Leidinger.net> Date: Fri, 26 Oct 2001 12:21:56 +0200 (CEST) From: Alexander Leidinger Subject: repeating medium errors and error from "camcontrol defects" To: scsi@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, RELENG_4_4: I get some errors: (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 f1 2b 50 0 0 c 0 (da0:ahc0:0:0:0): MEDIUM ERROR info:f12b59 asc:11,0 (da0:ahc0:0:0:0): Unrecovered read error sks:80,29 (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 f1 2b 50 0 0 c 0 (da0:ahc0:0:0:0): MEDIUM ERROR info:f12b59 asc:11,0 (da0:ahc0:0:0:0): Unrecovered read error sks:80,29 (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 f1 2b 50 0 0 c 0 (da0:ahc0:0:0:0): MEDIUM ERROR info:f12b59 asc:11,0 (da0:ahc0:0:0:0): Unrecovered read error sks:80,29 (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 f1 2b 50 0 0 c 0 (da0:ahc0:0:0:0): MEDIUM ERROR info:f12b59 asc:11,0 (da0:ahc0:0:0:0): Unrecovered read error sks:80,29 (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 f1 2b 50 0 0 c 0 (da0:ahc0:0:0:0): MEDIUM ERROR info:f12b59 asc:11,0 (da0:ahc0:0:0:0): Unrecovered read error sks:80,29 (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 f1 2b 50 0 0 c 0 (da0:ahc0:0:0:0): MEDIUM ERROR info:f12b59 asc:11,0 (da0:ahc0:0:0:0): Unrecovered read error sks:80,29 They are from 9:44 to 11:20 in the morning. I tried to issue "camcontrol defects da0 -f block -G", but I get "camcontrol: Error returned from read defect data command". da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) What did I wrong with camcontrol and what can I do to get rid of those errors? Do I have to replace the disk or the cable? Bye, Alexander. -- ...and that is how we know the Earth to be banana-shaped. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Oct 26 6:24:37 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by hub.freebsd.org (Postfix) with SMTP id 1E71E37B405 for ; Fri, 26 Oct 2001 06:24:35 -0700 (PDT) Received: (qmail 29330 invoked by uid 0); 26 Oct 2001 13:24:33 -0000 Received: from p3ee3778a.dip.t-dialin.net (HELO 1xp133) (62.227.119.138) by mail.gmx.net (mp002-rz3) with SMTP; 26 Oct 2001 13:24:33 -0000 Message-ID: <004701c15e21$a197b3d0$0400a8c0@1xp133> From: "Gregor Bittel" To: Subject: Re: repeating medium errors and error from "camcontrol defects" Date: Fri, 26 Oct 2001 15:24:22 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, >I tried to issue "camcontrol defects da0 -f block -G", but I get I get the same error, (4.1-Release), but you should try this one: camcontrol defects da0 -f phys -G Note that I use "phys" instead of "block", hope it helps. >What did I wrong with camcontrol and what can I do to get >rid of those errors? Do I have to replace the disk or the cable? First you should check the cable, then the termination, and at least another harddisk. -Gregor. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Oct 26 10:11:28 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 331BA37B406 for ; Fri, 26 Oct 2001 10:11:24 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id f9QHB7t53289; Fri, 26 Oct 2001 11:11:07 -0600 (MDT) (envelope-from ken) Date: Fri, 26 Oct 2001 11:11:06 -0600 From: "Kenneth D. Merry" To: Alexander Leidinger Cc: scsi@FreeBSD.ORG Subject: Re: repeating medium errors and error from "camcontrol defects" Message-ID: <20011026111106.A52864@panzer.kdm.org> References: <200110261021.f9QALvR02396@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200110261021.f9QALvR02396@Magelan.Leidinger.net>; from Alexander@Leidinger.net on Fri, Oct 26, 2001 at 12:21:56PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Oct 26, 2001 at 12:21:56 +0200, Alexander Leidinger wrote: > Hi, > > RELENG_4_4: > > I get some errors: > (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 f1 2b 50 0 0 c 0 > (da0:ahc0:0:0:0): MEDIUM ERROR info:f12b59 asc:11,0 > (da0:ahc0:0:0:0): Unrecovered read error sks:80,29 > (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 f1 2b 50 0 0 c 0 > (da0:ahc0:0:0:0): MEDIUM ERROR info:f12b59 asc:11,0 > (da0:ahc0:0:0:0): Unrecovered read error sks:80,29 > (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 f1 2b 50 0 0 c 0 > (da0:ahc0:0:0:0): MEDIUM ERROR info:f12b59 asc:11,0 > (da0:ahc0:0:0:0): Unrecovered read error sks:80,29 > (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 f1 2b 50 0 0 c 0 > (da0:ahc0:0:0:0): MEDIUM ERROR info:f12b59 asc:11,0 > (da0:ahc0:0:0:0): Unrecovered read error sks:80,29 > (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 f1 2b 50 0 0 c 0 > (da0:ahc0:0:0:0): MEDIUM ERROR info:f12b59 asc:11,0 > (da0:ahc0:0:0:0): Unrecovered read error sks:80,29 > (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 f1 2b 50 0 0 c 0 > (da0:ahc0:0:0:0): MEDIUM ERROR info:f12b59 asc:11,0 > (da0:ahc0:0:0:0): Unrecovered read error sks:80,29 > > They are from 9:44 to 11:20 in the morning. > > I tried to issue "camcontrol defects da0 -f block -G", but I get > "camcontrol: Error returned from read defect data command". > > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled > da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) > > What did I wrong with camcontrol and what can I do to get rid of those > errors? Do I have to replace the disk or the cable? As someone else already suggested, you should try using the 'phys' defect format, as many drives don't support the block format. As for the errors, they mean you have a bad block. Replacing the cable won't really affect the problem. You may want to look into getting a new drive, though, since medium errors typically indicate the drive is on its way out. To fix this particular bad block, what you should do is make sure read and write reallocation are turned on in mode page 1: camcontrol modepage da0 -m 1 -e -P 3 will allow you to edit the saved parameters and enable read and write reallocation. Then, write zeroes to the bad block to force the drive to remap it. Joerg Wunsch posted a this basic command in response to a similar question last week: dd if=/dev/zero of=/dev/da0 skip=0xf12b59 count=1 The caveat is that according to the man page, skip causes dd to skip on the input, not the output. I would suggest looking at the dd(1) man page and possibly using seek= instead. Alternatively, you can turn the read command into a write command and issue it via camcontrol: camcontrol cmd da0 -v -c "2a 0 0 f1 2b 59 0 v:i2 0" 1 -o 512 - < /dev/zero That should write 512 bytes (1 block) of zeros to block 0xf12b59. Obviously all of this is somewhat "dangerous" if you make a mistake, and in any case you're going to end up losing whatever data was in that 512 byte block. I normally use some variation of the camcontrol command above to force block remapping. I've thought about implementing a more automatic way of bad block remapping in camcontrol, but haven't really gotten around to it. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 27 9:57:23 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 51F5C37B406 for ; Sat, 27 Oct 2001 09:57:17 -0700 (PDT) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with esmtp (Exim 3.33 #1) id 15xWln-00079f-00; Sat, 27 Oct 2001 18:57:15 +0200 Received: from a34dd.pppool.de ([213.6.52.221] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.33 #3) id 15xWln-0000GL-00; Sat, 27 Oct 2001 18:57:15 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.6/8.11.6) with ESMTP id f9RGxFr03949; Sat, 27 Oct 2001 18:59:16 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200110271659.f9RGxFr03949@Magelan.Leidinger.net> Date: Sat, 27 Oct 2001 18:59:14 +0200 (CEST) From: Alexander Leidinger Subject: Re: repeating medium errors and error from "camcontrol defects" To: ken@kdm.org Cc: scsi@FreeBSD.ORG In-Reply-To: <20011026111106.A52864@panzer.kdm.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 26 Okt, Kenneth D. Merry wrote: (Please keep me in the CC.) [...] >> What did I wrong with camcontrol and what can I do to get rid of those >> errors? Do I have to replace the disk or the cable? > > As someone else already suggested, you should try using the 'phys' defect > format, as many drives don't support the block format. Yes, this works. > As for the errors, they mean you have a bad block. Replacing the cable > won't really affect the problem. You may want to look into getting a new > drive, though, since medium errors typically indicate the drive is on its > way out. It shows 285 defects with -P and 0 with -G. I thougth I have to replace it, when the -G list grows too fast, and not already if it just shows one error. > To fix this particular bad block, what you should do is make sure read > and write reallocation are turned on in mode page 1: > > camcontrol modepage da0 -m 1 -e -P 3 > > will allow you to edit the saved parameters and enable read and write > reallocation. Already turned on. > Then, write zeroes to the bad block to force the drive to remap it. Is there a way to determine the file which is affected? I didn't want just wrote zeros to it if I didn't know which file this affects. Maybe I'm able to replace the file from a backup after or before overwritting the block . Bye, Alexander. -- The best things in life are free, but the expensive ones are still worth a look. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 27 15: 1:12 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 33CB037B405 for ; Sat, 27 Oct 2001 15:01:06 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id f9RM0qB66402; Sat, 27 Oct 2001 16:00:52 -0600 (MDT) (envelope-from ken) Date: Sat, 27 Oct 2001 16:00:51 -0600 From: "Kenneth D. Merry" To: Alexander Leidinger Cc: scsi@FreeBSD.ORG Subject: Re: repeating medium errors and error from "camcontrol defects" Message-ID: <20011027160051.A66375@panzer.kdm.org> References: <20011026111106.A52864@panzer.kdm.org> <200110271659.f9RGxFr03949@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200110271659.f9RGxFr03949@Magelan.Leidinger.net>; from Alexander@leidinger.net on Sat, Oct 27, 2001 at 06:59:14PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, Oct 27, 2001 at 18:59:14 +0200, Alexander Leidinger wrote: > On 26 Okt, Kenneth D. Merry wrote: > > (Please keep me in the CC.) > > [...] > >> What did I wrong with camcontrol and what can I do to get rid of those > >> errors? Do I have to replace the disk or the cable? > > > > As someone else already suggested, you should try using the 'phys' defect > > format, as many drives don't support the block format. > > Yes, this works. > > > As for the errors, they mean you have a bad block. Replacing the cable > > won't really affect the problem. You may want to look into getting a new > > drive, though, since medium errors typically indicate the drive is on its > > way out. > > It shows 285 defects with -P and 0 with -G. I thougth I have to replace > it, when the -G list grows too fast, and not already if it just shows > one error. True enough. What probably happened in this case is that it wasn't able to recover the error on read, and you haven't tried to write the file, so it can't really do anything but report an error. > > To fix this particular bad block, what you should do is make sure read > > and write reallocation are turned on in mode page 1: > > > > camcontrol modepage da0 -m 1 -e -P 3 > > > > will allow you to edit the saved parameters and enable read and write > > reallocation. > > Already turned on. Cool. > > Then, write zeroes to the bad block to force the drive to remap it. > > Is there a way to determine the file which is affected? I didn't want > just wrote zeros to it if I didn't know which file this affects. Maybe > I'm able to replace the file from a backup after or before overwritting > the block . I don't know how you'd do that. It's probably possible to dissect the filesystem information to figure it out, but I don't know how to do that. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 27 15:35:37 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp.noos.fr (descartes.noos.net [212.198.2.74]) by hub.freebsd.org (Postfix) with ESMTP id 1298B37B406 for ; Sat, 27 Oct 2001 15:35:34 -0700 (PDT) Received: (qmail 32652366 invoked by uid 0); 27 Oct 2001 22:35:32 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.229.145]) (envelope-sender ) by 212.198.2.74 (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 27 Oct 2001 22:35:32 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.6/8.11.6) id f9RMZRQ77062; Sun, 28 Oct 2001 00:35:27 +0200 (CEST) (envelope-from root) Message-Id: <200110272235.f9RMZRQ77062@gits.dyndns.org> Subject: Re: repeating medium errors and error from "camcontrol defects" In-Reply-To: <20011026111106.A52864@panzer.kdm.org> To: "Kenneth D. Merry" Date: Sun, 28 Oct 2001 00:35:27 +0200 (CEST) Cc: Alexander Leidinger , scsi@FreeBSD.ORG Reply-To: clefevre@citeweb.net From: Cyrille Lefevre Organization: ACME X-Face: X-Mailer: ELM [version 2.4ME+ PL94c (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Kenneth D. Merry wrote: > On Fri, Oct 26, 2001 at 12:21:56 +0200, Alexander Leidinger wrote: [snip] > Then, write zeroes to the bad block to force the drive to remap it. I'm not really sure this always work. the way I use to remap bad block is to make a read check using the SCSI BIOS controller (TEKRAM and probably ADAPTEC allow this at boot time), when errors are encountered, the BIOS asks you whether or not you want to remap the defective block. so, I'm sure that bad blocks are remapped since it asks me to do something. Cyrille. -- Cyrille Lefevre mailto:clefevre@citeweb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Oct 27 21:35:33 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 6731337B403 for ; Sat, 27 Oct 2001 21:35:30 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id f9S4ZJ467851; Sat, 27 Oct 2001 22:35:19 -0600 (MDT) (envelope-from ken) Date: Sat, 27 Oct 2001 22:35:19 -0600 From: "Kenneth D. Merry" To: Cyrille Lefevre Cc: Alexander Leidinger , scsi@FreeBSD.ORG Subject: Re: repeating medium errors and error from "camcontrol defects" Message-ID: <20011027223519.A67823@panzer.kdm.org> References: <20011026111106.A52864@panzer.kdm.org> <200110272235.f9RMZRQ77062@gits.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200110272235.f9RMZRQ77062@gits.dyndns.org>; from clefevre@citeweb.net on Sun, Oct 28, 2001 at 12:35:27AM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Oct 28, 2001 at 00:35:27 +0200, Cyrille Lefevre wrote: > Kenneth D. Merry wrote: > > On Fri, Oct 26, 2001 at 12:21:56 +0200, Alexander Leidinger wrote: > [snip] > > Then, write zeroes to the bad block to force the drive to remap it. > > I'm not really sure this always work. the way I use to remap bad > block is to make a read check using the SCSI BIOS controller (TEKRAM > and probably ADAPTEC allow this at boot time), when errors are > encountered, the BIOS asks you whether or not you want to remap the > defective block. so, I'm sure that bad blocks are remapped since it > asks me to do something. That'll work as well, but it takes a while to do a verify on an entire disk. I think that in most cases, writing to the bad block, if you have AWRE turned on, will cause the block to get remapped. That is, unless, the drive is somehow able to write to the block but can't read it. You can detect that case by just trying to read the block once you've written it. If you can read it, it has likely been remapped. (Unless the drive can just "magically" read that block again.) The "right" solution to this would probably be to implement something in camcontrol similar to the BIOS verify routines that would then give the user the option of remapping a bad block, writing zeroes to it, etc. An adjunct to this command would be a separate camcontrol command to allow the user to remap a specific block. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message