Date: Tue, 08 Jan 2019 11:27:43 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 234741] Loader fails to load from ZFS with two disks in JBOD configuration Message-ID: <bug-234741-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234741-227>