From owner-freebsd-current@FreeBSD.ORG Tue Oct 12 00:38:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D891E16A4CE for ; Tue, 12 Oct 2004 00:38:28 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F74343D1F for ; Tue, 12 Oct 2004 00:38:28 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id i9C0cRQD018976; Mon, 11 Oct 2004 17:38:28 -0700 (PDT) (envelope-from marcel@xcllnt.net) In-Reply-To: <200410112310.19966.Emanuel.Strobl@gmx.net> References: <200410111101.59356.Emanuel.Strobl@gmx.net> <200410111848.15914.Emanuel.Strobl@gmx.net> <20041011170312.GA16348@ns1.xcllnt.net> <200410112310.19966.Emanuel.Strobl@gmx.net> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <08722E8C-1BE7-11D9-8B43-000D93C47836@xcllnt.net> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Mon, 11 Oct 2004 17:38:27 -0700 To: Emanuel Strobl X-Mailer: Apple Mail (2.619) cc: freebsd-current@freebsd.org Subject: Re: missing ad0p2 device while GEOM sees GPT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2004 00:38:29 -0000 On Oct 11, 2004, at 2:10 PM, Emanuel Strobl wrote: > Am Montag, 11. Oktober 2004 19:03 schrieb Marcel Moolenaar: > [...] >>> But when I try it fails becaus there also is no /dev/ad0p at all. >> >> Odd. I'll see if I can reproduce this. In the mean time, see if md(4) >> exhibits the same behaviour. >> >>> Btw, it's a i386 box, not ia64. >> >> I know. :-) > > Nice :) I have news, please let me know if I'm doing things the right > way. Now > I set up a standard MBR with one standard slice and standard labels > inside. > Then I issued 'gpt migrate -k -s ad0' and now I have a booting box and > could > add ('gpt add -b ??????? -s 2000000 -i 3 -t ufs ad0') a third GPT part > of > type ufs. Ok. No obvious bogons here. > After a reboot I also have the device ad0p3, but why do I need to > reboot? Dunno. AFAICT you don't have to reboot at all because if GEOM allows you to create a new partition/slice, it'll create the device nodes right away. You might want to sync(8) and see if the device node shows up then. We've had some latency/synchronisation issues in the past with mdconfig(8)... > And why doesn't 'gpt show ad0' work without setting > kern.geom.debugflags to > 16? Because gpt(8) opens the device RW by default and this is not allowed by GEOM (by default) when partitions are mounted. You can either give gpt(8) the -r option for opening the disk RO, or tell GEOM to loosen up (which is what the debugflags value does). > And like I posted in another mail, as soon as there is a GPT on the > disk > sysinstall panickes (BARF <171>, panic: Going nowhere without my > init!). I saw the mail, but did not answer. The problem is libdisk. When it encounters something in the GEOM conftxt sysctl that it doesn't expect it simply barfs (<171> in this case) and bails out. Since sysinstall(8) is the only consumer of this library, sysinstall is the only one affected. There are a lot of bugs in libdisk like that. My advice: don't do it... > And while I'm at sysinstall I'd liek to repeat another posting: > Sysinstall > always sets the boot flag to any slice, so if you add (or define two > at once) > a slice you have a invalid partition tabel (in the MBR) with two active > flags. File a PR? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net