"Hugo Silva" <[EMAIL PROTECTED]> 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 _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
