From owner-freebsd-questions@freebsd.org Thu Nov 17 23:21:08 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C03B0C47903 for ; Thu, 17 Nov 2016 23:21:08 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: from mail-it0-f41.google.com (mail-it0-f41.google.com [209.85.214.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9468ABCB for ; Thu, 17 Nov 2016 23:21:08 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: by mail-it0-f41.google.com with SMTP id j191so3109503ita.1 for ; Thu, 17 Nov 2016 15:21:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=V4dPBKqUn2NVcWMZi81QzlXDi3KLif5bb6zc9Pojs2E=; b=EaI4giCfZd5JbtmDoQx4/4JVpgnMBoxU/FyEQ6Pru9wDqbdDOAyYqTq/Qn0WMELp/b qwjqcrAMMQ/pGqrzVhmunsPXojADNgms451Ap4xi/6/fhz4OfjbyB8M30gD1INr6N18u kFpbMX2vSPAiXZVWJVy5Zw0+ldV7b+hgOYTUyAC/8g7hga6dNycTRdMm1wgyPgGfHeiA Yd/6IPqwwP5pROGzqzM107y9OV29MWKI1GlZidFlmtcJ/CX786/YWQtYUQdXWrYyISkn 0YcgXFt/oxR66OjJPzlblc3Pwjbauv4uzXUpqeLcXnPwBr7/Xmv4g/qfjqTt+htrH5nc ZNSQ== X-Gm-Message-State: AKaTC033T9Cz3F7s9FAwbaP3/Klo3Y7nIbnlxjEGilZ0Hcmme7ZnTjPguE7gLV0sYEPPfA== X-Received: by 10.107.169.95 with SMTP id s92mr5589561ioe.65.1479424463958; Thu, 17 Nov 2016 15:14:23 -0800 (PST) Received: from WorkBox.homestead.org (174-30-201-142.mpls.qwest.net. [174.30.201.142]) by smtp.gmail.com with ESMTPSA id o21sm89792itb.6.2016.11.17.15.14.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Nov 2016 15:14:22 -0800 (PST) Received: from localhost (WorkBox.homestead.org [local]) by WorkBox.homestead.org (OpenSMTPD) with ESMTPA id 3089a46e; Thu, 17 Nov 2016 17:14:23 -0600 (CST) References: <07218d20-34a5-171b-f6a8-de3c271733cc@columbus.rr.com> <575baf45-b23d-163f-79b0-213a6ba51c91@columbus.rr.com> <86eg29x1on.fsf@WorkBox.homestead.org> <33eee98a-dbf4-4376-3cee-d4349b11c985@columbus.rr.com> User-agent: mu4e 0.9.16; emacs 25.1.1 From: Brandon J. Wandersee To: Baho Utot Cc: freebsd-questions@freebsd.org Subject: Re: Ok How do I boot this monster? In-reply-to: <33eee98a-dbf4-4376-3cee-d4349b11c985@columbus.rr.com> Date: Thu, 17 Nov 2016 17:14:23 -0600 Message-ID: <86mvgxbsxc.fsf@WorkBox.homestead.org> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 23:21:08 -0000 Baho Utot writes: > On 11/17/16 15:59, Brandon J. Wandersee wrote: >> Baho Utot writes: >> >>> On 11/17/16 14:19, Warren Block wrote: >>>> On Thu, 17 Nov 2016, Baho Utot wrote: >>>> >>>>> Can this also boot the raidz? >>>> No, boot0 is MBR-only. The easiest way I see to do this is to install >>>> gptzfsboot bootcode to the ZFS drives and choose one of them from the >>>> BIOS boot menu. Grub can multi-boot GPT also, although it needs a >>>> small partition of its own. >>> I think the bsdinstall puts that code onto the zfs drives already or am >>> I miss informed? >> I believe it should in its unadulterated state. But then you hacked the >> installer, introducing a new variable. >> >>> Would creating the raidz on MBR partitions be an answer? >> It would be *an* answer, but I'm not sure I would consider it *the* >> answer. It would basically place an expiration date on your new install, >> since it would depend on older hardware to keep functioning. A more >> recent motherboard would not be able to read the drives without legacy >> BIOS support, so you might not be able to just transplant the disks into >> a new machine when the time came. >> >> I would recommend just using gpart(8) to install the correct bootcode >> (/boot/gptzfsboot) as Warren suggested. The trouble, though, is >> that---unless I'm mistaken---that bootcode requires a dedicated >> partition. Configuring the system to boot would require 128k partitions >> to be created at the start of each disk to hold the bootcode, and that >> would mean either manually partitioning the drives (which is the typical >> way of installing to a custom ZFS setup) or writing more code into your >> custom bsdinstall. >> > > Don't read too much into the "hacked bsdinstall version", I ain't that > good. All I did was this..... > > from: > f_eval_catch $funcname gpart "$GPART_ADD_LABEL" \ > zfs$index freebsd-zfs $disk || return $FAILURE > to: > f_eval_catch $funcname gpart "$GPART_ADD_LABEL_WITH_SIZE" \ > zfs$index freebsd-zfs 800Gb $disk || return $FAILURE > > The raidz will boot if I pull the other drives and let it boot with just > the 4 zfs raidz drives so I know it will boot. Just have to get it to > play nice with the other systems (win7 and 10.0) and boot. > > I just need to configure out how to make it boot with the other drives. > Hand holding required. Ah, I see. I must have misread something; I thought FreeBSD wasn't booting at all. As you describe it now, it sounds like the motherboard firmware is defaulting to a particular disk and finding the one bootloader. Which is how it always works, but I judging from earlier responses you might be accustomed to GRUB presenting you with a menu to chain-load systems from. If you have a newer motherboard, the board's firmware might have a hotkey tied to a built-in boot menu you can use without the need for GRUB or something similar. In the case of my five-year-old laptop it's F12. -- :: Brandon J. Wandersee :: brandon.wandersee@gmail.com :: -------------------------------------------------- :: 'The best design is as little design as possible.' :: --- Dieter Rams ----------------------------------