Date: Sun, 29 Aug 1999 14:06:12 -0500 From: David Kelly <dkelly@hiwaay.net> To: "Kenneth D. Merry" <ken@kdm.org> Cc: groudier@club-internet.fr (Gerard Roudier), freebsd-scsi@FreeBSD.ORG Subject: Re: Seagate vs Quantum.. opinions? Message-ID: <199908291906.OAA94336@nospam.hiwaay.net> In-Reply-To: Message from "Kenneth D. Merry" <ken@kdm.org> of "Sat, 28 Aug 1999 01:37:39 MDT." <199908280737.BAA94296@panzer.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"Kenneth D. Merry" writes: > In any case, David, I'd say try the following things, in light of what > Gerard said: > > - first, try using the -v switch, -f phys (instead of block format, since > only Quantum disks seem to support it, and the SCSI-2 spec says: "NOTE 110 The use of the block format is not recommended. There is no universal > model that sensibly defines the meaning of the logical block address of > a defect. In the usual case, a defect that has been reassigned no longer > has a logical block address.") and -PG. > > - If that doesn't work, try increasing the dlist_length parameter in > readdefects() in src/sbin/camcontrol/camcontrol.c to 65536. Interesting. Believe this was at least part of the problem. I don't know that I believe the answer but it did make a difference: # ./camcontrol defects -v -PG -f phys (pass2:ncr0:0:0:0): READ DEFECT DATA(10). CDB: 37 0 1d 0 0 0 0 0 0 0 (pass2:ncr0:0:0:0): error code 0 Got 0 defects. # ./camcontrol defects -v -G -f phys (pass2:ncr0:0:0:0): READ DEFECT DATA(10). CDB: 37 0 d 0 0 0 0 0 0 0 (pass2:ncr0:0:0:0): error code 0 Got 0 defects. # ./camcontrol defects -v -P -f phys (pass2:ncr0:0:0:0): READ DEFECT DATA(10). CDB: 37 0 15 0 0 0 0 0 0 0 (pass2:ncr0:0:0:0): error code 0 Got 0 defects. # camcontrol defects -v -P -f phys error reading defect list: Input/output error CAM status is 0 # which camcontrol /sbin/camcontrol # pwd /home/obj/usr/src/sbin/camcontrol # So it appears the new camcontrol helps. And that I found the correct one after rebuilding it. Seems back in RELENG_22 if one simply typed "make" in a directory the obj files didn't get moved elsewhere. > It would also be helpful to see what happens on an Adaptec controller, as > this could be the result of a bug in the NCR driver. I'll see what I can do. At the moment I don't have access to SGI machines like I used to, but I've never seen a grood drive report a null factory bad block list. Mostly the reason to read my bad block list is that I believe it is growing. The drive is supposed to be auto-reassigning and I wanted to find out if it is: (da0:ncr0:0:0:0): READ(10). CDB: 28 0 1 9 b6 2 0 0 2 0 (da0:ncr0:0:0:0): MEDIUM ERROR info:109b603 asc:11,b (da0:ncr0:0:0:0): Unrecovered read error - recommend reassignment sks:80,2f (da0:ncr0:0:0:0): READ(10). CDB: 28 0 0 6a f2 6a 0 0 2 0 (da0:ncr0:0:0:0): MEDIUM ERROR info:6af26b asc:11,b (da0:ncr0:0:0:0): Unrecovered read error - recommend reassignment sks:80,2f (da0:ncr0:0:0:0): READ(10). CDB: 28 0 0 6a f2 6a 0 0 2 0 (da0:ncr0:0:0:0): MEDIUM ERROR info:6af26b asc:11,b (da0:ncr0:0:0:0): Unrecovered read error - recommend reassignment sks:80,2f Of the above, I don't really know what block(s) are the problems. -- 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-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908291906.OAA94336>