From owner-freebsd-bugs  Thu Sep 14 06:57:51 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id GAA11003
          for bugs-outgoing; Thu, 14 Sep 1995 06:57:51 -0700
Received: from vistec.com (luna.vistec.com [194.64.40.71])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id GAA10996
          for <freebsd-bugs@freebsd.org>; Thu, 14 Sep 1995 06:57:48 -0700
Received: by vistec.com (Smail3.1.28.1 #10)
	id m0stEpa-0001IgC; Thu, 14 Sep 95 15:59 MET DST
Message-Id: <m0stEpa-0001IgC@vistec.com>
Date: Thu, 14 Sep 95 15:59 MET DST
To: bde@zeta.org.au
From: Marcus.John@wiesbaden.netsurf.de
Reply-To: Marcus.John@wiesbaden.netsurf.de
Subject: Re: Funny fdisk?
Cc: freebsd-bugs@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
X-Mailer: <WinQVT/Net v3.9>
Sender: bugs-owner@freebsd.org
Precedence: bulk

Bruce Evans wrote:
>Does fdisk report the proper information if you boot from wd0?
Yes.

>`netboot' doesn't initialize the boot parameters for BIOS drives.  This
>makes a difference only if the command to ask the drive for its parameters
>fails (it shouldn't fail for IDE or EIDE drives, but failures have been
>reported).  If both the BIOS parameters and the drive parameters are
>unavailable, then I would expect ufs to fail, but fdisk might work :-).

But it is just the other way round.
fdisk is wrong, but UFS mount correctly and even swapon works without
destroying the disks contents.

Thanks!

Marcus.John@wiesbaden.netsurf.de