From owner-freebsd-questions@FreeBSD.ORG Wed May 14 00:18:02 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A79B737B401 for ; Wed, 14 May 2003 00:18:02 -0700 (PDT) Received: from babyruth.hotpop.com (babyruth.hotpop.com [204.57.55.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C77A43FB1 for ; Wed, 14 May 2003 00:18:01 -0700 (PDT) (envelope-from teilhk@Phreaker.net) Received: from phreaker.net (kubrick.hotpop.com [204.57.55.16]) by babyruth.hotpop.com (Postfix) with SMTP id 4DE73215EE4 for ; Wed, 14 May 2003 07:17:58 +0000 (UTC) Received: from dsl-200-95-25-87.prodigy.net.mx (dsl-200-95-25-87.prodigy.net.mx [200.95.25.87]) by smtp-2.hotpop.com (Postfix) with ESMTP id A3F171800C4 for ; Wed, 14 May 2003 07:17:57 +0000 (UTC) From: Teilhard Knight To: FreeBSD Content-Type: text/plain Organization: Message-Id: <1052896702.3300.17.camel@arlette.love.dad> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4-1.1mdk Date: 14 May 2003 02:18:22 -0500 Content-Transfer-Encoding: 7bit X-HotPOP: ----------------------------------------------- Sent By HotPOP.com FREE Email Get your FREE POP email at www.HotPOP.com ----------------------------------------------- Subject: About my problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2003 07:18:02 -0000 For those who do not know what I am talking about, this is what is happening to me: I have compiled my kernel. Everything seems to be all right, except that on boot it cannot mount root. It displays: "mounting root from ufs:ad2s2a", and a failure message. Now, I am left at boot with an inquire for a manual root filesystem specification., like this: mount using filesystem eg. ufs:/dev/da0s1a ? List valid disk boot devices abort manual imput mountroot> The HD where FreeBSD is installed is ad2 in my previous kernel and in this new one it is ad1. I have now found out that this is the source of the problem. I checked the partition table, and the slices are called ad2s2a ---> ad2s2g. If this is the case, no way I can mount root on a disk called ad1 with those slices. So, I'll pose a different question. Do you know of a possible way I can make my new kernel to spot my HD as ad2? To me this is the only solution possible. Teilhard Knight The Extraterrestrial Who ate my sandwich?