From owner-freebsd-bugs@freebsd.org Tue Jan 8 11:27:46 2019 Return-Path: Delivered-To: freebsd-bugs@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 E2679149C869 for ; Tue, 8 Jan 2019 11:27:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9FD0786018 for ; Tue, 8 Jan 2019 11:27:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 63977149C865; Tue, 8 Jan 2019 11:27:45 +0000 (UTC) Delivered-To: bugs@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 3E388149C863 for ; Tue, 8 Jan 2019 11:27:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA1F886016 for ; Tue, 8 Jan 2019 11:27:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 0B82D20F1 for ; Tue, 8 Jan 2019 11:27:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x08BRhbj017324 for ; Tue, 8 Jan 2019 11:27:43 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x08BRhhm017323 for bugs@FreeBSD.org; Tue, 8 Jan 2019 11:27:43 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 234741] Loader fails to load from ZFS with two disks in JBOD configuration Date: Tue, 08 Jan 2019 11:27:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: theraven@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jan 2019 11:27:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234741 Bug ID: 234741 Summary: Loader fails to load from ZFS with two disks in JBOD configuration Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: theraven@FreeBSD.org After an upgrade of a Hyper-V VM to 12.0, I can no longer boot. The root filesystem is on ZFS, with two virtual disks in a JBOD configuration (my preferred configuration for VMs, because it gives a nice easy way of adding storage: just add more virtual disks as needed and expand the zpool). The loader fails with the error "all block copies unavailable.". I could s= till load the old kernel from the same zpool and boot, and I can boot from the CD image with currdev and vfs.root.mountfrom set to the ZFS filesystem (so I c= an, at least, use the VM - for now, though rebooting involves typing a lot into= the loader prompt). There's also a suspicious loader error message that loader.lua contains an invalid character '*' on line 1: loader.lua doesn't contain the character '= *' anywhere. When the machine was originally installed, it had a single virtual disk in = the zpool, so presumably all of /boot (on zpool/ROOT/default) was on a single d= isk. The second virtual disk is larger than the initial one, so it's likely that blocks in /boot are split over both disks. My guess is that loader is fail= ing to find blocks that are on the second disk. --=20 You are receiving this mail because: You are the assignee for the bug.=