From owner-freebsd-current Tue Jun 30 15:13:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15076 for freebsd-current-outgoing; Tue, 30 Jun 1998 15:13:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bb.cc.wa.us (chris@bb.cc.wa.us [134.39.181.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15042 for ; Tue, 30 Jun 1998 15:12:56 -0700 (PDT) (envelope-from chris@bb.cc.wa.us) Received: from localhost (chris@localhost) by bb.cc.wa.us (8.8.8/8.6.9) with SMTP id WAA15923; Tue, 30 Jun 1998 22:07:51 GMT Date: Tue, 30 Jun 1998 15:07:50 -0700 (PDT) From: Chris Coleman To: "Kurt D. Zeilenga" cc: freebsd-current@FreeBSD.ORG Subject: Re: System won't boot after Install. In-Reply-To: <199806302204.PAA25475@proxy4.ba.best.com> 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 Well, its on sd0. :-( Now what? Christopher J. Coleman (whyareyou@lookingforme.com) Computer Support Analyst I (509)-762-6341 FreeBSD Book Project: http://www.vmunix.com/fbsd-book/ On Tue, 30 Jun 1998, Kurt D. Zeilenga wrote: > Chris, > > Is the root on sd0 (target 0)? I had a problem a few months ago booting FreeBSD > when the root was on sd1 (target 1). The panic I got was "cannot mount root" > or something. To get to work, I had to remove the primary drive (target 0), > build a kernel that hardcoded sd0 to be target 1 and sd1 to 0, then reinstalling > the primary drive. I still run this way today. > > Check out bug kern/6505 for details. A search in -current and/or -bugs > for "cannot mount root" or "zeilenga" would probably locate my postings. > > Regards, Kurt > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message