Date: Mon, 04 Jul 2016 04:49:39 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 210803] installerconfig: bsdinstall zfsboot requires ZFSBOOT_DISKS or it fails Message-ID: <bug-210803-6@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210803 Bug ID: 210803 Summary: installerconfig: bsdinstall zfsboot requires ZFSBOOT_DISKS or it fails Product: Base System Version: 10.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: laurieodgers83@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org I am currently setting up a scripted interactive install using installercon= fig for a ZFS-on-root install of Freebsd 10.3. The preamble of installerconfig appears to work perfectly fine - hostname is set, network is set up, ZFS datasets are created and mounted to /mnt etc, however if I don't set "ZFSBOOT_DISKS=3Dada0" within installerconfig then t= he installation shows an error message at the very end and does not proceed wi= th my installerconfig script: "No root partition was found. The root FreeBSD partition must have a mountpoint of '/'."=20 The installer then kicks me to a login prompt of the live CD instead of proceeding with the rest of the installerscript. Note that all ZFS datasets are set up correctly and mounted - I am unsure w= hy the installer is complaining that nothing is mounted? I do not want to have= to set ZFS_BOOT_DISKS=3D as the user should be able to set this up themselves interactively. The preamble to my installerconfig is as follows: ############################## export DISTRIBUTIONS=3D"base.txz kernel.txz lib32.txz" export BSDINSTALL_CONFIGCURRENT=3D"yes" export BSDINSTALL_DISTDIR=3D"/usr/freebsd-dist/" export BSDINSTALL_CHROOT=3D"/mnt" export VAR_NONINTERACTIVE=3D"NO" export ZFSBOOT_DISKS=3D"" export ZFSBOOT_DATASETS=3D" # DATASET OPTIONS (comma or space separated; or both) # Boot Environment [BE] root and default boot dataset /ROOT mountpoint=3Dnone /ROOT/default mountpoint=3D/ # Compress /tmp, allow exec but not setuid /tmp mountpoint=3D/tmp,exec=3Don,setuid=3Doff # Don't mount /usr so that 'base' files go to the BEROOT /usr mountpoint=3D/usr,canmount=3Doff # Home directories separated so they are common to all BEs /usr/home # NB: /home is a symlink to /usr/home # Ports tree /usr/ports setuid=3Doff # Source tree (compressed) /usr/src # Create /var and friends /var mountpoint=3D/var,canmount=3Doff /var/audit exec=3Doff,setuid=3Doff /var/crash exec=3Doff,setuid=3Doff /var/log exec=3Doff,setuid=3Doff /var/mail atime=3Don /var/tmp setuid=3Doff # Create /tredly and friends /tredly mountpoint=3D/tredly /tredly/downloads mountpoint=3D/tredly/downloads /tredly/log mountpoint=3D/tredly/log /tredly/releases mountpoint=3D/tredly/releases /tredly/ptn mountpoint=3D/tredly/ptn # set up the releases datasets so that tredly init runs correctly during install /tredly/downloads/10.3-RELEASE=20=20=20=20=20=20=20=20=20 mountpoint=3D/tredly/downloads/10.3-RELEASE /tredly/releases/10.3-RELEASE=20=20=20=20=20=20=20=20=20=20 mountpoint=3D/tredly/releases/10.3-RELEASE # set up the default partition /tredly/ptn/default mountpoint=3D/tredly/ptn/default /tredly/ptn/default/cntr mountpoint=3D/tredly/ptn/defaul= t/cntr /tredly/ptn/default/data mountpoint=3D/tredly/ptn/defaul= t/data /tredly/ptn/default/log mountpoint=3D/tredly/ptn/defaul= t/log /tredly/ptn/default/psnt mountpoint=3D/tredly/ptn/defaul= t/psnt /tredly/ptn/default/remotecontainers=20=20=20 mountpoint=3D/tredly/ptn/default/remotecontainers " export ZFSBOOT_BEROOT_NAME=3DROOT export ZFSBOOT_BOOTFS_NAME=3Ddefault export ZFSINTERACTIVE=3Dtrue bsdinstall keymap bsdinstall hostname bsdinstall zfsboot bsdinstall checksum bsdinstall distextract bsdinstall netconfig bsdinstall config --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-210803-6>