From owner-freebsd-stable@freebsd.org Mon Oct 23 07:41:04 2017 Return-Path: Delivered-To: freebsd-stable@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 8488CE439CF for ; Mon, 23 Oct 2017 07:41:04 +0000 (UTC) (envelope-from fbsd-lists@dudes.ch) Received: from mail.dudes.ch (mail.dudes.ch [193.73.211.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.dudes.ch", Issuer "StartCom Class 3 OV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2012165EA1 for ; Mon, 23 Oct 2017 07:41:03 +0000 (UTC) (envelope-from fbsd-lists@dudes.ch) Received: from mwoffice.virtualtec.office (pippin.virtualtec.ch [93.189.66.120]) (authenticated bits=0) by mail.dudes.ch (8.15.2/8.15.2) with ESMTPSA id v9N7ewTe010008 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 23 Oct 2017 09:40:58 +0200 (CEST) (envelope-from fbsd-lists@dudes.ch) X-Authentication-Warning: mail.dudes.ch: Host pippin.virtualtec.ch [93.189.66.120] claimed to be mwoffice.virtualtec.office Date: Mon, 23 Oct 2017 09:40:57 +0200 From: Markus Wild To: freebsd-stable@freebsd.org Subject: Re: System fails to boot with zfs root on nvme mirror when not using full disks Message-ID: <20171023094057.7a69db2b@mwoffice.virtualtec.office> In-Reply-To: <20171022150304.14d3a0c9@amd64.dudes.ch> References: <20171020171345.073bd9b1@mwoffice.virtualtec.office> <20171020165144.GC96120@in-addr.com> <20171022150304.14d3a0c9@amd64.dudes.ch> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 193.73.211.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2017 07:41:04 -0000 I have found the problem... I seem to be a victim of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221075 I wasn't able to get the system to boot just by using /dev/nvd0p3 and /dev/nvd1p3 (avoiding labels), but I did succeed with a custom kernel as per the PR: include GENERIC ident NOMMC nodevice mmc nodevice mmcsd nodevice sdhci So, there is indeed a problem with that part... Cheers, Markus