Date: Fri, 16 Jun 1995 07:00:02 -0700 From: cstruble@vt.edu To: freebsd-bugs Subject: bin/523: disklabel -B too anal Message-ID: <199506161400.HAA15364@freefall.cdrom.com> In-Reply-To: Your message of Fri, 16 Jun 1995 09:54:57 -0400 <199506161354.JAA07513@singularity.bevc.blacksburg.va.us>
next in thread | previous in thread | raw e-mail | index | archive | help
>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: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 16 07:00:01 1995 >Originator: Craig Struble >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/ | >Release: FreeBSD 2.0-BUILT-19950603 i386 >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. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506161400.HAA15364>