|
Revision tags: release/12.4.0, release/13.1.0 |
|
| #
52ce808a |
| 08-Dec-2021 |
Emmanuel Vadot <[email protected]> |
bsdinstall: zfsboot: Prompt user for zpool name if the pool already exists
If one install FreeBSD on multiple disks (say 13 and CURRENT) the first created pool will always be used. Prompt the user f
bsdinstall: zfsboot: Prompt user for zpool name if the pool already exists
If one install FreeBSD on multiple disks (say 13 and CURRENT) the first created pool will always be used. Prompt the user for a new pool name if we detect that the default or supplied one already exists.
Reviewed by: imp MFC after: 2 weeks Sponsored by: Beckhoff Automation GmbH & Co. KG Differential Revision: https://reviews.freebsd.org/D33331
(cherry picked from commit 9935b0e8ea41804b32576987531be4d31ba705f1)
show more ...
|
|
Revision tags: release/12.3.0, release/13.0.0 |
|
| #
611d8311 |
| 23-Feb-2021 |
Nathan Whitehorn <[email protected]> |
Mount the EFI system partition (ESP) on newly-installed systems and VM images.
Per hier(7), the ESP will be mounted at /boot/efi. On UFS systems, any existing ESP will be reused and mounted there; o
Mount the EFI system partition (ESP) on newly-installed systems and VM images.
Per hier(7), the ESP will be mounted at /boot/efi. On UFS systems, any existing ESP will be reused and mounted there; otherwise, a new one will be made. On ZFS systems, space for an ESP is allocated on all disks in the root pool, but only the partition actually used to boot is set up and mounted.
This makes future upgrades of the EFI loader easier (upgrade scripts can just change /boot/efi) and also greatly simplifies the parts of the installer involved in initialization of the ESP. It also makes the installer's behavior correspond to the documentation in hier(7).
Reviewed by: imp, tsoome, bdragon Approved by: re (gjb) Relnotes: yes Differential Revision: https://reviews.freebsd.org/D28897
(cherry picked from commit 0b7472b3d8d2f1e90fade5236b44fd98d8e396c2) (cherry picked from commit 2c26d77d989abe48c662eeb6f52f7e4c9b81680c) (cherry picked from commit e77cf2a4ab32a381df3c06d25b8b4f650047c3f2) (cherry picked from commit e70eb40271512dfbca7cecf823e4b445e3989c2e)
show more ...
|
| #
c415d0df |
| 15-Jan-2021 |
Mitchell Horne <[email protected]> |
bsdinstall: riscv-specific tweaks
Make the installer more useful, by allowing it to create a bootable installation. Also, enable the menu option for ZFS-on-root.
Like arm64, RISC-V boots by UEFI on
bsdinstall: riscv-specific tweaks
Make the installer more useful, by allowing it to create a bootable installation. Also, enable the menu option for ZFS-on-root.
Like arm64, RISC-V boots by UEFI only, so arm64's partedit implementation is renamed and shared among the two platforms.
Reviewed by: gjb
(cherry picked from commit 7b08a307e88bb1abe17d13d11288392a8e4739ce)
show more ...
|
|
Revision tags: release/12.2.0, release/11.4.0 |
|
| #
a107ddbb |
| 15-Jan-2020 |
Rebecca Cran <[email protected]> |
bsdinstall: Use TMPDIR if set
Submitted by: Ryan Moeller <[email protected]> Reviewed by: bcran, Nick Wolff <[email protected]> Differential Revision: https://reviews.freebsd.org/D22979/
|
|
Revision tags: release/12.1.0 |
|
| #
a89559c2 |
| 09-Oct-2019 |
Yuri Pankov <[email protected]> |
bsdinstall: fix ESP detection for auto ZFS layout
Pass the list of user selected disks from zfsboot to bootconfig so that the latter doesn't rely on ESP autodetection that apparently fails for some
bsdinstall: fix ESP detection for auto ZFS layout
Pass the list of user selected disks from zfsboot to bootconfig so that the latter doesn't rely on ESP autodetection that apparently fails for some cases, e.g. memstick installation with nvme (boot) and sata drives.
While here, fix printing of debug messages in bootconfig.
Reviewed by: bcran, imp, tsoome Differential Revision: https://reviews.freebsd.org/D21930
show more ...
|
|
Revision tags: release/11.3.0 |
|
| #
db8b5613 |
| 20-Dec-2018 |
Rebecca Cran <[email protected]> |
Rework UEFI ESP generation
Currently, the installer uses pre-created 800KB FAT12 filesystems that it dd's onto the ESP partition. This changeset improves that by having the installer generate a FAT3
Rework UEFI ESP generation
Currently, the installer uses pre-created 800KB FAT12 filesystems that it dd's onto the ESP partition. This changeset improves that by having the installer generate a FAT32 filesystem directly onto the ESP using newfs_msdos and then copying loader.efi into /EFI/freebsd. For live installs it then runs efibootmgr to add a FreeBSD boot entry in the BIOS.
Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D17947
show more ...
|
|
Revision tags: release/12.0.0 |
|
| #
1b41374f |
| 28-Oct-2018 |
Devin Teske <[email protected]> |
Sort i18n messages in bsdinstall zfsboot
No functional change.
Sponsored by: Smule, Inc.
|
| #
2c9d3297 |
| 28-Oct-2018 |
Devin Teske <[email protected]> |
Adjust for 80-columns.
No functional change.
Sponsored by: Smule, Inc.
|
| #
ee21b0ef |
| 26-Oct-2018 |
Devin Teske <[email protected]> |
Adjust bsdinstall zfsboot code to 80-columns and whitespace fixes
No functional changes.
Sponsored by: Smule, Inc.
|
| #
aa2a0e0f |
| 23-Aug-2018 |
Allan Jude <[email protected]> |
bsdinstall/zfsboot: Enable new UEFI+GELI support
After r336252 it is no longer necessary to have a separate bootpool when booting from an encrypted disk with UEFI.
This change also switches the EFI
bsdinstall/zfsboot: Enable new UEFI+GELI support
After r336252 it is no longer necessary to have a separate bootpool when booting from an encrypted disk with UEFI.
This change also switches the EFI System Partition contents from the 800 KB boot1.efifat to a new 200 MB filesystem created with newfs_msdos and uses loader.efi directly, instead of boot1.efi.
PR: 228916 Reviewed by: dteske MFC after: 1 month Relnotes: yes Sponsored by: Klara Systems Differential Revision: https://reviews.freebsd.org/D12315
show more ...
|
|
Revision tags: release/11.2.0, release/10.4.0 |
|
| #
e39a9678 |
| 30-Jul-2017 |
Ed Maste <[email protected]> |
bsdinstall: default to UEFI-only boot on arm64
Reviewed by: allanjude Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D11721
|
|
Revision tags: release/11.1.0 |
|
| #
98b9d384 |
| 20-Jun-2017 |
Steven Hartland <[email protected]> |
Fixed bsdinstall location of vfs.zfs.min_auto_ashift
vfs.zfs.min_auto_ashift is a sysctl only not a tunable so updated bsdinstall to use the correct location /etc/sysctl.conf instead of /boot/loader
Fixed bsdinstall location of vfs.zfs.min_auto_ashift
vfs.zfs.min_auto_ashift is a sysctl only not a tunable so updated bsdinstall to use the correct location /etc/sysctl.conf instead of /boot/loader.conf
Reported by: Aaron Caza Reviewed by: allanjude MFC after: 2 days Sponsored by: Multiplay Differential Revision: https://reviews.freebsd.org/D11278
show more ...
|
| #
4ca43ae5 |
| 16-Jun-2017 |
Ed Maste <[email protected]> |
bsdinstall: use consistent EFI configuration across platforms
- increase arm64 EFI partition to 200M, as x86 - use EFI_BOOTPART_SIZE and EFI_BOOTPART_PATH macros on x86 - increase ZFS EFI partition
bsdinstall: use consistent EFI configuration across platforms
- increase arm64 EFI partition to 200M, as x86 - use EFI_BOOTPART_SIZE and EFI_BOOTPART_PATH macros on x86 - increase ZFS EFI partition to 200M
PR: 201898 Reviewed by: allanjude, manu MFC after: 3 days Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D11239
show more ...
|
| #
46c380e6 |
| 12-Jun-2017 |
Allan Jude <[email protected]> |
bsdinstall: Make ZFS min_auto_ashift adjustment persistent
Reported by: feld Reviewed by: dteske, tsoome MFC after: 3 days Sponsored by: ScaleEngine Inc. Differential Revision: https://reviews.freeb
bsdinstall: Make ZFS min_auto_ashift adjustment persistent
Reported by: feld Reviewed by: dteske, tsoome MFC after: 3 days Sponsored by: ScaleEngine Inc. Differential Revision: https://reviews.freebsd.org/D10895
show more ...
|
|
Revision tags: release/11.0.1, release/11.0.0 |
|
| #
1b63cafb |
| 16-Jul-2016 |
Allan Jude <[email protected]> |
A failed installation once restarted will often error out
If an encrypted install is attempted and fails for any reason, the disk cannot be erased by the installer because the partition is in use by
A failed installation once restarted will often error out
If an encrypted install is attempted and fails for any reason, the disk cannot be erased by the installer because the partition is in use by GELI
At the start of the installation process, all ZFS pools are exported and all GELI instances are detached, to allow a restarted install to proceed
PR: 210814 Reported by: jonathan MFC after: 10 days
show more ...
|
| #
4487af02 |
| 16-Jul-2016 |
Allan Jude <[email protected]> |
Fix encrypted MBR install
The pools are exported and reimported in order to write the bootcode This causes an error when the bootpool is later mounted by common code The bootpool is now imported wit
Fix encrypted MBR install
The pools are exported and reimported in order to write the bootcode This causes an error when the bootpool is later mounted by common code The bootpool is now imported with the -N flag to prevent mounting
Reported by: Michael Dexter MFC after: 5 days
show more ...
|
| #
ca13d5d2 |
| 03-Jul-2016 |
Allan Jude <[email protected]> |
Fix an error in bsdinstall when ZFS installation uses a bootpool
A separate bootpool is used when the selected partition type is MBR or when the disk is GELI encrypted and a UEFI loader is selected.
Fix an error in bsdinstall when ZFS installation uses a bootpool
A separate bootpool is used when the selected partition type is MBR or when the disk is GELI encrypted and a UEFI loader is selected.
BIOS avoids the bootpool by using bootcode and loader that support GELI.
bsdinstall did not remount the bootpool after creating the main pool, which caused an error when mkdir tried to create /boot/zfs
PR: 210717 Approved by: re (gjb) Sponsored by: ScaleEngine Inc.
show more ...
|
| #
52fffe93 |
| 10-Jun-2016 |
Allan Jude <[email protected]> |
Fix bsdinstall for root-on-zfs with MBR partitioning
Fix an error where vfs.root.mountfrom was not always set as required when creating a bootpool. After the recent geliboot changes, it was only set
Fix bsdinstall for root-on-zfs with MBR partitioning
Fix an error where vfs.root.mountfrom was not always set as required when creating a bootpool. After the recent geliboot changes, it was only set if the main pool was encrypted.
Also resolve an error where the bootpool was unmounted twice causing bsdinstall to stop with an error message about the failed command.
Approved by: re (gjb) Sponsored by: BSDCan Hacker Lounge
show more ...
|
| #
24d17f1e |
| 24-May-2016 |
Allan Jude <[email protected]> |
Only set kern.geom.part.mbr.enforce_chs=0 once, instead of once per disk
Sponsored by: ScaleEngine Inc.
|
| #
bb4fd0a0 |
| 24-May-2016 |
Allan Jude <[email protected]> |
Add support for RAID 1+0 (striped mirrors) to bsdinstall/zfsboot
Sponsored by: ScaleEngine Inc.
|
| #
b06bc65e |
| 23-May-2016 |
Allan Jude <[email protected]> |
Only export and re-import the root pool if installing on MBR
This step is required in order to dd the boot2 bits into the ZFS partition
Sponsored by: ScaleEngine Inc.
|
| #
7289f18f |
| 23-May-2016 |
Allan Jude <[email protected]> |
Fix missing pool name in zfs set command
|
| #
dcf36219 |
| 23-May-2016 |
Allan Jude <[email protected]> |
Fix error in bsdinstall where additional filesystems cannot be mounted
Do not set canmount=noauto on the boot environment at create time, because this causes / to not be mounted, and since the chroo
Fix error in bsdinstall where additional filesystems cannot be mounted
Do not set canmount=noauto on the boot environment at create time, because this causes / to not be mounted, and since the chroot is read only, new mountpoints cannot be created.
The property is set later, when other properties are adjusted
Reported by: HardenedBSD Sponsored by: ScaleEngine Inc.
show more ...
|
| #
a1b8f55c |
| 22-May-2016 |
Allan Jude <[email protected]> |
bsdinstall/zfsboot GPT+BIOS+GELI installs now make use of GELIBOOT
In this configuration, a separate bootpool is not required. This allows ZFS Boot Environments to be used with GELI encrypted ZFS po
bsdinstall/zfsboot GPT+BIOS+GELI installs now make use of GELIBOOT
In this configuration, a separate bootpool is not required. This allows ZFS Boot Environments to be used with GELI encrypted ZFS pools.
Support for GPT+EFI+GELI is planned for the future.
Tested by: Joseph Mingrone, HardenedBSD Relnotes: yes Sponsored by: ScaleEngine Inc. Differential Revision: https://reviews.freebsd.org/D5869
show more ...
|
| #
595568b5 |
| 22-May-2016 |
Allan Jude <[email protected]> |
Fix default ZFS layout to work better by default with sysutils/beadm
The root file system is mounted early via vfs.root.mountfrom. The canmount=noauto property only affects the zfs rc.d script. This
Fix default ZFS layout to work better by default with sysutils/beadm
The root file system is mounted early via vfs.root.mountfrom. The canmount=noauto property only affects the zfs rc.d script. This ensures that the 'default' BE is not mounted overtop of another BE when one is selected from the beastie menu
Sponsored by: ScaleEngine Inc.
show more ...
|