From owner-freebsd-scsi Mon Jun 4 13:50: 7 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id E65EE37B405; Mon, 4 Jun 2001 13:50:01 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f54Ko0U97864; Mon, 4 Jun 2001 14:50:00 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200106042050.f54Ko0U97864@aslan.scsiguy.com> To: Mike Smith Cc: Chris Dillon , freebsd-scsi@FreeBSD.ORG Subject: Re: Mylex controllers? In-Reply-To: Your message of "Wed, 30 May 2001 14:22:17 PDT." <200105302122.f4ULMHR02253@mass.dis.org> Date: Mon, 04 Jun 2001 14:50:00 -0600 From: "Justin T. Gibbs" 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, 30 May 2001, Mike Smith wrote: >> >> > The controller isn't the problem, it's CAM. You could try this patch: Can you be a bit more descriptive? Not having one of these controllers or an affected enclosure makes it difficult to reproduce this here or provide a fix. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jun 4 14: 5:55 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id EFF7837B401 for ; Mon, 4 Jun 2001 14:05:46 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f54LFHL03876; Mon, 4 Jun 2001 14:15:17 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106042115.f54LFHL03876@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Justin T. Gibbs" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Mylex controllers? In-reply-to: Your message of "Mon, 04 Jun 2001 14:50:00 MDT." <200106042050.f54Ko0U97864@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Jun 2001 14:15:16 -0700 From: Mike Smith 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, 30 May 2001, Mike Smith wrote: > >> > >> > The controller isn't the problem, it's CAM. You could try this patch: > > Can you be a bit more descriptive? Not having one of these controllers > or an affected enclosure makes it difficult to reproduce this here or > provide a fix. At this point in time, I don't know; I just suspect that CAM and the controller are fighting it out over the enclosure manager. I should probably be more specific here; the adapter *really* ought to tell the driver about enclosures that it's talking to, so that it can mask them out and make them invisible. All the solutions I've been trying to come up with at the moment are targetted around detecting this automagically. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jun 6 1: 5:49 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from ex3beimcoims01.cec.be (ex3beimcoims01.cec.eu.int [158.169.131.56]) by hub.freebsd.org (Postfix) with ESMTP id 4516F37B407; Wed, 6 Jun 2001 01:05:42 -0700 (PDT) (envelope-from Konstantinos.Dryllerakis@cec.eu.int) Received: by ex3beimcoims01 with Internet Mail Service (5.5.2650.21) id ; Wed, 6 Jun 2001 10:05:17 +0200 Message-ID: <5D802E6EDA71D411BFA900D0B76DEB1B0247EC92@EX2BEL86MBX02> From: Konstantinos.Dryllerakis@cec.eu.int To: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.org Subject: Help needed: MEDIUM ERRORs for scsi device Date: Wed, 6 Jun 2001 10:03:17 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" 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 Dear All, A few days ago, I started receiving "MEDIUM ERROR"s from my FreeBSD 3.3 machine (HP Netserver less than 1 year old). I have searhed through the archives/FAQs but I could not locate enough information to understand if the drive is dying (and should be replaced immediately) or if this is a situation that you may recover gracefully from. Furthermore, I am having trouble decoding the SCSI errors... I would really appreciate any information/help on the subject. Thanks in advance, Kostis Dryllerakis (kd@belgacom.net) The errors received are the following: -------------- /kernel: (da0:ahc0:0:0:0): READ(10). CDB: 28 0 1 9 20 60 0 0 10 0 /kernel: (da0:ahc0:0:0:0): MEDIUM ERROR info:1092060 asc:11,0 /kernel: (da0:ahc0:0:0:0): Unrecovered read error sks:80,35 /kernel: (da0:ahc0:0:0:0): READ(10). CDB: 28 0 1 1 a9 10 0 0 4 0 /kernel: (da0:ahc0:0:0:0): MEDIUM ERROR info:101a912 asc:11,0 /kernel: (da0:ahc0:0:0:0): Unrecovered read error sks:80,35 -------------- Hardware is: -------------- ahc0: rev 0x04 int a irq 10 on pci0.5.0 ahc0: Using left over BIOS settings ahc0: aic7895 Wide Channel A, SCSI Id=7,16/255 SCBs da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8678MB (17773524 512 byte sectors: 64H 32S/T 8678C) --------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jun 6 19:31:18 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 8628637B406; Wed, 6 Jun 2001 19:31:01 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA32465; Wed, 6 Jun 2001 20:30:52 -0600 (MDT) (envelope-from ken) Date: Wed, 6 Jun 2001 20:30:52 -0600 From: "Kenneth D. Merry" To: Konstantinos.Dryllerakis@cec.eu.int Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Help needed: MEDIUM ERRORs for scsi device Message-ID: <20010606203052.A32387@panzer.kdm.org> References: <5D802E6EDA71D411BFA900D0B76DEB1B0247EC92@EX2BEL86MBX02> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <5D802E6EDA71D411BFA900D0B76DEB1B0247EC92@EX2BEL86MBX02>; from Konstantinos.Dryllerakis@cec.eu.int on Wed, Jun 06, 2001 at 10:03:17AM +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 Wed, Jun 06, 2001 at 10:03:17 +0200, Konstantinos.Dryllerakis@cec.eu.int wrote: > Dear All, > > A few days ago, I started receiving "MEDIUM ERROR"s from my FreeBSD 3.3 > machine (HP Netserver less than 1 year old). I have searhed through the > archives/FAQs but I could not locate enough information to understand if the > drive is dying (and should be replaced immediately) or if this is a > situation that you may recover gracefully from. Furthermore, I am having > trouble decoding the SCSI errors... > > I would really appreciate any information/help on the subject. > > Thanks in advance, > > Kostis Dryllerakis (kd@belgacom.net) > > > The errors received are the following: > -------------- > /kernel: (da0:ahc0:0:0:0): READ(10). CDB: 28 0 1 9 20 60 0 0 10 0 > /kernel: (da0:ahc0:0:0:0): MEDIUM ERROR info:1092060 asc:11,0 > /kernel: (da0:ahc0:0:0:0): Unrecovered read error sks:80,35 > /kernel: (da0:ahc0:0:0:0): READ(10). CDB: 28 0 1 1 a9 10 0 0 4 0 > /kernel: (da0:ahc0:0:0:0): MEDIUM ERROR info:101a912 asc:11,0 > /kernel: (da0:ahc0:0:0:0): Unrecovered read error sks:80,35 > -------------- This means that you've got at least two bad blocks. The first thing to do is make sure you've got auto read and write reallocation turned on. To check it, type: camcontrol modepage -n da -u 0 -m 1 -P 3 If AWRE and/or ARRE are set to 0, type this: camcontrol modepage -n da -u 0 -m 1 -P 3 -e And change the values to 1. That will make sure that if possible, any future bad blocks will be automatically remapped. As for your current bad blocks, there are a couple of ways to handle them. One way to deal with it would be to write zeros to those two bad blocks. It will corrupt whatever those blocks are a part of, but may save the rest of your data. Another way to handle it is to backup your system, and then write zeros over the entire disk. Anyway, to write zeros to those two bad blocks: camcontrol cmd -n da -u 0 -v -c "2a 0 v:i4 0 v:i2 0" 0x1092060 1 -o 512 - < /dev/zero camcontrol cmd -n da -u 0 -v -c "2a 0 v:i4 0 v:i2 0" 0x101a912 1 -o 512 - < /dev/zero I think the hex notation will work as an argument there. If you want to be a little more sure it'll work right, you can do it like this: camcontrol cmd -n da -u 0 -v -c "2a 0 01 09 20 60 0 v:i2 0" 1 -o 512 - < /dev/zero camcontrol cmd -n da -u 0 -v -c "2a 0 01 01 a9 12 0 v:i2 0" 1 -o 512 - < /dev/zero So that might silence the drive about those two blocks. I would keep an eye on the grown defects list, though. To do that: camcontrol defects -n da -u 0 -G -f phys If the grown defects list increases, your drive is probably on its way out. In any event, you should probably make sure you've got good backups of the machine and be prepared to install a new disk. 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 Thu Jun 7 9:46:47 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from jhs.muc.de (jhs.muc.de [193.149.49.84]) by hub.freebsd.org (Postfix) with ESMTP id 6694437B409; Thu, 7 Jun 2001 09:46:34 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: from park.jhs.private (localhost [127.0.0.1]) by jhs.muc.de (8.11.0/8.11.0) with ESMTP id f57087q53342; Thu, 7 Jun 2001 00:08:08 GMT (envelope-from jhs@park.jhs.private) Message-Id: <200106070008.f57087q53342@jhs.muc.de> To: Konstantinos.Dryllerakis@cec.eu.int Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Help needed: MEDIUM ERRORs for scsi device From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Wed, 06 Jun 2001 10:03:17 +0200." <5D802E6EDA71D411BFA900D0B76DEB1B0247EC92@EX2BEL86MBX02> Date: Thu, 07 Jun 2001 02:08:07 +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 Konstantinos.Dryllerakis@cec.eu.int wrote: > A few days ago, I started receiving "MEDIUM ERROR"s from my FreeBSD 3.3 > machine (HP Netserver less than 1 year old). I have searhed through the > archives/FAQs but I could not locate enough information to understand if the > drive is dying (and should be replaced immediately) or if this is a > situation that you may recover gracefully from. Furthermore, I am having > trouble decoding the SCSI errors... > > I would really appreciate any information/help on the subject. > Thanks in advance, > Kostis Dryllerakis (kd@belgacom.net) > > The errors received are the following: > -------------- > /kernel: (da0:ahc0:0:0:0): READ(10). CDB: 28 0 1 9 20 60 0 0 10 0 > /kernel: (da0:ahc0:0:0:0): MEDIUM ERROR info:1092060 asc:11,0 > /kernel: (da0:ahc0:0:0:0): Unrecovered read error sks:80,35 > /kernel: (da0:ahc0:0:0:0): READ(10). CDB: 28 0 1 1 a9 10 0 0 4 0 > /kernel: (da0:ahc0:0:0:0): MEDIUM ERROR info:101a912 asc:11,0 > /kernel: (da0:ahc0:0:0:0): Unrecovered read error sks:80,35 > -------------- FreeBSD comes with Source Code :-)) ... ultimate (if harder to read), fallback documentation :-) I dont have a /usr/src that old, (& my discs are too busy to do a cvs extract), so look on your own /usr/src, but here's an example from 4.1.1: Grep "MEDIUM ERROR" ( Grep is just my little find + grep shell http://bim.bsn.com/~jhs/bin/.csh/Grep ) On a 4.1.1 /usr/src/ tree produces ./sys/cam/scsi/scsi_all.c: "MEDIUM ERROR", ./sys/dev/ata/atapi-all.c: case 0x03: return ("MEDIUM ERROR"); ./sys/i386/isa/wd_cd.c: printf("atapi%d:%d: medium error\n", ata->ctrlr, unit); As you are using a da drive look at /sys/cam/scsi/scsi_all.c const char *scsi_sense_key_text[] = { "NO SENSE", "RECOVERED ERROR", "NOT READY", "MEDIUM ERROR", "HARDWARE FAILURE", "ILLEGAL REQUEST", "UNIT ATTENTION", "DATA PROTECT", "BLANK CHECK", "Vendor Specific", "COPY ABORTED", "ABORTED COMMAND", "EQUAL", "VOLUME OVERFLOW", "MISCOMPARE", "RESERVED" }; [I'm not a FreeBSD SCSI programmer, but] It looks like SCSI error return codes. Definition of meaning of these codes belongs to the SCSI standards, (not FreeBSD, so grab a SCSI manual or SCSI FAQ from newsgroup comp.answers). In your shoes, I'd probably ensure a backup, [optionally buy a spare disc if for a commercial production system, just in case], then do a reformat (can be done from scsi controller bios, or from FreeBSD (on FreeBSD-4.1.1 see EG man camcontrol, but as you have an older 3.3 (not sure if it has CAM) maybe a different command, try `apropos scsi`). After the reformat, the disc will probably be better or dead, either way, a problem resolved. Good Luck ! Julian - Julian Stacey Unix Consultant - Munich Germany http://bim.bsn.com/~jhs/ Ihr Rauchen => mein allergischer Kopfschmerz ! Kau/Schnupftabak probieren ! Like Linux ? Then also look at FreeBSD with its 5000+ packages ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message