From owner-freebsd-current Mon Nov 16 12:05:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01700 for freebsd-current-outgoing; Mon, 16 Nov 1998 12:05:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01621 for ; Mon, 16 Nov 1998 12:04:45 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.8]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA1E1B; Mon, 16 Nov 1998 20:35:17 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 16 Nov 1998 20:39:42 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Doug White Subject: Re: Ick, Help! Booting problem? Cc: current@FreeBSD.ORG, Jeroen Ruigrok van der Werven Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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... >> 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. Nah... I used to have SIMM problems until I got these new ones which are all tested... besides else I had to have them way sooner... >> 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. That's a conclusion I reached myself ;) Thanks anyway... Conclusion: reinstall minimal system, then make world from latest cvsup sources on one of my slices, plus made new kernel... All working again... --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message