From owner-freebsd-current Mon Nov 16 12:13:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03005 for freebsd-current-outgoing; Mon, 16 Nov 1998 12:13:33 -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 MAA02984 for ; Mon, 16 Nov 1998 12:13:30 -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 MAA22314; Mon, 16 Nov 1998 12:12:21 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 16 Nov 1998 12:12:20 -0800 (PST) From: Doug White To: Jeroen Ruigrok/Asmodai cc: current@FreeBSD.ORG, Jeroen Ruigrok van der Werven 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 Mon, 16 Nov 1998, Jeroen Ruigrok/Asmodai wrote: > On 16-Nov-98 Doug White wrote: > > On Sat, 14 Nov 1998, Jeroen Ruigrok van der Werven wrote: > >> 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. > > After using a disk/holographic shell I tried to ls /sbin/init and it gave me an > error I cannot remember. > > > It sounds like your disk crashed. > > Yeah, wonder how/why though... I also verify media/low level format before > using them, brand new disk too... Sounds like an initial failure .. warranty replacement. 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