From owner-freebsd-questions Wed Jul 1 17:24:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23187 for freebsd-questions-outgoing; Wed, 1 Jul 1998 17:24:53 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from homer.supersex.com (homer.supersex.com [209.5.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23172 for ; Wed, 1 Jul 1998 17:24:46 -0700 (PDT) (envelope-from leo@homer.supersex.com) Received: (from leo@localhost) by homer.supersex.com (8.8.8/8.8.5) id UAA18080; Wed, 1 Jul 1998 20:25:42 -0400 (EDT) Message-ID: <19980701202542.46690@supersex.com> Date: Wed, 1 Jul 1998 20:25:42 -0400 From: Leo Papandreou To: questions@FreeBSD.ORG Subject: bad blocks Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Two questions, actually: (1) Can moving to a different brand of scsi adaptor (2940 to NCR875) and/or OS version (2.1-STABLE to 2.2-STABLE) introduce bad blocks in a device? I've been getting a lot of MEDIUM ERROR messages when accessing a particular set of files. Verifying the disk in bios shows many bad blocks but when trying to remap them the bios eventually gives up with the following message: Reassign block command failed Sense Key=03, ASC=80 ASCQ=00 Something like (cant repeat the message verbatim as the machine is down) ASC=80 also appears in the kernel messages. ------------------------------------------------------------------ (2) since moving from 2.1 to 2.2 I've been seeing repeated de0: receive: ... : alignment error and at least one de0: receive: ... : bad crc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message