From owner-freebsd-current Wed Feb 12 12:34:16 2003 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 90A3137B401 for ; Wed, 12 Feb 2003 12:34:15 -0800 (PST) Received: from mail.gmx.net (imap.gmx.net [213.165.65.60]) by mx1.FreeBSD.org (Postfix) with SMTP id 40CD043FA3 for ; Wed, 12 Feb 2003 12:34:14 -0800 (PST) (envelope-from capm@gmx.net) Received: (qmail 17105 invoked by uid 0); 12 Feb 2003 20:34:07 -0000 Received: from xdsl-195-14-206-165.netcologne.de (HELO gmx.net) (195.14.206.165) by mail.gmx.net (mp006-rz3) with SMTP; 12 Feb 2003 20:34:07 -0000 Message-ID: <3E4AAFB7.2030700@gmx.net> Date: Wed, 12 Feb 2003 21:33:59 +0100 From: Pascal Giannakakis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: de, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: shutdown / reboot causes filesystem-errors Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG LO, after I cvsupped the system to the most recent version, I found out what the reason of locking during boot was (at least for me): corrupt FS. It seems like a shutdown / reboot leaves the filesystem dirty, which means to get the server up I need to run fsck from the fixit-image. As usual this problem is somewhat beyond my knowledge, so i hope somebody can tell me a) how to pinpoint the exact problem and b) fix it. Another thing that I have been struggeling for ages is how to make the kernel boot verbose. Neither "boot -v" nor setting the variable or entry in /boot/loader.conf works. The syslog does not reveal any information. What's the deal? TIA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message