From owner-freebsd-current@FreeBSD.ORG Thu Jan 3 23:24:46 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 309CBE63 for ; Thu, 3 Jan 2013 23:24:46 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id DEFEFD7E for ; Thu, 3 Jan 2013 23:24:45 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 03 Jan 2013 18:24:39 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr16.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id CEA51393; Thu, 3 Jan 2013 18:24:38 -0500 Received-SPF: None identity=pra; client-ip=209.6.85.139; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="roberthuff@rcn.com"; x-conformance=sidf_compatible Received-SPF: Neutral identity=mailfrom; client-ip=209.6.85.139; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="roberthuff@rcn.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None identity=helo; client-ip=209.6.85.139; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="postmaster@[192.168.1.101]"; x-conformance=sidf_compatible X-Auth-ID: roberthuff Received: from 209-6-85-139.c3-0.smr-ubr2.sbo-smr.ma.cable.rcn.com (HELO [192.168.1.101]) ([209.6.85.139]) by smtp01.lnh.mail.rcn.net with ESMTP; 03 Jan 2013 18:24:38 -0500 Message-ID: <50E612DA.8020704@rcn.com> Date: Thu, 03 Jan 2013 18:23:06 -0500 From: Robert Huff User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Warren Block Subject: Re: problem after installkernel going from 9.0 to CURRENT References: <50E0BFA0.6070702@rcn.com> <50E476D3.2030609@rcn.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Junkmail-Whitelist: YES (by domain whitelist at mr16.lnh.mail.rcn.net) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 03 Jan 2013 23:24:46 -0000 On 1/3/2013 11:40 AM, Warren Block wrote: > On Wed, 2 Jan 2013, Robert Huff wrote: > >> (While this may not be a strictly CURRENT issue, I asked on >> questions@, but have not found a solution.) >> >> Situation: >> One of my boxes failed, and for various reasons it became easier >> to just scrub and rebuild it. Like its predecessor it will run CURRENT >> 1) Using BSDinstall, I flushed then created the first disk: >> >> ada2p1 freebsd-boot 128k >> ada2p2 freebsd-swap 4g >> ada2p3 freebsd-ufs 25g >> >> 5) On rebooting, the loader(??) claims to not be able to find a >> bootable partition - i.e. I get a screen that ends in "mountroot > ". >> Providing the presumptive value by hand returns "error 19". > > It really does not sound like a GPT problem, because 9.0 booted. I don't (at the moment) think it's GPT caused; but I do think it may be GPT related. > The > -current kernel can't find/detect the device. Scrolling back in the > console buffer might find a problem. buildworld/kernel/installworld do > not affect the disk partitioning, but can change the code that looks for > those partitions. Exactly. I'm looking for help figuring out how the hand-off from loader to kernel got broken and what I have to do to fix it. One possibility: I believe I labeled each of the partitions during the gpt creation process. Can I use those labels to (hopefully) by-pass this issue? Robert Huff