From owner-freebsd-questions@FreeBSD.ORG Thu Nov 18 07:25:06 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E66EC16A4D0 for ; Thu, 18 Nov 2004 07:25:06 +0000 (GMT) Received: from mtiwmhc11.worldnet.att.net (mtiwmhc11.worldnet.att.net [204.127.131.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3773F43D48 for ; Thu, 18 Nov 2004 07:25:00 +0000 (GMT) (envelope-from jayobrien@worldnet.att.net) Received: from [192.168.1.6] (dsl093-180-184.sac1.dsl.speakeasy.net[66.93.180.184]) by worldnet.att.net (mtiwmhc11) with ESMTP id <2004111807245511100j7tide> (Authid: jayobrien@att.net); Thu, 18 Nov 2004 07:24:55 +0000 Message-ID: <419C4E43.8060002@att.net> Date: Wed, 17 Nov 2004 23:24:51 -0800 From: Jay O'Brien User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD - questions References: <419AFE36.9010107@att.net> <419B989A.3020002@att.net> In-Reply-To: <419B989A.3020002@att.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: bsdlabel messages? (resolved) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 07:25:07 -0000 I asked about error messages displayed by disklabel; after much on- line searching, I found that several others reported the same problem; I couldn't find that any of the others found a resolution. I've found an answer; it may well be an oversight in bsdlabel and it's MAN file. Example error messages are as follows: partition a: partition extends past end of unit partition b: offset past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities Here's the story for anyone else that may run into the problem. The command 'disklabel ad0' worked fine in 4.10 using disklabel. The same command or 'bsdlabel ad0' doesn't work for me in 5.3 using bsdlabel; instead, I get a "no valid label found" message. Referring to MAN BSDLABEL, I found that it says to use the command 'bsdlabel disk', where "disk represents the disk in question, and may be in the form da0 or /dev/da0." Using the da0 form didn't work, so I arbitrarily tried 'bsdlabel ad0s1a' and got the expected display plus an additional 17 error lines. Had I read farther into MAN BSDLABEL, I would have found the example 'bsdlabel da0s1'. That form provides the expected results, without the extra error lines. Only the argument 'ad1s1' gives the expected results when using 5.3's bsdlabel. Using 'ad1s1a' or 'ad1s1c' returns the expected results and adds troubling additional error lines. Using 'ad0' alone fails. Disklabel, in 4.10, seems more tolerant of user input, displaying the correct report when the disk, slice, or any valid partition is used as the "disk" argument. Bsdlabel, however, works differently. If this issue was created to get this new user to experiment and to Read The Freebsd MANual, it worked. Whew. Jay O'Brien Rio Linda, California, USA