From owner-freebsd-questions Thu Jun 7 9:46:49 2001 Delivered-To: freebsd-questions@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-questions@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-questions" in the body of the message