From owner-freebsd-current  Mon Nov 25 10:45: 7 2002
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 141CB37B401
	for <current@FreeBSD.ORG>; Mon, 25 Nov 2002 10:45:06 -0800 (PST)
Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 67FBD43EAF
	for <current@FreeBSD.ORG>; Mon, 25 Nov 2002 10:45:05 -0800 (PST)
	(envelope-from archie@dellroad.org)
Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20])
	by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id KAA15157;
	Mon, 25 Nov 2002 10:36:13 -0800 (PST)
Received: from arch20m.dellroad.org (localhost [127.0.0.1])
	by arch20m.dellroad.org (8.12.6/8.12.6) with ESMTP id gAPIa8FF006883;
	Mon, 25 Nov 2002 10:36:08 -0800 (PST)
	(envelope-from archie@arch20m.dellroad.org)
Received: (from archie@localhost)
	by arch20m.dellroad.org (8.12.6/8.12.6/Submit) id gAPIa8CM006882;
	Mon, 25 Nov 2002 10:36:08 -0800 (PST)
From: Archie Cobbs <archie@dellroad.org>
Message-Id: <200211251836.gAPIa8CM006882@arch20m.dellroad.org>
Subject: Re: -current unusable after a crash
In-Reply-To: <200211250959.39594.mi+mx@aldan.algebra.com>
To: Mikhail Teterin <mi+mx@aldan.algebra.com>
Date: Mon, 25 Nov 2002 10:36:08 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL99b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Mikhail Teterin wrote:
> The only way to get my -current system back to normal after a crash is
> to boot into single user and do an explicit ``fsck -p''.
> 
> Otherwise the system will, seemingly, boot fine, but none of the ttyvs
> will accept any input, although tty-switching works fine. Remote
> connections (ssh, telnet) don't bring up the login prompt.

FYI, "me too". Manual fsck after booting single user mode fixed it.

-Archie

__________________________________________________________________________
Archie Cobbs     *     Packet Design     *     http://www.packetdesign.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message