Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Aug 1999 12:30:02 -0700 (PDT)
From:      David Kelly <dkelly@hiwaay.net>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: kern/13433: 'camcontrol defects' SCSI error 
Message-ID:  <199908291930.MAA18662@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

The following reply was made to PR kern/13433; it has been noted by GNATS.

From: David Kelly <dkelly@hiwaay.net>
To: "Kenneth D. Merry" <ken@kdm.org>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/13433: 'camcontrol defects' SCSI error 
Date: Sun, 29 Aug 1999 13:41:47 -0500

 "Kenneth D. Merry" writes:
 > You can read the defects list on an IBM drive.  Here's an example:
 > 
 > ========================================================================
 > # uname -rs                        
 > FreeBSD 3.2-STABLE
 > # camcontrol inquiry da1           
 > pass1: <IBM DDRS-39130 S97B> Fixed Direct Access SCSI-2 device 
 > pass1: Serial Number RE2B9804        
 > pass1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled
 > # camcontrol defects da1 -f phys -G
 > Got 4 defects:
 > 189:6:72
 > 189:6:73
 > 189:6:74
 > 189:6:75
 > # camcontrol defects da1 -v -PG -f phys
 > (pass1:ahc0:0:1:0): READ DEFECT DATA(10). CDB: 37 0 1d 0 0 0 0 fd e8 0 
 > (pass1:ahc0:0:1:0): error code 0
 > Got 457 defects:
 > 38:4:188
 > 38:4:189
 > 38:4:190
 > 38:4:191
 > 38:4:192
 > 38:4:193
 > 38:4:194
 > 38:4:195
 > [ .... lots more .... ]
 > ========================================================================
 > 
 > There are several things to mention here:
 > 
 > - The NCR driver, at this point, is known to be a little flaky sometimes,
 >   and it's difficult to interpret the error messages from it.  It would be
 >   helpful if you show the output from one of your Adaptec controllers.  The
 >   IBM disk on in the above example is on an Adaptec 2940UW (7880) board.
 
 The DCAS and DDRS drives which are connected to Adaptec controllers are 
 at work, beyond my reach at the moment. I'll try the exact example you 
 provide... tomorrow.
 
 Meanwhile here is what I get when attempting the slightly different 
 command lines provided (Symbios/NCR '875, DCHS):
 
 # camcontrol inquiry
 pass2: <IBM OEM DCHS09W 2222> Fixed Direct Access SCSI-2 device 
 pass2: Serial Number         68210913
 pass2: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled
 # camcontrol defects -f bfi
 error reading defect list: Input/output error
 # camcontrol defects -f phys
 error reading defect list: Input/output error
 # camcontrol defects da0 -v -PG -f phys
 error reading defect list: Input/output error
 CAM status is 0
 
 tail -4 /var/log/messages says:
 Aug 29 13:23:25 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded.
 Aug 29 13:23:27 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 0) @0xc0a84400.
 Aug 29 13:23:27 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded.
 Aug 29 13:23:27 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 0) @0xc0a84400.
 
 The "camcontrol defects da0 -v -PG -f phys" is notable because there 
 was a 2 second delay not present in other attempts.
 
 Further experiments suggest -P causes the delay.
 
 > - The only disks I've seen that will return defects in block format are
 >   Quantum disks.  IBM and Seagate disks generally will not.  They will,
 >   however, return defects in physical sector format, as I demonstrated above.
 
 I used "block" in my earlier example simply because 1) there was no 
 default format, and 2) "block" was listed first in camcontrol(1).
 
 > - In your example command above, you did not specify either the GLIST or
 >   PLIST.  That can cause problems with some disks.  You may want to specify
 >   both the GLIST and PLIST (-PG).  I have a Seagate disk that doesn't seem
 >   to want to return any defects unless both are specified.
 > 
 > - You should specify the -v switch to camcontrol so you have a chance of
 >   getting SCSI sense information when the command fails.
 
 "CAM status is 0" appears to be all -v does in this case.
 
 > I won't deny that there may be a problem with getting the defect lists off
 > drives in some cases, but I will say that I haven't seen many problems
 > personally.
 > 
 > I'll need some more information (as outlined above) to get an idea of what
 > may be wrong here.
 
 Used to have a spare '875 card that I could carry to work to try there. 
 But the way things are now I believe I'll be carrying some of my HD's 
 at work (they are mine, not work's) home to try. Got a great deal on 
 DDRS drives a while back and bought two where only one was called for.
 
 I do have an old narrow 2940 here at home. Its driving my tape drives. 
 The DCHS is wide. Not sure how it would behave on a narrow controller 
 if I had cables to connect it.
 
 to be continued.
 
 --
 David Kelly N4HHE, dkelly@nospam.hiwaay.net
 =====================================================================
 The human mind ordinarily operates at only ten percent of its
 capacity -- the rest is overhead for the operating system.
 
 
 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908291930.MAA18662>