From owner-freebsd-questions@FreeBSD.ORG Tue Mar 2 22:58:59 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 0FAEB16A4CE for ; Tue, 2 Mar 2004 22:58:59 -0800 (PST) Received: from ns1.tiadon.com (SMTP.tiadon.com [69.27.132.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8138543D1F for ; Tue, 2 Mar 2004 22:58:58 -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); Wed, 3 Mar 2004 00:59:18 -0600 Message-ID: <4045822E.50003@daleco.biz> Date: Wed, 03 Mar 2004 00:58:54 -0600 From: "Kevin D. Kinsey, DaleCo, S.P." User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040212 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Patrick Fish References: <200432205632.047919@patrick> In-Reply-To: <200432205632.047919@patrick> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 03 Mar 2004 06:59:18.0750 (UTC) FILETIME=[0C5717E0:01C400ED] cc: questions@freebsd.org Subject: Re: FreeBSD 4.9 rebooting into single user mode 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, 03 Mar 2004 06:58:59 -0000 Patrick Fish wrote: >Hi, > >I just applied the FreeBSD-SA-04:04.tcp patch onto my 4.9-STABLE box and rebooted. > >On more than one occasion FreeBSD boots into single user mode and awaits for someone to enter the default shell path. This becomes a problem since the server is remote - is there a way to not have it boot into single user mode after we recompile the kernel? > > >(please reply to all, i'm not on this list) > > > > >TIA, >Patrick Fish > > > I would suggest that something is wrong. FreeBSD generally doesn't boot into single user mode unless it's either told to, or has to. The most likely probable cause is a bad HDD*, but there may be other possibilities. What happens after someone does enter the default shell path? Does another reboot cure the problem? What console messages (if any, but there should be some) appear to be abnormal prior to the boot prompt? Kevin Kinsey DaleCo, S.P. More specifically, bad sectors or whatnot; anything requiring a fsck....