From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 02:51:04 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 81ED916A4B3 for ; Sun, 21 Sep 2003 02:51:04 -0700 (PDT) Received: from pfepc.post.tele.dk (pfepc.post.tele.dk [193.162.153.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A5C043FF7 for ; Sun, 21 Sep 2003 02:51:03 -0700 (PDT) (envelope-from nicolai@catpipe.net) Received: from 0x50a4509b.boanxx9.adsl-dhcp.tele.dk (0x50a4509b.boanxx9.adsl-dhcp.tele.dk [80.164.80.155]) by pfepc.post.tele.dk (Postfix) with ESMTP id 58921262AA6 for ; Sun, 21 Sep 2003 11:51:01 +0200 (CEST) From: Nicolai Petri Organization: catpipe Systems ApS To: current@freebsd.org Date: Sun, 21 Sep 2003 11:50:41 +0200 User-Agent: KMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309211150.41961.nicolai@catpipe.net> Subject: Unable to newfs/fsck partition on -current because of write failed. 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: Sun, 21 Sep 2003 09:51:04 -0000 I'm running -current from september, 14 on my notebook. After an unclean shutdown (out of batteri) my /var filesystem died horrible. Now when i'm trying to do a fsck I always get "write failed" for a lot of blocks. I saw this error some months ago where I just wiped the fs with newfs. But now even newfs gives me "Write failed". This seems a bit odd because i can easily do a "dd if=/dev/zero of=/dev/ad0s2d" and clear out the label. Any hints ? I'm thinking geom and/or blocksize problems. But that's just a guess. -- Cheers, Nicolai Petri