From owner-freebsd-stable@FreeBSD.ORG Thu Aug 7 18:43:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 925FB1065684 for ; Thu, 7 Aug 2008 18:43:13 +0000 (UTC) (envelope-from besko@msu.edu) Received: from sys16.mail.msu.edu (sys16.mail.msu.edu [35.9.75.116]) by mx1.freebsd.org (Postfix) with ESMTP id 6E7A98FC19 for ; Thu, 7 Aug 2008 18:43:13 +0000 (UTC) (envelope-from besko@msu.edu) Received: from user-718268.user.msu.edu ([35.10.4.118]) by sys16.mail.msu.edu with esmtpsa (Exim 4.63 #1) (TLSv1:AES256-SHA:256) id 1KRAS8-0003nK-AZ; Thu, 07 Aug 2008 14:43:12 -0400 Message-ID: <489B423F.3050102@msu.edu> Date: Thu, 07 Aug 2008 14:43:11 -0400 From: Lisa Besko User-Agent: Thunderbird 2.0.0.14 (X11/20080613) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4899E3AC.40201@msu.edu> <84dead720808061904v398ff7cdieaeca41ed7a8207e@mail.gmail.com> <489B05D9.7030407@msu.edu> In-Reply-To: <489B05D9.7030407@msu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus: None found by Clam AV Cc: Joseph Koshy Subject: Re: Swapping boot disks and getting mountroot>===SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: besko@msu.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Aug 2008 18:43:13 -0000 I got thinks working by commenting out options ATA_STATIC_ID # Static device numbering in the kernel. I had to build a test kernel as described in /usr/src/UPDATING. I still got my mountroot> prompt but for a change is showed me some possible devices. I was able to ad0s1a to boot from. I rebooted to my working kernel and edited /etc/fstab to use ad0. Then booted my test kernel again. The system booted. I installed the kernel w/o ATA_STATIC_ID and was able to boot in my Sunfire X2100 and my X2200. LB Lisa Besko wrote: > > > Joseph Koshy wrote: >>> I notice that it finds the device ad4 but then it tries to mount root >>> from >>> /dev/ad6s1a. I've edited the fstab to have it look for ad4s1a but it >>> still >>> won't boot. Anyone have any pointers or ideas? >> >> Have you tried interrupting the boot sequence and setting new >> values for the `rootdev' and `root_disk_unit' loader variables? >> The loader(8) manual page has more information. > > No I haven't tried that yet. Will that get me to a point where I can > trust it to boot on it's own to the correct disk all the time? > > LB -- Lisa Besko