Date: Mon, 09 Jul 2018 07:00:39 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 229628] Can't import bootpool in ZFS installation with installerconfig Message-ID: <bug-229628-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229628 Bug ID: 229628 Summary: Can't import bootpool in ZFS installation with installerconfig Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: kiri@kx.openedu.org Created attachment 194980 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D194980&action= =3Dedit bsdinstall,zfsboot and script patch of 12.0-CURRENT-r335317 In bsdinstall using installerconfig, if you divide the ZFS file system into bootpool and zroot, there are the following problems.=20 (1) Since /boot is symbolically linked to /bootpool, it is=20=20 expanded by tar - xf distrubution_tarball - C chroot_directory=20 in script so it will not be expanded to /bootpool. This=20 can be solved by adding the -P option to tar.=20 (2) bootpool's zpool.cache information does not contain bootpool information and zroot's zpool.cache does not exist, bootpool will not be imported at boot time and will not boot properly. To solve this problem create zpool.cache with bootpool and zroot in /boot/zfs/zpool.cache with zpsboot on bootpool after creating bootpool, and on zroot as well zpool.cache in /boot/zfs/zpool.cache.=20 If you try to output debugging information to the display and the file at the same time, it will not be output to the specified file normally . This is because tee does not have the -a option in bsdinstall. --=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-229628-227>