From owner-freebsd-current Mon Nov 16 08:49:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00200 for freebsd-current-outgoing; Mon, 16 Nov 1998 08:49:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00195 for ; Mon, 16 Nov 1998 08:49:02 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id IAA09980; Mon, 16 Nov 1998 08:48:21 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 16 Nov 1998 08:48:21 -0800 (PST) From: Doug White To: Jeroen Ruigrok van der Werven cc: current@FreeBSD.ORG Subject: Re: Ick, Help! Booting problem? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Nov 1998, Jeroen Ruigrok van der Werven wrote: > when I woke up this morning I wanted to dial in to my ISP to get my > mail. So I had ppp running in one window and just did a dial ISP. > Nothing happened. I looked at all the connectors, nothing weird. So I > 'quit'ted ppp and then started it again. Curiously enough I mentioned > that not enough inodes were available. > > This has never happened before, so I thought (Windows 95 thinking, I > admit), well let's reboot the sucker then. OK, it all detected the > devices and other things again, but at the point where it was supposed > to come up with the login: prompt, I got /stand/sysinstall. The system will fault over to sysinstall if init is corrupted or missing. It sounds like your disk crashed. > OK, I thought, could be a glitch in CURRENT, so I tried rebooting with > -s and that got me the same /stand/sysinstall! Also when I tried to > 'Exit Install' I never got to rebooting, it just caught a lot of SIG > 11's. .. or one of your SIMMs fried. > Could I use a bootdisk to get to my partitions? But even if I do, I > have no idea where the problem might lie... You'll have to reinstall to get init back. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message