From owner-freebsd-fs@freebsd.org Wed Sep 19 19:05:15 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FD8A10A41C3 for ; Wed, 19 Sep 2018 19:05:15 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.2 with cipher DHE-RSA-CAMELLIA128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DD6CB8DE83 for ; Wed, 19 Sep 2018 19:05:14 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Wed, 19 Sep 2018 21:04:48 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1537383906; bh=+fD7GQnYGJDoXCYdQnWRyIUD73/mSz3pZxlxtcDm7Dk=; h=Date:From:To:Subject:In-Reply-To; b=V5dHdQAAuqayocWo2H6x+pgoiYCxlbDtD+0ipNoEqQ9WJYcN0iQ+yq/xmNINOKbWT iILlVD4qqmrjqwdFjb1S3KNXEovPMWF7cguboF0bghC0fME76pqNu/CfGY5m4VJUfm hGt1cYOwD2kv6LllmiqiNSFEX1b1seCbsIhSwM6B6NnwYS7htawanNIq2aBSWsrqfJ R++t0UbGJ69Jqe1INqDFDgF8/F54BRBzAoE/Rj7/Zdvf4uo1ssr9mhn5nXFrEc0utF t7aKNLzbqOPcObi6cyUK/kW32t926es1OQ1nY9q4PIHb0RRdGtg0d6z24x6tPiIkXS fwxURxoRWkbkA== Message-ID: <20180919210448.Horde.pAvRtBuz4AvR5qdGFrmSjTp@webmail.leidinger.net> From: Alexander Leidinger To: freebsd-fs@freebsd.org Subject: Re: Fixing vdev name In-Reply-To: User-Agent: Horde Application Framework 5 Accept-Language: de,en Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Sep 2018 19:05:15 -0000 Quoting David Chisnall (from Wed, 19 Sep 2018 15:16:16 +0100): > Hello the list, > > I have a VM that uses ZFS with a pair of striped devices. The first > is a partition on the root disk, created by the installer. When > this was too small, I added another device (da1) and told the pool > to expand to use it (no redundancy, because the underlying storage > for the VM images provides that). After a reboot, I can no longer > boot the system. Booting from the install CD and attempting to > import the pool, it correctly identifies da0p4 as one of the > devices, but gives me a long number instead of da1. This means ZFS doesn't see the other device (or more correctly no device with the ZFS meta-data on the device which matches what the pool wants to see as the second vdev). Do you see the second disk from non-ZFS tools? Does the partition info look OK there (if you partitioned it before giving it to ZFS)? Does the geometry/size look correct? > How do I fix this so that the pool again points to da1? As a side note, it doesn't matter if it is da1 or something else (e.g. /dev/gpt/ or whatever), as long as it is a geom provider instead of the uuid of the device like it seems to be the case right now. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF