Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Aug 1999 21:40:03 -0700 (PDT)
From:      "Kenneth D. Merry" <ken@kdm.org>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: kern/13433: 'camcontrol defects' SCSI error
Message-ID:  <199908280440.VAA18468@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: "Kenneth D. Merry" <ken@kdm.org>
To: dkelly@hiwaay.net
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/13433: 'camcontrol defects' SCSI error
Date: Fri, 27 Aug 1999 22:34:40 -0600 (MDT)

 dkelly@hiwaay.net wrote...
 > 
 > >Number:         13433
 > >Category:       kern
 > >Synopsis:       'camcontrol defects' does not work with IBM drives
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:        
 > >Keywords:       
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Fri Aug 27 20:10:01 PDT 1999
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     David Kelly
 > >Release:        FreeBSD 3.2-STABLE i386
 > >Organization:
 > n/a
 > >Environment:
 > 
 > 	
 > 
 > >Description:
 > 
 > Can't read defect lists from IBM SCSI drives.
 > I don't have non-IBM drives to try.
 > Same problem with Adaptec and Symbios controllers. /var/log/messages
 > might have slightly different error codes. See below for Symbios/NCR
 > example.
 > 
 > >How-To-Repeat:
 > 
 > % su -m
 > # camcontrol defects -f block
 > error reading defect list: Input/output error
 > # 
 > 
 > # tail -5 /var/log/messages
 > Aug 27 21:28:14 nospam su: dkelly to root on /dev/ttyp1
 > Aug 27 21:28:33 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded.
 > Aug 27 21:28:33 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0a84400.
 > Aug 27 21:28:33 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded.
 > Aug 27 21:28:33 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0a84400.
 > 
 > >Fix:
 > 	
 > I don't have a clue. Purchase non-IBM drives?
 
 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 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.
 
 - 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.
 
 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.
 
 Ken
 -- 
 Kenneth Merry
 ken@kdm.org
 


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?199908280440.VAA18468>