From owner-freebsd-current@FreeBSD.ORG Tue May 11 20:13:57 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 423FF1065673 for ; Tue, 11 May 2010 20:13:57 +0000 (UTC) (envelope-from alexbestms@uni-muenster.de) Received: from SECMAIL.UNI-MUENSTER.DE (SECMAIL.UNI-MUENSTER.DE [128.176.192.141]) by mx1.freebsd.org (Postfix) with ESMTP id C11998FC1C for ; Tue, 11 May 2010 20:13:56 +0000 (UTC) Received: from mail-ew0-f224.google.com (mail-ew0-f224.google.com [209.85.219.224]) by SECMAIL.UNI-MUENSTER.DE (Postfix) with ESMTP id 103DDBF406 for ; Tue, 11 May 2010 22:13:53 +0200 (CEST) Received: by ewy24 with SMTP id 24so1499325ewy.13 for ; Tue, 11 May 2010 13:13:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.102.16.36 with SMTP id 36mr3705546mup.124.1273608832195; Tue, 11 May 2010 13:13:52 -0700 (PDT) Received: by 10.103.167.8 with HTTP; Tue, 11 May 2010 13:13:52 -0700 (PDT) In-Reply-To: <3a142e751003291708nc3e110bjca1789cc807f61a2@mail.gmail.com> References: <3a142e751003291708nc3e110bjca1789cc807f61a2@mail.gmail.com> Date: Tue, 11 May 2010 22:13:52 +0200 Message-ID: From: Alexander Best To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: fsck unable to read disk sectors X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 11 May 2010 20:13:57 -0000 the problem is getting more awkward. if i do `fsck /dev/label/rootfs` fsck complains that it cannot read a specific sector of my hdd as i mentioned before. if i run fsck on the device node directly using `fsck /dev/ada0p3` however, fsck succeeds. what i did was to boot into single user mode with / being mounted read only. for some reason however fsck will check /dev/label/rootfs in write mode, but if i want fsck to check ada0p3 it will only do so in read mode. this looks like something is really broken. right now the only way to get the clean flag set on my hdd is to boot from a livefs cd and then run `fsck /dev/ada0p3` (again: `fsck /dev/label/rootfs` will NOT succeed). this is the output of `glabel status` btw: Name Status Components label/boot N/A ada0p1 gptid/e52df583-e446-11de-bb92-000fb58207c8 N/A ada0p1 label/swap N/A ada0p2 label/rootfs N/A ada0p3 cheers. On Tue, Mar 30, 2010 at 2:08 AM, Paul B Mahol wrote: > On 3/29/10, Alexander Best wrote: >> hi there, >> >> when doing fsck on my / fs i get this error: >> >> "Cannot Read BLK. 471617640" and "The Following Disk Sectors could not be >> read: 471617643". after this message the partition gets marked dirty. >> >> i performed the following steps to verify the problem: >> >> 1) dd if=/dev/ada0 of=/dev/null bs=1m >> 2) fsck / under freebsd 7 >> 3) mount -u -o snapshot /.snap/snapshot1 / && fsck_ffs /.snap/snapshot1 >> >> all three steps showed no problem with that harddrive whatsoever. also >> smartd >> doesn't complain about anything. >> >> i'm running HEAD (r205860) on amd64. >> >> this is the output of `dmesg -a|grep ada0`: >> >> ada0 at ahcich2 bus 0 scbus3 target 0 lun 0 >> ada0: ATA-7 SATA 2.x device >> ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) >> ada0: Command Queueing enabled >> ada0: 238474MB (488395055 512 byte sectors: 16H 63S/T 16383C) > > Last time I tried ahci on dead disk it did not complained at all > (usually I get dead LBA listed on console). > -- Alexander Best