From brucek@mustang.bagel.com Sat Mar 20 09:54:40 1999
Return-Path: <brucek@mustang.bagel.com>
Received: from mustang.bagel.com (mustang.bagel.com [199.165.203.196])
	by hub.freebsd.org (Postfix) with ESMTP id 87D1815099
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 20 Mar 1999 09:53:53 -0800 (PST)
	(envelope-from brucek@mustang.bagel.com)
Received: (from brucek@localhost)
	by mustang.bagel.com (8.9.1/8.9.1) id JAA08780;
	Sat, 20 Mar 1999 09:53:40 -0800 (PST)
	(envelope-from brucek)
Message-Id: <199903201753.JAA08780@mustang.bagel.com>
Date: Sat, 20 Mar 1999 09:53:40 -0800 (PST)
From: brucek@bagel.com
Sender: brucek@mustang.bagel.com
Reply-To: brucek@bagel.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: 3.1 boot fails with invalid format
X-Send-Pr-Version: 3.2

>Number:         10694
>Category:       kern
>Synopsis:       3.1 boot fails with invalid format
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Mar 20 10:00:01 PST 1999
>Closed-Date:    Sat Mar 20 14:32:51 PST 1999
>Last-Modified:  Sat Mar 20 14:34:08 PST 1999
>Originator:     Bruce Komito
>Release:        FreeBSD 3.1-RELEASE i386
>Organization:
Sierra Lakes Internet
>Environment:
Pentium or K6 CPU w/AMI Bios, 128mb, Adaptec 1542 or 2940

>Description:

After a virgin install of 3.1, boot fails with message "invalid format".
On the same system, a virgin install of both 2.2.8 and 3.0-971208-SNAP
boots successfully.  Upgrade of 2.2.8 or 3.0-971208-SNAP to 3.1 also fails
with "invalid format" message at boot time.


>How-To-Repeat:

Install 3.1 from ftp.freebsd.org and attempt to boot.

>Fix:
	
	


>Release-Note:
>Audit-Trail:

From: "Daniel C. Sobral" <dcs@newsguy.com>
To: brucek@bagel.com
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/10694: 3.1 boot fails with invalid format
Date: Sun, 21 Mar 1999 03:33:45 +0900

 Exactly how did you perform this "virgin install"? Because the error
 you report indicates you are probably using the old bootblocks...
 
 brucek@bagel.com wrote:
 > 
 > >Number:         10694
 > >Category:       kern
 > >Synopsis:       3.1 boot fails with invalid format
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       medium
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:
 > >Keywords:
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Sat Mar 20 10:00:01 PST 1999
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Bruce Komito
 > >Release:        FreeBSD 3.1-RELEASE i386
 > >Organization:
 > Sierra Lakes Internet
 > >Environment:
 > Pentium or K6 CPU w/AMI Bios, 128mb, Adaptec 1542 or 2940
 > 
 > >Description:
 > 
 > After a virgin install of 3.1, boot fails with message "invalid format".
 > On the same system, a virgin install of both 2.2.8 and 3.0-971208-SNAP
 > boots successfully.  Upgrade of 2.2.8 or 3.0-971208-SNAP to 3.1 also fails
 > with "invalid format" message at boot time.
 > 
 > >How-To-Repeat:
 > 
 > Install 3.1 from ftp.freebsd.org and attempt to boot.
 > 
 > >Fix:
 > 
 > 
 > 
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 > 
 > To Unsubscribe: send mail to majordomo@FreeBSD.org
 > with "unsubscribe freebsd-bugs" in the body of the message
 
 --
 Daniel C. Sobral			(8-DCS)
 dcs@newsguy.com
 dcs@freebsd.org
 
 	"What happened?"
 	"It moved, sir!"
 
 
State-Changed-From-To: open->closed 
State-Changed-By: dcs 
State-Changed-When: Sat Mar 20 14:32:51 PST 1999 
State-Changed-Why:  
User installed 3.1 using 2.2.x disk. 3.1 *must* be installed 
with 3.1 disks. 
>Unformatted:
