From owner-freebsd-hackers Fri Oct 23 23:29:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA20623 for freebsd-hackers-outgoing; Fri, 23 Oct 1998 23:29:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA20618 for ; Fri, 23 Oct 1998 23:29:46 -0700 (PDT) (envelope-from ab@paert.tse-online.de) Received: (qmail 19281 invoked by uid 1000); 24 Oct 1998 06:31:40 -0000 Message-ID: <19981024083139.H365@paert.tse-online.de> Date: Sat, 24 Oct 1998 08:31:39 +0200 From: Andreas Braukmann To: "Kenneth D. Merry" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bad sectors Mail-Followup-To: "Kenneth D. Merry" , freebsd-hackers@freebsd.org References: <19981022233738.J1126@paert.tse-online.de> <199810222310.RAA19256@panzer.plutotech.com> <19981023073056.E365@paert.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <19981023073056.E365@paert.tse-online.de>; from Andreas Braukmann on Fri, Oct 23, 1998 at 07:30:56AM +0200 Organization: TSE TeleService GmbH Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, ... I have to admit, that I've simply forgotten to peek into /var/log/messages (the console is 600m away from me). And there are the error messages: Oct 23 07:32:04 paert /kernel: (pass1:ncr0:0:1:0): extraneous data discarded. Oct 23 07:32:05 paert /kernel: (pass1:ncr0:0:1:0): COMMAND FAILED (9 0) @0xf0e88200. -ab On Fri, Oct 23, 1998 at 07:30:56AM +0200, Andreas Braukmann wrote: > On Thu, Oct 22, 1998 at 05:10:02PM -0600, Kenneth D. Merry wrote: > > Andreas Braukmann wrote... > > > from dmesg: > > > da1 at ncr0 bus 0 target 1 lun 0 > > > da1: Fixed Direct Access SCSI2 device > > > da1: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled > > > da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) > > > > > > any hints? is it my fault? the drive's fault? > > > > Try a different format (the other choices are 'bfi' and 'block'). Some > > drives don't support all of the different formats. > Hmmm. The results: > paert# camcontrol defects -v -n da -u 1 -f block -P > error reading defect list: Input/output error > CAM status is 0 > paert# camcontrol defects -v -n da -u 1 -f phys -P > error reading defect list: Input/output error > CAM status is 0 > paert# camcontrol defects -v -n da -u 1 -f bfi -P > error reading defect list: Input/output error > CAM status is 0 > > IMHO strange. I get the same for '-G'. > > > the command line, you'll get sense information that will tell you why the > > command is failing. > hhm. The i/o ist failing, but camcontrol doesn't print any sense information. > > Two questions arise: > a) Are the IBM drives supposed to deliver the requested error > information? > > b) I might build a kernel with some CAM-debug options. Would this > be helpful. -- /// TSE TeleService GmbH | Gsf: Arne Reuter | /// Hovestrasse 14 | Andreas Braukmann | We do it with /// D-48351 Everswinkel | HRB: 1430, AG WAF | FreeBSD/SMP /// ------------------------------------------------------------------- /// PGP-Key: http://www.tse-online.de/~ab/public-key /// Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message