Date: Mon, 11 Nov 2019 09:40:21 -0330 From: Jonathan Anderson <jonathan.anderson@mun.ca> To: Andriy Gapon <avg@FreeBSD.org> Cc: "freebsd-fs@FreeBSD.org" <freebsd-fs@freebsd.org> Subject: Re: Broken ZFS boot on upgrade Message-ID: <20191111131021.GC70914@bagstock.jonandchrissy.ca> In-Reply-To: <1cb4895b-c84d-6204-18fa-53eac7195ad6@FreeBSD.org> References: <CAP8WKbJWSHzhFCKijRVxydKEwgD_4NX2gmA-QVEVZPuotFCGvQ@mail.gmail.com> <1cb4895b-c84d-6204-18fa-53eac7195ad6@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/11, Andriy Gapon wrote: > Could it be that you have 2TB+ disk(s) and a relatively old BIOS ? The first two vdevs use 1 TiB disks, but the third vdev has 3 TiB disks, so that sounds like a possible explanation... perhaps the contents of /boot previously resided on one of the 1 TiB vdevs but the new /boot lives on the new vdev post-upgrade. Is there a zfs admin command to ask which vdev(s) a file or directory's blocks reside on? My BIOS is from 2016, so not "old", but possibly old enough? Thank you, Jon -- Jonathan Anderson jonathan@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191111131021.GC70914>