From owner-freebsd-questions Mon Mar 5 0:55:52 2001 Delivered-To: freebsd-questions@freebsd.org Received: from internet.simplifiedtechnology.com (internet.simplifiedtechnology.com [207.21.31.250]) by hub.freebsd.org (Postfix) with ESMTP id 4DEAF37B718 for ; Mon, 5 Mar 2001 00:55:50 -0800 (PST) (envelope-from GregoryC@stcinc.com) Received: from stcinc.com ([10.2.1.2]) by internet.simplifiedtechnology.com (8.10.2/8.10.2) with ESMTP id f258s2K05324 for ; Mon, 5 Mar 2001 00:54:02 -0800 (PST) Message-ID: <3AA35657.68992FC4@stcinc.com> Date: Mon, 05 Mar 2001 01:03:19 -0800 From: Gregory Carvalho Reply-To: GregoryC@stcinc.com Organization: Simplified Technology Company X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Questions Subject: Bizarre disklabel result Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To get disklabel to function with a Iomega Jax, I had to do the following: # disklabel -R -B /dev/rda2 diskproto disklabel: Mar 4 23:01:22 funk /kernel: da2: cannot find label (no disk label) ioctl DIOCWLABEL: Operation not supported by device Mar 4 23:01:22 funk /kernel: da2s4: cannot find label (no disk label) # disklabel -R -r da2 diskproto # Now newfs functions properly. I repeated the process several times by using dd to clear the Jaz disk. If I didn't use the -R -B line before the -R -r line, the following occurs: # disklabel -R -r da2 diskproto Mar 4 23:00:39 funk /kernel: da2: cannot find label (no disk label) disklabel: No space left on device Mar 4 23:00:39 funk /kernel: da2s4: cannot find label (no disk label) # With this, as I am sure you can imagine, newfs does not function. This behaviour perplexes me, and I hope someone can point to the problem. Please advise, Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message