From owner-freebsd-hackers  Thu Apr 18 07:05:39 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA05949
          for hackers-outgoing; Thu, 18 Apr 1996 07:05:39 -0700 (PDT)
Received: from grapenuts.bellcore.com (grapenuts.bellcore.com [192.4.4.35])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA05940
          for <hackers@FreeBSD.ORG>; Thu, 18 Apr 1996 07:05:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by grapenuts.bellcore.com (8.6.9/8.6.10) with SMTP id KAA13919; Thu, 18 Apr 1996 10:04:11 -0400
Message-Id: <199604181404.KAA13919@grapenuts.bellcore.com>
X-Authentication-Warning: grapenuts.bellcore.com: Host localhost didn't use HELO protocol
From: Andrew Heybey <ath@bellcore.com>
To: Jaye Mathisen <mrcpu@cdsnet.net>
cc: hackers@FreeBSD.ORG
Subject: Re: Putting a valid partition table on a BIG disk? 
In-reply-to: Your message of Wed, 17 Apr 1996 12:41:52 -0700.
             <Pine.NEB.3.92.960417123709.12421U-100000@schizo.cdsnet.net> 
Date: Thu, 18 Apr 1996 10:04:10 -0400
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

  mrcpu> 16GB's.  /stand/sysinstall causes a panic instantly, although
  mrcpu> I'm in the middle of a make world which may correct that.

I have experienced the same sysinstall causes panic problem when
booting the 960323 SNAP with an unlabeled Seagate 9G disk.  I
installed without the big disk, then reconnected it and labelled it.
I was going to send a bug report but tried the boot floppy again and
it worked so I thought I might have seen a one-time glitch.

andrew