From owner-freebsd-current Fri Oct 18 10:20:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0211637B401 for ; Fri, 18 Oct 2002 10:20:30 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 2B82D43E65 for ; Fri, 18 Oct 2002 10:20:29 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 46322 invoked by uid 1000); 18 Oct 2002 17:20:29 -0000 Date: Fri, 18 Oct 2002 10:20:29 -0700 (PDT) From: Nate Lawson To: Luigi Rizzo Cc: current@freebsd.org Subject: Re: any recent changes related to MD_ROOT ? In-Reply-To: <20021017183802.A74694@carp.icir.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 17 Oct 2002, Luigi Rizzo wrote: > Hi, > > on a freshly cvsupped source tree, i notice that picobsd images > with a preloaded MD_ROOT cannot boot anymore: the kernel goes up > to this stage: > > Mounting root from ufs:/dev/md0c > setrootbyname failed > ffs_mountroot: can't find rootvp > Root mount failed: 6 > > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:da0s1a > ? List valid disk boot devices > Abort manual input > > mountroot> > > at which point you can proceed by specifying "ufs:md0" as the root > path, and everything works fine. > It certainly used to work (though i do not remember if the root path > came out as md0c or just md0) up to a couple of months ago, roughly. > > Does this ring any bell on what might have changed more or less recently > that affects this ? Who builds up the '/dev/md0c' name for the root > filesystem ? phk@ removed old BSD partition compatibility (md0a,b,c) a while back and then added it in for the devfs case. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message