From owner-freebsd-questions@FreeBSD.ORG Fri Jan 2 09:41:04 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 7E35916A4CE for ; Fri, 2 Jan 2004 09:41:04 -0800 (PST) Received: from ns1.tiadon.com (SMTP.tiadon.com [69.27.132.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1330243D45 for ; Fri, 2 Jan 2004 09:41:03 -0800 (PST) (envelope-from kdk@daleco.biz) Received: from daleco.biz ([69.27.131.0]) by ns1.tiadon.com with Microsoft SMTPSVC(6.0.3790.0); Fri, 2 Jan 2004 11:44:17 -0600 Message-ID: <3FF5ACEC.5060308@daleco.biz> Date: Fri, 02 Jan 2004 11:39:56 -0600 From: "Kevin D. Kinsey, DaleCo, S.P." User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031124 X-Accept-Language: en-us, en MIME-Version: 1.0 To: orlandina References: <691642047.20040102194334@bk.ru> In-Reply-To: <691642047.20040102194334@bk.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 02 Jan 2004 17:44:17.0593 (UTC) FILETIME=[0B732A90:01C3D158] cc: freebsd-questions@freebsd.org Subject: Re: Problem with FreeBSD 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: Fri, 02 Jan 2004 17:41:04 -0000 orlandina wrote: >Hello freebsd-questions, > > I have one problem with system. Always after rebooting it says that > file systems was uncorrectly unmounted and i have no way to recovery > system without reinstallation. Can you help with solving this > problem? May be problem is in compatibility with processor (Athlon > 850)? > > > Most likely you have some rather bunged up hard disk partition(s). Please find a man page (on the web if FBSD refuses to boot due to bad unmounts) and check up on "fsck". You will probably have to boot into "single user" mode, using a dumbed down version of /bin/sh (well, not dumbed down, really, but it won't be able to find squat, cause your other partitions won't be available, and therefore neither will your $PATH environment variable) and issue fsck commands followed by mount commands using the full pathname to recover from whatever has happened.... power failure, perhaps? Or as I said, bad HDD??? HTH, Kevin Kinsey