From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 19:48:50 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 B236016A41F for ; Fri, 4 Nov 2005 19:48:50 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BEA043D45 for ; Fri, 4 Nov 2005 19:48:49 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id jA4JmlbG076428; Fri, 4 Nov 2005 13:48:48 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <436BBB1C.1030900@centtech.com> Date: Fri, 04 Nov 2005 13:48:44 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jochen Gensch References: <200511042023.36498.incmc@gmx.de> In-Reply-To: <200511042023.36498.incmc@gmx.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1162/Thu Nov 3 11:15:03 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: Filesystem panic - one hd inaccessable under 6-STABLE 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: Fri, 04 Nov 2005 19:48:50 -0000 Jochen Gensch wrote: > Hi! > > I've encountered a very bad thing here. I was compiling openoffice, when the > system suddenly paniced and rebooted. When it was booting again it said: > > Nov 4 19:53:15 incmc kernel: Trying to mount root from ufs:/dev/ad0s3a > Nov 4 19:53:15 incmc savecore: reboot after panic: ufs_dirbad: bad dir > Nov 4 19:53:15 incmc savecore: writing core to vmcore.0 > > The bad news is, one harddisk, which was attached via firewire lost its > superblock and cannot be used any more. This is my backup drive :-(. A fsck > -t uds /device ends up with: > > fsck -t ufs /dev/da0s1 > ** /dev/da0s1 > Cannot find file system superblock > ioctl (GCINFO): Inappropriate ioctl for device > fsck_ufs: /dev/da0s1: can't read disk label > > both harddrives are running with ufs2 + softupdates > > I'm scared :-( try: fsck -b 160 /dev/da0s1 Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------