From owner-freebsd-stable@FreeBSD.ORG Tue Dec 15 22:11:11 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 364D2106568D for ; Tue, 15 Dec 2009 22:11:11 +0000 (UTC) (envelope-from freebsd-stable@adam.gs) Received: from mail.adam.gs (mail.adam.gs [76.9.2.116]) by mx1.freebsd.org (Postfix) with ESMTP id 0FA408FC20 for ; Tue, 15 Dec 2009 22:11:10 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by mail.adam.gs (Postfix) with ESMTP id E2FAC3E3B39 for ; Tue, 15 Dec 2009 17:11:09 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Adam Jacob Muller In-Reply-To: <1260805564.2281.86.camel@balrog.2hip.net> Date: Tue, 15 Dec 2009 17:11:09 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <42F3C226-766E-45BA-AB2E-74643B3E8724@adam.gs> References: <2A3A50FE-13F4-4AA7-976E-37354E5736B5@adam.gs> <4B256907.4060805@lazlarlyricon.com> <1260805564.2281.86.camel@balrog.2hip.net> To: Robert Noland X-Authentication: 7ONxL3Xv++PBILH0qQg4bwAZcYbRJ4be+KVtSstgqdLQbsx9kEG+7EKoYMcZ9CdBhwI11VX1Co14cIBEAP77YHVOlWwfzUTORF/ussFFvVNrG6N/MSShTd3Eu4IdflEmJ4V/D025/IaLFQ8+qQ5LQiizvpewDg3r59FQBA58ocQPxWFeMFNvbqf1NQ== Cc: freebsd-stable@freebsd.org, Adam Jacob Muller , Rolf G Nielsen Subject: Re: freebsd / gpt boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 22:11:11 -0000 On Dec 14, 2009, at 10:46 AM, Robert Noland wrote: > On Sun, 2009-12-13 at 23:21 +0100, Rolf G Nielsen wrote: >> Adam Jacob Muller wrote: >>> Hi, >>> I'm trying to setup a system with a very large RAID array (total = ~10TB), I would ideally like to have the system boot directly off that = 10TB array, so i'm trying to get the system setup with GPT but running = into an issue. >>>=20 >>>=20 >>> The initial pre-loader (boot0 I think? -- i'm not sure what this is = called) is unable to find loader at /boot/loader nor can it load = /boot/kernel/kernel >>>=20 >>=20 >> Is the partitioning done correctly (have you created a small boot=20 >> partition, 15 sectors is enough for booting from ufs, but the = tutorials=20 >> I've found deal mainly with booting from zfs and they recommend 128=20= >> sectors to make future bootcode changes easier)? >=20 > You will need to be doing all of this from a current 8-STABLE. One = bug > in dealing with larger zfs raidz volumes was fixed and made it into = 8.0. > Another, which deals with GPT/ZFS and large volumes did not make it = and > only exists in 8-STABLE, iirc. Also, with the gptzfsboot code from > -STABLE, it will request to load /boot/zfsloader by default (and > LOADER_ZFS_SUPPORT is no longer required). >=20 >> gpart add -b 34 -s 128 -t freebsd-boot -i 1 da0 >>=20 >> Have you embedded the correct boot code? >>=20 >> gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 da0 >> (for booting from ufs). >>=20 >> or >>=20 >> gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 >> (for booting from zfs). >>=20 >> You may also need to set it active by >>=20 >> gpart set -a active -i 1 da0 >=20 > The above step is no longer needed on -STABLE, the pmbr will be marked > active when you install bootcode. Robert, Do either of these bugs affect GPT/UFS, which is what I am using here. These bugs are affecting the actual older versions of the tools (IE = using the gpart from an 8.0-pre or earlier could cause issues like = this)? Also, perhaps not coincidentally, booting the FreeBSD memstick image = produces the same error (boot0 can't find loader). -Adam >=20 > robert. >=20 >> And of course, substitute your arrays device node for da0 in my = examples. >>=20 >>> Copying /boot/loader to /loader allows me to enter /loader at the = "boot:" prompt and the loader will load, however, its unable to load the = kernel. >>>=20 >>> If I do an "ls" at the loader prompt I can see boot listed as a = directory (with a "d" before it) >>> Trying to do "ls boot" inexplicably it says "boot: not a directory" >>>=20 >>> re-applying my /boot/loader.conf settings (for some reason = vfs.root.mountfrom=3Dufs:/dev/label/root is required, or else I get a = mountroot>) and then: >>> load /kernel >>> boot >>>=20 >>> does work, and lets the system boot normally and everything is as = expected (/boot is a directory etc). >>>=20 >>> Anyone have any ideas about either of these things (the = vfs.root.mountfrom is minor i guess but i'm curious if they are = related?) >>>=20 >>> Thanks in advance, >>>=20 >>> -Adam >>>=20 >>> _______________________________________________ >>> freebsd-stable@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" >>>=20 >>>=20 >>>=20 >>=20 >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" > --=20 > Robert Noland > FreeBSD >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org"