From owner-freebsd-current Tue Jun 30 15:08:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13938 for freebsd-current-outgoing; Tue, 30 Jun 1998 15:08:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13903 for ; Tue, 30 Jun 1998 15:07:56 -0700 (PDT) (envelope-from Kurt@Boolean.Net) Received: from gypsy (mg135-057.ricochet.net [204.179.135.57]) by proxy4.ba.best.com (8.8.8/8.8.BEST) with SMTP id PAA25475; Tue, 30 Jun 1998 15:04:16 -0700 (PDT) Message-Id: <199806302204.PAA25475@proxy4.ba.best.com> X-Sender: boolean@shell17.ba.best.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 30 Jun 1998 14:54:30 -0700 To: Chris Coleman From: "Kurt D. Zeilenga" Subject: Re: System won't boot after Install. Cc: freebsd-current@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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