From owner-freebsd-questions@FreeBSD.ORG Wed Nov 24 16:10:29 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C7D316A4D3 for ; Wed, 24 Nov 2004 16:10:29 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1EE443D54 for ; Wed, 24 Nov 2004 16:10:28 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iAOGAR2f035558; Wed, 24 Nov 2004 10:10:27 -0600 (CST) (envelope-from dan) Date: Wed, 24 Nov 2004 10:10:27 -0600 From: Dan Nelson To: FreeBSD Questions Message-ID: <20041124161027.GC95873@dan.emsphone.com> References: <138bced704112323133d942afc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <138bced704112323133d942afc@mail.gmail.com> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-questions@freebsd.org Subject: Re: ffs_clusteralloc X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 16:10:29 -0000 In the last episode (Nov 24), FreeBSD Questions said: > I have a 5.2 box which I use as a general purpose server in my house. > It has been a very good box up to now. I noticed that it wasn't > responding last night so I took a look at it and there was a message > which read: "panic: ffs_clusteralloc: map mismatch". > > Not thinking much of it other than "Oh an error, oh well ". > I rebooted it. Now it refuses to boot. As soon as the login prompt > appears I receive the same panic and the machine reboots. Chances are your filesystem has an error in it that's not caught by the preliminary fsck, the system boots normally, the background fsck kicks off, the kernel hits the corrupt block and panics, and repeats the loop. Try booting into single-user and run fsck -p, then reboot again and see if the problem's gone. -- Dan Nelson dnelson@allantgroup.com