From cstruble@singularity.bevc.blacksburg.va.us  Fri Jun 16 06:54:46 1995
Received: from singularity.bevc.blacksburg.va.us (root@singularity.bevc.blacksburg.va.us [198.82.204.56])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA15024
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 16 Jun 1995 06:54:44 -0700
Received: (from cstruble@localhost) by singularity.bevc.blacksburg.va.us (8.6.11/8.6.9) id JAA07513; Fri, 16 Jun 1995 09:54:57 -0400
Message-Id: <199506161354.JAA07513@singularity.bevc.blacksburg.va.us>
Date: Fri, 16 Jun 1995 09:54:57 -0400
From: cstruble@vt.edu
Reply-To: cstruble@vt.edu
To: FreeBSD-gnats-submit@freebsd.org
Subject: disklabel -B too anal
X-Send-Pr-Version: 3.2

>Number:         523
>Category:       bin
>Synopsis:       disklabel -B anal about writing boot blocks
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 16 07:00:01 1995
>Closed-Date:    Fri Jun 16 22:22:39 MET DST 1995
>Last-Modified:
>Originator:     Craig Struble
>Release:        FreeBSD 2.0-BUILT-19950603 i386
>Organization:
Craig Struble - Grad Student, Consultant, |
Student ACM Co-President, Virginia Tech   | The space reserved for more 
Email - cstruble@vt.edu                   | obfuscation.
URL   - http://acm.vt.edu/~cstruble/      |
>Environment:

	FreeBSD 2.0.5 installed on SCSI drive. The system has 2 SCSI drives and
    1 IDE drive.

>Description:

	disklabel -B won't install boot blocks if it finds trouble in the
	disk label. Not a bad thing, except that the label installed on the
	drive has a superblock size of 0. The disk label was installed with
	sysinstall.

>How-To-Repeat:

	Install FreeBSD onto a SCSI drive on a system with an IDE drive.
	Try updating your bootblocks with disklabel -B

>Fix:
	
	One way of getting around the problem is to comment out the check of
	the disk label when only writing boot blocks. However, this probably
	isn't the safest thing to do. It looks like either sysinstall needs
	to correct the disk label it writes, or disklabel -B shouldn't be
	so anal about how it checks the disk label.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: joerg 
State-Changed-When: Fri Jun 16 22:22:39 MET DST 1995 
State-Changed-Why:  
Duplicate for i386/251 
>Unformatted:



