Date: Mon, 7 Jun 2004 10:46:48 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Joan Picanyol <lists-freebsd-current@biaix.org> Cc: "'freebsd-current@freebsd.org'" <freebsd-current@freebsd.org> Subject: Re: Sysinstall & labels/fdisk Message-ID: <20040607104535.T19466@carver.gumbysoft.com> In-Reply-To: <20040607171612.GA86565@grummit.biaix.org> References: <FE045D4D9F7AED4CBFF1B3B813C8533703FFC22D@mail.sandvine.com> <20040607171612.GA86565@grummit.biaix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 7 Jun 2004, Joan Picanyol wrote: > * Alex Hoff <ahoff@sandvine.com> [20040607 16:47]: > > I have run in to an odd problem that on a freebsd 5.2 current system after > > running fdisk and disklabel the initial time on install, i am never allowed > > to do it again. > > > > What I have tried on many different systems, is to run sysinstall, and > > either run fdisk or label. After making a change and trying to write the > > changes, it will fail. Even if you dont make a change, and just try to write > > the current settings to the disk, it will fail. The following error comes up > > "ERROR: Unable to write data to disk ad0" (if also tried different types of > > disk devices - da/aacd). Ktrace shows the error as "errno 1 Operation not > > permitted" > > GEOM won't let you touch MBR/slices/partitions on used devices. For it > to allow footshooting you should set kern.geom.debugflags=16 Be REALLY careful with this! I have a documented case of te device entries getting confused and blowing away the wrong partition. I STRONGLY recommend AGAINST using this flag. Make backups, we are not responsible, etc. etc. etc. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040607104535.T19466>