From nobody@FreeBSD.ORG Sat May 29 09:01:11 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 011B514F8F; Sat, 29 May 1999 09:01:10 -0700 (PDT)
Message-Id: <19990529160110.011B514F8F@hub.freebsd.org>
Date: Sat, 29 May 1999 09:01:10 -0700 (PDT)
From: dalroi@wit401310.student.utwente.nl
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: Boot manager only beeps at selecting bootable FreeBSD-partition
X-Send-Pr-Version: www-1.0

>Number:         11926
>Category:       i386
>Synopsis:       Boot manager only beeps at selecting bootable FreeBSD-partition
>Confidential:   no
>Severity:       critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May 29 09:10:00 PDT 1999
>Closed-Date:    Mon Jun 28 12:48:35 PDT 1999
>Last-Modified:  Mon Jun 28 13:05:16 PDT 1999
>Originator:     Alban Hertroys
>Release:        3.2-RELEASE
>Organization:
>Environment:
not available
>Description:
Boot manager shows:
F1 DOS
F3 FreeBSD
F5 Disk 1

Both options F1 & F5 work, but pressing F3 only does "beep".

When trying to boot this FBSD kernel from my old setup (on Disk 1), it 
can't find a kernel at 0:wd(0,a), 0:wd(1,a), 0:wd(2,a) or 0:wd(3,a). 
Selecting 1:wd(2,a) boots my old FBSD 3.1, as expected.

Hard-disk setup:
/dev/wd0s1    1046728   343448   703280    (DOS partition)
/dev/wd0s3      39647    19044    17432    (FreeBSD-3.2)
After the FBSD partition is my DOS extended partition.

I expect the start of the FBSD-3.2 partition is before cylinder 1024, 
but I'v not found a way of checking, yet.	
>How-To-Repeat:
Just try to boot.
>Fix:


>Release-Note:
>Audit-Trail:

From: Zach Heilig <zach@uffdaonline.net>
To: dalroi@wit401310.student.utwente.nl
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: i386/11926: Boot manager only beeps at selecting bootable FreeBSD-partition
Date: Sat, 29 May 1999 12:07:02 -0500

 On Sat, May 29, 1999 at 09:01:10AM -0700, dalroi@wit401310.student.utwente.nl wrote:
 > I expect the start of the FBSD-3.2 partition is before cylinder 1024, 
 > but I'v not found a way of checking, yet.	
 
 This happened to me when I installed a new disk (intended to be the boot
 disk).  The bios had set the disk to "proper" parameters
 (8912 cylinders/15 heads/63 sectors), and windows used that for writing the
 initial partition table.  I had to change some parameters in the bios, and
 repartition the drive before re-installing everything.
 
 The way to figure out the partition info is:
 
 $ fdisk wd0
 ******* Working on device /dev/rwd0 *******
 parameters extracted from in-core disklabel are:
 cylinders=557 heads=240 sectors/track=63 (15120 blks/cyl)
 
 parameters to be used for BIOS calculations are:
 cylinders=557 heads=240 sectors/track=63 (15120 blks/cyl)
 
 Media sector size is 512
 Warning: BIOS sector numbering starts with sector 1
 Information from DOS bootblock is:
 The data for partition 1 is:
 sysid 11,(DOS or Windows 95 with 32 bit FAT)
     start 63, size 4006737 (1956 Meg), flag 0
 	beg: cyl 0/ sector 1/ head 1;
 	end: cyl 264/ sector 63/ head 239
 The data for partition 2 is:
 sysid 165,(FreeBSD/NetBSD/386BSD)
     start 4006800, size 4415040 (2155 Meg), flag 80 (active)
 	beg: cyl 265/ sector 1/ head 0;
 	end: cyl 556/ sector 63/ head 239
 The data for partition 3 is:
 <UNUSED>
 The data for partition 4 is:
 <UNUSED>
 
 -- 
 Zach Heilig <zach@uffdaonline.net>
 
State-Changed-From-To: open->closed 
State-Changed-By: rnordier 
State-Changed-When: Mon Jun 28 12:48:35 PDT 1999 
State-Changed-Why:  
A beep when selecting a partition indicates one of two problems: 

o  There was an error reading the first-level bootstrap: either 
due to a media error (very unlikely in the case of a hard drive), 
or because the sector is above cylinder 1023 

o  Although the sector was read without error, there is no magic 
number indicating that the sector is bootable: almost certainly 
because the partition table entry was created with the wrong 
geometry 

If this is still an issue, it may be worth re-installing FreeBSD, and 
paying particular attention to the geometry used (which may be set in 
the installtion program, sysinstall).  However, you're welcome to send 
along a copy of your master boot record, if you can't get things 
working, and we can verify what the problem is. 

-- 
Robert Nordier 
>Unformatted:
