From owner-freebsd-current@FreeBSD.ORG Wed Jul 16 06:01:06 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A60637B401 for ; Wed, 16 Jul 2003 06:01:06 -0700 (PDT) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7837E43F3F for ; Wed, 16 Jul 2003 06:01:05 -0700 (PDT) (envelope-from anderson@centtech.com) Received: from centtech.com (dhcp-243.centtech.com [204.177.173.243]) by otter3.centtech.com (8.12.3/8.12.3) with ESMTP id h6GD0w56074955; Wed, 16 Jul 2003 08:00:58 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <3F154C78.8020607@centtech.com> Date: Wed, 16 Jul 2003 08:00:40 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Darren Pilgrim References: <20030716051629.39cce343.dmp@bitfreak.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: 'Hard error reading fsbn' in 5.1 but not 5.0? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 13:01:06 -0000 Darren Pilgrim wrote: > Just now, my 120GB western digital, immediately upon the mounting of all > filesystems during startup, made a faint "click", then my screen filled with > errors of the form: > > ad6: hard error reading fsbn -# of -#--# error=10 > > That's not an exact quote, of course, since the messages scrolled by so fast I > couldn't actually read parts of them. Those # signs are in place of large > numbers (most were 12-18 digits). This was in 5.1-R, fresh install, in the > first 15G of the disk, just after having booted into DOS to create some DOS > partitions after the FreeBSD slice. > > I booted back into 5.0, and am presently writing across the entire disk with > this command: > > fdisk -I /dev/ad6 && dd if=/dev/zero of=/dev/ad6s1 bs=1m > > At more than 33 minutes into it at 24+MB/sec, there have been no such errors and > the portion of the disk that was being mounted has already been covered by > zeros. Darren - I've seen this before (actually, on western digital drives) a few times, and I'll tell you it's never good. Each time, I thought "maybe it's a bug somewhere in the OS" because I could rebuild the OS on the drive, and the error would seem to disappear - for awhile. Then the drive would get worse, and rapidly deteriorate into a door stop. I'm not sure if it's software or not, but I would double check your backups and start making plans to swap the drive. Eric -- ------------------------------------------------------------------ Eric Anderson Systems Administrator Centaur Technology Attitudes are contagious, is yours worth catching? ------------------------------------------------------------------