From owner-freebsd-questions Fri Feb 18 14:41: 1 2000 Delivered-To: freebsd-questions@freebsd.org Received: from kaon.intercom.com (kaon.intercom.com [198.143.3.30]) by hub.freebsd.org (Postfix) with ESMTP id BCF2737BACA for ; Fri, 18 Feb 2000 14:40:55 -0800 (PST) (envelope-from jason@intercom.com) Received: from [198.143.3.26] (helo=intercom.com) by kaon.intercom.com with esmtp (Exim 3.13 #1) id 12Lw4v-0002Np-00 for freebsd-questions@freebsd.org; Fri, 18 Feb 2000 17:40:49 -0500 Date: Fri, 18 Feb 2000 17:40:49 -0500 (EST) From: "Jason J. Horton" X-Sender: mail@kaon.intercom.com To: freebsd-questions@freebsd.org Subject: Re: problems booting kernel from large drive In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forgot to mention that this is a 3.4-STABLE machine > I have a system with a 27gig IBM EIDE, and when I set up the system, > I only made 2 partitions, / and swapspace. The system has been working > just fine, till I did a "make world" and installed a new kernel. Now when > I boot, I get errors like this: > >> FreeBSD/i386 BOOT > Default: 0:wd(0,a)/kernel > boot: > Disk error 0x1 (lba=0xc21e2f) > Invalid format > > I am assuming I am getting this because I made the drive "dangerously > dedicated". Is there any way to install my new kernel in such a way that > it is loadable? > > Also, if I want to specify an alternate kernel to boot from on startup, > would I make an entry like this in /boot/loader.conf: > boot /kernel.old;/kernel.different > The loader(8) manpage is kinda vague. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message