From owner-freebsd-stable@FreeBSD.ORG Wed Sep 10 23:41:14 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 B82A0FF1 for ; Wed, 10 Sep 2014 23:41:14 +0000 (UTC) Received: from smtp1.multiplay.co.uk (smtp1.multiplay.co.uk [85.236.96.35]) by mx1.freebsd.org (Postfix) with ESMTP id 69C60D1B for ; Wed, 10 Sep 2014 23:41:13 +0000 (UTC) Received: by smtp1.multiplay.co.uk (Postfix, from userid 65534) id CD0C120E7088D; Wed, 10 Sep 2014 23:41:11 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.multiplay.co.uk X-Spam-Level: * X-Spam-Status: No, score=2.0 required=8.0 tests=AWL,BAYES_00,DOS_OE_TO_MX, FSL_HELO_NON_FQDN_1,RDNS_DYNAMIC autolearn=no version=3.3.1 Received: from r2d2 (82-69-141-170.dsl.in-addr.zen.co.uk [82.69.141.170]) by smtp1.multiplay.co.uk (Postfix) with ESMTPS id E37F420E7088B; Wed, 10 Sep 2014 23:41:09 +0000 (UTC) Message-ID: <9F24DD48FBEA46C39F98DF600D46DA1A@multiplay.co.uk> From: "Steven Hartland" To: "Steven Hartland" , "Kimmo Paasiala" References: <51AD1F36-1089-481F-8784-8BD8E6EF020F@icloud.com> <71DEB316-3CDD-4403-A397-BCE684725ABD@icloud.com> <25886C53-39C1-47A8-95F7-494FA6E7ABA2@icloud.com> <20140819071045.GS2737@kib.kiev.ua> <99FB0662-1954-4ECB-939B-06D0AA49C1A1@icloud.com> <20140819074643.GU2737@kib.kiev.ua> <7F008C560B48412AB66A1EBD9382DDAE@multiplay.co.uk> <9315C209-701A-49EF-85D3-ACCCD1513EC3@icloud.com> <959C54D2C8EB4AC8983DC1DA3CE042E3@multiplay.co.uk> Subject: Re: ZFS on root booting broken somewhere after r270020 Date: Thu, 11 Sep 2014 00:41:17 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 23:41:14 -0000 ----- Original Message ----- From: "Steven Hartland" To: "Kimmo Paasiala" Cc: Sent: Wednesday, September 10, 2014 11:36 PM Subject: Re: ZFS on root booting broken somewhere after r270020 > > ----- Original Message ----- > From: "Kimmo Paasiala" > To: "Steven Hartland" > Cc: > Sent: Wednesday, September 10, 2014 8:26 PM > Subject: Re: ZFS on root booting broken somewhere after r270020 > > >> >>> On 9.9.2014, at 19.03, Kimmo Paasiala wrote: >>> >>> >>>> On 9.9.2014, at 18.53, Steven Hartland wrote: >>>> >>>> ----- Original Message ----- From: "Kimmo Paasiala" >>>>> Hi it’s me again. Something that was committed in stable/10 after r271213 up to >>>>> and including r271288 broke ZFS on Root booting in exactly the same way again. >>>>> I know the problem is no longer related to extra kernel modules loaded in >>>>> /boot/loader.conf because I’m loading only the required zfs.ko and opensolaris.ko >>>>> modules. Also, the new vt(4) console that I’m using is not the culprit because the >>>>> same thing happens with kern.vty set to “sc”. >>>> >>>> I've just updated my stable/10 box to r271316 and no problems booting from a ZFS root. >>>> >>>> So first things first what error are you seeing? >>>> >>>> Next what is you're: >>>> * Hardware >>>> * Pool layout >>>> >>>> Regards >>>> Steve >>> >>> The error is the same as before: >>> >>> • Mounting from zfs:rdnzltank/ROOT/default failed with error 5. >>> >>> Followed by the mountroot prompt and I get only these devices to choose from, no sign of the ZFS pool: >>> >>> • mountroot> >>> • List of GEOM managed disk devices: >>> • gpt/fb10disk1 gpt/fb10swap1 diskid/DISK-S13UJDWS301624p3 diskid/DISK-S13UJDWS301624p2 diskid/DISK-S13UJDWS301624p1 ada0p3 >>> ada0p2 ada0p1 diskid/DISK-S13UJDWS301624 ada0 >>> >>> Hardware is a Gigabyte GA-D510UD Mini-ITX motherboard: >>> >>> http://www.gigabyte.com/products/product-page.aspx?pid=3343#ov >>> >>> 4GBs of RAM. One 750GB Samsung HD753LJ 3.5” SATA HD on the Intel SATA controller. >>> >>> Pool layout: >>> >>> pool: rdnzltank >>> state: ONLINE >>> scan: scrub repaired 0 in 1h7m with 0 errors on Wed Aug 20 09:27:48 2014 >>> config: >>> >>> NAME STATE READ WRITE CKSUM >>> rdnzltank ONLINE 0 0 0 >>> gpt/fb10disk1 ONLINE 0 0 0 >>> >>> errors: No known data errors >>> >>> Output of ‘gpart show’: >>> >>> freebsd10 ~ % gpart show >>> => 34 1465146988 ada0 GPT (699G) >>> 34 2014 - free - (1.0M) >>> 2048 1024 1 freebsd-boot (512K) >>> 3072 1024 - free - (512K) >>> 4096 16777216 2 freebsd-swap (8.0G) >>> 16781312 1448365710 3 freebsd-zfs (691G) >>> >>> >>> HTH, >>> >>> -Kimmo >> >> >> More information. This version still works: >> >> FreeBSD freebsd10.rdnzl.info 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 r271237: Wed Sep 10 11:00:15 EEST 2014 >> root@buildstable10amd64.rdnzl.info:/usr/obj/usr/src/sys/GENERIC amd64 >> >> The next higher version r271238 breaks booting for me. The commit in question is this one: >> >> http://svnweb.freebsd.org/base?view=revision&sortby=rev&sortdir=down&revision=271238 > > Investigating, had no reports of issues while this has been in head. I've just installed a stable/10 kernel, specifically: 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #11 r271316M and booted fine from a mirrored root without issue: config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada0p3 ONLINE 0 0 0 ada2p3 ONLINE 0 0 0 gpart show ada0 ada2 => 34 250069613 ada0 GPT (119G) 34 128 1 freebsd-boot (64K) 162 8388608 2 freebsd-swap (4.0G) 8388770 241680877 3 freebsd-zfs (115G) => 40 586072288 ada2 GPT (279G) 40 128 1 freebsd-boot (64K) 168 8388608 2 freebsd-swap (4.0G) 8388776 577683552 3 freebsd-zfs (275G) I then detached the second disk so the machine had just: config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 ada0p3 ONLINE 0 0 0 Rebooted and again all fine no issues I've also got a raidz1 box on the same kernel it too is fine. => 34 500118125 ada0 GPT (238G) 34 128 1 freebsd-boot (64K) 162 500117997 2 freebsd-zfs (238G) ... So its seems like there's something odd about your environment, especially given you've had a similar issue before. So the questions: 1. What does zpool get all report? 2. What does /boot/loader.conf have in it? 3. What does zdb -C rdnzltank report? 4. What does /etc/rc.conf have in it? Regards Steve