From owner-freebsd-questions@FreeBSD.ORG Thu Oct 25 12:48:44 2007 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 338E016A41B for ; Thu, 25 Oct 2007 12:48:44 +0000 (UTC) (envelope-from web@umich.edu) Received: from skycaptain.mr.itd.umich.edu (smtp.mail.umich.edu [141.211.93.160]) by mx1.freebsd.org (Postfix) with ESMTP id E241313C4B8 for ; Thu, 25 Oct 2007 12:48:43 +0000 (UTC) (envelope-from web@umich.edu) Received: FROM dell1 (Unknown [141.211.15.39]) BY skycaptain.mr.itd.umich.edu ID 47208E50.56E23.7812 ; 25 Oct 2007 08:38:40 -0400 Date: Thu, 25 Oct 2007 08:38:41 -0400 From: William Bulley To: questions@freebsd.org Message-ID: <20071025123841.GA73226@dell1> Mail-Followup-To: questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Cc: Subject: boot manager oddity (two IDE drives, two o/s) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Oct 2007 12:48:44 -0000 I have two IDE drives (ad0 and ad1) on a Dell system that is running Windows XP on ad0 and FreeBSD 6.2 on ad1. Drive ad0 is 80 GB. Drive ad1 is 250 GB. When I installed FreeBSD onto ad1, I installed the FreeBSD boot manager onto both ad0 and ad1 disk drives. When the machine powers up from a cold start, I don't see the ad0 boot manager at all. I see the ad1 boot manager. It looks like this. F1 FreeBSD F5 Drive 0 and FreeBSD boots just fine if I select F1. I don't see the ad0 boot manager until I reboot FreeBSD and select F5 from the above "menu". Then I get this: F1 ??? F2 DOS F5 Drive 1 Hitting F5 gives me the expected: F1 FreeBSD F5 Drive 0 But, if I want to boot up Windows, I hit F2, and then Windows starts up. If I shut down Windows (restart), then I again see this: F1 ??? F2 DOS F5 Drive 1 But this time, when I hit F5 nothing happens!?!?!?! Here is the output of two boot0cfg(8) commands: freebsd% boot0cfg -v ad0 # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xde 4:254:63 63 80262 2 0x00 5: 0: 1 0x07 1023:254:63 80325 156151800 version=1.0 drive=0x80 mask=0xf ticks=182 options=nopacket,update,nosetdrv default_selection=F5 (Drive 1) freebsd% boot0cfg -v ad1 # flag start chs type end chs offset size 1 0x80 0: 1: 1 0xa5 1023:254:63 63 524281212 version=1.0 drive=0x81 mask=0xf ticks=182 options=nopacket,update,nosetdrv default_selection=F1 (Slice 1) What I want to know is am I doing something wrong, or, am I not doing enough to configure (using the boot0cfg(8) command) the two boot managers (one on each drive)? BTW, the "???" slice above is the Windows recovery (or diagnostic?) slice, I believe. I have looked in the Handbook to no avail. Any ideas? Help! Regards, web... -- William Bulley Email: web@umich.edu