From owner-freebsd-stable@FreeBSD.ORG Thu Jul 31 01:39:40 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3651BE70 for ; Thu, 31 Jul 2014 01:39:40 +0000 (UTC) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anubis.delphij.net", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B4C62098 for ; Thu, 31 Jul 2014 01:39:40 +0000 (UTC) Received: from zeta.ixsystems.com (unknown [69.198.165.132]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by anubis.delphij.net (Postfix) with ESMTPSA id 68E42A654; Wed, 30 Jul 2014 18:39:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphij.net; s=anubis; t=1406770779; x=1406785179; bh=0bp57e9xW30xV4ADHsMFYk0h5x98e9xcvdL+0lFo8i8=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To; b=0xw2SNujNyxaaAnoNjJNtRJgZUfeEy5sg8HDfvDNTjkclBOlVyKfh3bcRJ28RR68T TmqwS01Mw+pYSmxrJVDaQFu3qEsXvDRLCHlOLPoFERzH41px9qfuYC/mMo/iwkb/Mk ev1pucXskid2RVhazQY5A8PE7RNRZlMWWRq2wfyQ= Message-ID: <53D99E5A.10702@delphij.net> Date: Wed, 30 Jul 2014 18:39:38 -0700 From: Xin Li Reply-To: d@delphij.net Organization: The FreeBSD Project MIME-Version: 1.0 To: Michael Jung , "freebsd-stable@freebsd.org" Subject: Re: r269147 fails to boot after ZFS pool upgrade and new boot code installation References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2014 01:39:40 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 07/29/14 07:04, Michael Jung wrote: > Everyone, > > The freebsd-fs was silent about this post so I'm hoping someone > will chime in here. > > 10-stable r269147: Upgraded the zfs pool to 5000 and installed new > bootcode. The system was working fine prior to upgrading the pool. > > NOTE: Due to the BIOS not supporting drives > 2TB in ACHI mode > this MB is running in legacy IDE mode. I understand the speed > implications of this - it is just a test box. > > ZFS MIRROR BOOT ada0/ada1 > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad0 gpart > bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad1 > > Loading Operating System ... ZFS: i/o error - all block copies > unavailable ZFS: can't read object set for dataset u ZFS: can't > open root filesystem gptzsboot: failed to mount default pool zroot > > FreBSD/x86 boot Default zroot: boot: > > I tried to recover using > > FreeBSD-Stable USB Live CD r268571 but could not import the pool. The feature was merged in r268649 so this is expected. > FreeBSD-11-Current r268622 LIVE CD (USB) imports the pool fine. > > Only two mirrored drives attached to onboard SATA. Both drives > show up in = BIOS as first two boot devices. > > I attempted to install the r269147 bootcode again like: > > # zpool import -f -N zroot # mkdir /tmp/zroot # mount -r -t zfs > zroot/ROOT/default /tmp/zroot # gpart bootcode -b > /tmp/zroot/boot/pmbr -p /tmp/zroot/boot/gptzfsboot -i 1= ada0 # > gpart bootcode -b /tmp/zroot/boot/pmbr -p > /tmp/zroot/boot/gptzfsboot -i 1= ada1 > > > but resulted in same problem. I also tried installing 11-current > bootcode = r268622 which also fails to boot. > > (I did not export the pool. I even tried power reset after writing > bootcod= e) This shouldn't matter. > gpart list/show: > > > 34 5860533101 ada0 GPT (2.7T) > > 34 6 - free - (3.0K) > > 40 1024 1 freebsd-boot (512K) > > 1064 25165824 2 freebsd-swap (12G) > > 25166888 5835366240 3 freebsd-zfs (2.7T) > > 5860533128 7 - free - (3.5K) Just a wild guess -- how much space have you used in the pool? And what's the exact BIOS limitation on 2TB drives? I'm asking because the gptzfsboot stage, there is no driver present and the system still rely on BIOS's functionality to do disk access. If the data is located outside BIOS's reach -- there are some strange ones of them, like 137GB, 2TiB, etc., then the gptzfsboot may not be able to read data from the pool if it has to reach out these portion of disk. Note that it's generally a good idea to use a small, dedicated zfs pool located at the beginning of disk(s) as root pool anyways. Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0 iQIcBAEBCgAGBQJT2Z5aAAoJEJW2GBstM+nsePwP/AhJCWmyVOJwb0hTTtwnKV8O eqJNe2u5NwBns+5kSSCDnYKodgOlq2MXaW5UFswg+Rh6Qiyze/xyj1UBHq+oA5rR YBNgh5XwAxGfdWeSO/26WLtylRjwcnYoqjUpbWauqpvxjxOd7AoAkaXUz6BkIu26 tKhjJnN4kiUdhUsHmWP4A2PU/sRqetWIp/MusgR4+NLVhI6Gw6G+RbRo+YFXPbPO KTKMOJeg+bGX8W4SUMM3MVWKNh8ju37IYo5cqBN1EfYgr3CT/y7uSQes+v3iC8nQ jYsghIp4YMZzh8NDLAPX83cBb6FsXNjd17HmByX+kagOYEDP8/fe7dsuXm0KYTYF dtAeGRuup6Gl2RNyfbo2z/INXgWYUPlT5I4a9b7bohLK2bCm2MQZ/IUER3NYjx2b +BqvCwn7P21V54e+iXbMCdQYyXf0fAkNqVFxsoIjHPxPD9wLPHx7+KF+um0Qrpm5 luGLtV9j4t1xOCyxsGZmndDPKgFfVtnNq/5Ykj+cD2oJhIQc7UZwa2UfahO0NwPb tmkZEtkkwD/H0pRcWx8Os51Adm9anXzbhwXF33HZaaF8sXnsgIgaAv1clwC4gEI5 g1r6mGEN3J2ty49Y7xDqQ3FVwj8VVSZ6PObKhgtWnS05CFI4OPtIyjOlD8FSj4tr BnNsREoSSsQKgGDUzz3J =stUo -----END PGP SIGNATURE-----