From owner-freebsd-questions@FreeBSD.ORG Mon Sep 27 12:33:11 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 D26DF16A4CE for ; Mon, 27 Sep 2004 12:33:11 +0000 (GMT) Received: from mra04.ex.eclipse.net.uk (mra04.ex.eclipse.net.uk [212.104.129.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BE7943D1D for ; Mon, 27 Sep 2004 12:33:11 +0000 (GMT) (envelope-from fun@thingy.apana.org.au) Received: from localhost (localhost.localdomain [127.0.0.1]) by mra04.ex.eclipse.net.uk (Postfix) with ESMTP id 6FD5E133EB0 for ; Mon, 27 Sep 2004 13:27:34 +0100 (BST) Received: from mra04.ex.eclipse.net.uk ([127.0.0.1]) by localhost (mra04.ex.eclipse.net.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 02346-01-10 for ; Mon, 27 Sep 2004 13:27:34 +0100 (BST) Received: from [10.0.0.4] (unknown [81.168.35.151]) by mra04.ex.eclipse.net.uk (Postfix) with ESMTP id D6D7C133F3E for ; Mon, 27 Sep 2004 13:27:32 +0100 (BST) Message-ID: <4158070F.20901@thingy.apana.org.au> Date: Mon, 27 Sep 2004 13:26:55 +0100 From: David Gerard User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by Eclipse VIRUSshield at eclipse.net.uk Subject: Re: Problem with corrupt filesystem-any good log funktion? 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: Mon, 27 Sep 2004 12:33:11 -0000 Fredrik Andersson wrote: > Have problem that the filesystem be corrupt, but don't know why! > Look's that the server restart sometime and after it comes too the line > "Enter full patchname of shell or Return for /bin/sh" > After pushing return I do an fsck too repair the corrupt filesystem. After this all seems working ok again. > Is there any good logging funktion that can get more facts about what can be the problem!?? > The system is 4.9-RELEASE-p5 FreeBSD 4.9-RELEASE-p5 #0 You can check bugs on freebsd.org. I had a similar problem with 5.3 beta 5 - I have an MSDOS disk. fsck went looking for /sbin/fsck_msdos , but the binary is actually called /sbin/fsck_msdosfs . Once I got the system started, doing ln -s /sbin/fsck_msdosfs /sbin/fsck_msdos fixed that one. - d.