From owner-freebsd-questions@FreeBSD.ORG Wed Jul 7 22:22:02 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 1103916A4CE for ; Wed, 7 Jul 2004 22:22:02 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1B6943D48 for ; Wed, 7 Jul 2004 22:22:01 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from working.potentialtech.com (pa-plum-cmts1e-68-68-113-64.pittpa.adelphia.net [68.68.113.64]) by internet.potentialtech.com (Postfix) with ESMTP id 0C5CF69A42; Wed, 7 Jul 2004 18:22:00 -0400 (EDT) Date: Wed, 7 Jul 2004 18:21:59 -0400 From: Bill Moran To: "Hugo Silva" Message-Id: <20040707182159.1cce4bde.wmoran@potentialtech.com> In-Reply-To: <51383.81.84.175.12.1089203326.squirrel@81.84.175.12> References: <51383.81.84.175.12.1089203326.squirrel@81.84.175.12> Organization: Potential Technologies X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: bypass no new partitions protection ? 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: Wed, 07 Jul 2004 22:22:02 -0000 "Hugo Silva" wrote: > Hi all > > In one of my servers I left a 80GB disk unpartitioned to later partitition > it according to my needs, only to have sysinstall always complain it > couldn't write to ad1. I've googled a bit and it seems its related to some > kind of protection that won't allow the system to create any new > partitions while the system is running. You need to cut/paste the _exact_ error message into your question. > Is there any way to bypass this behaviour? a patch? a trick ? I really > need to overcome this but found no way. There should be a way to create > partitions on the 2nd disk, since it's not being used by the system.. I would like to know what patch/trick you used to _create_ this behaviour. I have done exactly what you're describing several times, with never a problem. The default behaviour is to allow you to partition/newfs unused disks in the system. Is your securelevel set high? If so, set it to -1 and reboot the system, then try again. You can't write to disk devices with securelevel at 2 or greater. Other than that, I'm not sure what could be causing the problem. -- Bill Moran Potential Technologies http://www.potentialtech.com