From owner-freebsd-questions@FreeBSD.ORG Thu Aug 21 15:51:34 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85451106566B for ; Thu, 21 Aug 2008 15:51:34 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from betty.computinginnovations.com (mail.computinginnovations.com [64.81.227.250]) by mx1.freebsd.org (Postfix) with ESMTP id 333CE8FC14 for ; Thu, 21 Aug 2008 15:51:33 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from p28.computinginnovations.com (dhcp-10-20-30-100.computinginnovations.com [10.20.30.100]) (authenticated bits=0) by betty.computinginnovations.com (8.14.2/8.14.2) with ESMTP id m7LFpP1P043727; Thu, 21 Aug 2008 10:51:26 -0500 (CDT) (envelope-from derek@computinginnovations.com) Message-Id: <6.0.0.22.2.20080821105014.02680d28@mail.computinginnovations.com> X-Sender: derek@mail.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Thu, 21 Aug 2008 10:51:18 -0500 To: "Marcel Grandemange" , From: Derek Ragona In-Reply-To: <016001c90391$3e9abf80$bbd03e80$@za.net> References: <016001c90391$3e9abf80$bbd03e80$@za.net> Mime-Version: 1.0 X-Antivirus: avast! (VPS 080821-0, 08/21/2008), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: ClamAV 0.93.3/8061/Wed Aug 20 19:00:17 2008 on betty.computinginnovations.com X-Virus-Status: Clean X-ComputingInnovations-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: m7LFpP1P043727 X-ComputingInnovations-MailScanner: Found to be clean X-ComputingInnovations-MailScanner-From: derek@computinginnovations.com X-Spam-Status: No Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: THE FOLLOWING DISK SECTORS COULD NOT BE READ X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2008 15:51:34 -0000 At 08:24 AM 8/21/2008, Marcel Grandemange wrote: >On a different dilemma, I have a FreeBSD proxy server with what looks like a >failing drive. > >The drive ONLY holds cache so is not critical for system operation however >id still like to try something. > >It seem that no matter how many times I run fsck it still comes up with same >result, is there a way to isolate the bad sectors and use the replacement >ones on drive? Or even just isolate so that I can continue using the drive >for now. > > > >su-2.05b# fsck -y /dev/ad1s1d > >** /dev/ad1s1d > >** Last Mounted on /mnt/cache > >** Phase 1 - Check Blocks and Sizes > > > >CANNOT READ BLK: 15430784 > >UNEXPECTED SOFT UPDATE INCONSISTENCY > > > >CONTINUE? yes > > > >THE FOLLOWING DISK SECTORS COULD NOT BE READ: 15430836, 15430837, 15430838, >1543 0839, 15430840, 15430841, 15430842, >15430843, 15430844, 15430845, 15430846, 1543 >0847, > >** Phase 2 - Check Pathnames > >** Phase 3 - Check Connectivity > >** Phase 4 - Check Reference Counts > >** Phase 5 - Check Cyl groups > >366612 files, 8044663 used, 1423024 free (125376 frags, 162206 blocks, 1.3% >frag mentation) > > > >***** FILE SYSTEM STILL DIRTY ***** > > > >***** PLEASE RERUN FSCK ***** > >su-2.05b# fsck -y /dev/ad1s1d > >** /dev/ad1s1d > >** Last Mounted on /mnt/cache > >** Phase 1 - Check Blocks and Sizes > > > >CANNOT READ BLK: 15430784 > >UNEXPECTED SOFT UPDATE INCONSISTENCY > > > >CONTINUE? yes > > > >THE FOLLOWING DISK SECTORS COULD NOT BE READ: 15430836, 15430837, 15430838, >1543 0839, 15430840, 15430841, 15430842, >15430843, 15430844, 15430845, 15430846, 1543 >0847, > >** Phase 2 - Check Pathnames > >** Phase 3 - Check Connectivity > >** Phase 4 - Check Reference Counts > >** Phase 5 - Check Cyl groups > >366612 files, 8044663 used, 1423024 free (125376 frags, 162206 blocks, 1.3% >frag mentation) > > > >***** FILE SYSTEM STILL DIRTY ***** > > > >***** PLEASE RERUN FSCK ***** Sounds like the media has failed. You can try running diagnostics from the hard drive manufacturer and test the disk, but you likely need to replace it. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.