From owner-freebsd-current@FreeBSD.ORG Thu Aug 18 18:02:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 1DF0916A41F for ; Thu, 18 Aug 2005 18:02:13 +0000 (GMT) (envelope-from crapsh@monkeybrains.net) Received: from mail.monkeybrains.net (mail1.monkeybrains.NET [207.7.142.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id D874543D46 for ; Thu, 18 Aug 2005 18:02:12 +0000 (GMT) (envelope-from crapsh@monkeybrains.net) Received: from [192.168.0.3] (adsl-67-121-155-68.dsl.pltn13.pacbell.net [67.121.155.68]) (authenticated bits=0) by mail.monkeybrains.net (8.13.4/8.13.4) with ESMTP id j7II2Ct5001921 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 18 Aug 2005 11:02:12 -0700 (PDT) (envelope-from crapsh@monkeybrains.net) Message-ID: <4304CD1F.8020907@monkeybrains.net> Date: Thu, 18 Aug 2005 11:02:07 -0700 From: Rudy Rucker User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050426) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on mail.monkeybrains.net X-Virus-Status: Clean Subject: Boot loader messed up - How do I fix? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Aug 2005 18:02:13 -0000 I did a cvsup & made a new kernel & world on August 9th but now I can't boot. This was on my second drive. When I boot, I get this menu: F1: ?? F2: FreeBSD (old, May 31st FreeBSD 6.0 CURRENT) F5: Drive 2 (newer, Aug 9th FreeBSD - CURRENT) F2 works fine. F5 _used_ to go to my other drive and boot FreeBSD just fine. I have updated along the CURRENT branch many times, so I sort of know what I am doing ;) If I edit the fstab file on Drive 1 to mount only points on Drive 2, the boot loader will load the kernel from the first drive, but then everything else works fine on Drive 2. Here are my questions: Why is the boot code on Drive 1 unable to load the kernel on Drive 2? How do I fix my computer to boot the kernel on Disk 2? (Would changing my supfile to grab RELENG_6 resolve this problem? I am trying that right now...) Rudy