From owner-freebsd-fs@FreeBSD.ORG Fri Jul 22 04:39:16 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8322A1065670 for ; Fri, 22 Jul 2011 04:39:16 +0000 (UTC) (envelope-from mainland@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 475F48FC14 for ; Fri, 22 Jul 2011 04:39:16 +0000 (UTC) Received: by ywf7 with SMTP id 7so1182133ywf.13 for ; Thu, 21 Jul 2011 21:39:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=lLOO/cMabn8GI0ewypv3x/Oc2PiJbgg5IwMAHOZXx3o=; b=CHDX+SxGDsTLiVs2BDGrHFGKTPN4swkjw6ZWvvzH+8Olzw2y8p5Uv0Px8iWIlgS36i BkUGWOSZNQk78zo+y6yx8iIIUzTk5iPwlINmSKvZFigKHVH7VXb3L7m45wWKldqK8q/W tsZAod7t7IOclQDDwiWttbDSHp6jkvh1zuDVM= Received: by 10.236.75.200 with SMTP id z48mr1432257yhd.518.1311307960347; Thu, 21 Jul 2011 21:12:40 -0700 (PDT) MIME-Version: 1.0 Sender: mainland@gmail.com Received: by 10.231.33.68 with HTTP; Thu, 21 Jul 2011 21:12:20 -0700 (PDT) From: Geoffrey Mainland Date: Fri, 22 Jul 2011 00:12:20 -0400 X-Google-Sender-Auth: VeTa7RRZ5lyAHar8sXf-9O_NqC8 Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Can't get 8.2-STABLE to boot from ZFS v28 with ashift=12 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2011 04:39:16 -0000 I'm trying to get a system up and running with a couple new WD EARS drives on 8.2-STABLE (built July 20, so it has ZFS v28 support). I'd like to be able to boot from a ZFS pool where I've used the gnop trick when creating the pool to make sure ZFS accesses my drive in 4k chunks. Booting from ZFS without using gnop (so ashift=9) works beautifully, but when I use the gnop trick to create the pool (ashfit=12), ZFS booting doesn't work at all. I have a script to build my pool with and without using gnop. Without gnop, I create the pool like this: zpool create $TANK gpt/${DISK0} gpt/${DISK1} With gnop, the pool is created like this: gnop create -S 4096 gpt/${DISK0} gnop create -S 4096 gpt/${DISK1} zpool create $TANK gpt/${DISK0}.nop gpt/${DISK1}.nop zpool export $TANK gnop destroy gpt/${DISK0}.nop gnop destroy gpt/${DISK1}.nop zpool import $TANK Other than this, the pools are set up identically by the script. Without gnop I'm golden. With gnop, on boot I get the spinner and then the computer reboots (it looks like boot0 fails). Any ideas what might be going on? Thanks, Geoff