[Bug 274223] scriptedpart utility fails refuses to generate an fstab file, making automated v14.0 installs impossible.

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 02 Oct 2023 19:31:54 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274223

            Bug ID: 274223
           Summary: scriptedpart utility fails refuses to generate an
                    fstab file, making automated v14.0 installs
                    impossible.
           Product: Base System
           Version: 14.0-CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: ladar@lavabitllc.com

Created attachment 245389
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=245389&action=edit
Error message when /mnt fills up.

The v14.0 installer has a broken version of the
/usr/libexec/bsdinstall/scriptedpart utility. It partitions the target disk
properly, but doesn't write the target disk layout to an fstab file, as it
should. Because of this, the '
'bsdinstall mount' step fails to mount the target disk onto the /mnt
mountpoint. Because the /mnt directory is setup as a tmpfs (with my configs),
the installer continues. It then either a) fails when the /mnt partition runs
out of space, or b) if the tmpfs is large enough, completes the install, only
to have it disappear when the VM reboots.

This issue was discovered with HBSD v14.0 and then confirmed using the FBSD
14.0 BETA4 and BETA1 installers. See these emails for more verbosity on the
subject.

https://groups.google.com/a/hardenedbsd.org/g/users/c/co6oSBfmdOE/m/0aBHQ54qAwAJ

https://groups.google.com/a/hardenedbsd.org/g/users/c/co6oSBfmdOE/m/yvs6JkQ9AwAJ

https://groups.google.com/a/hardenedbsd.org/g/users/c/co6oSBfmdOE/m/8xCnhSJAAwAJ

https://groups.google.com/a/hardenedbsd.org/g/users/c/co6oSBfmdOE/m/wL2mf8xOAwAJ

I've confirmed this bug on QEMU using the AMD64. The other hypervisor installs
(Vbox, Vmware, Hyper-V, etc) also failed, so I assume the bug isn't platform
specific, but I haven't pulled up the console on the systems to confirm.

-- 
You are receiving this mail because:
You are the assignee for the bug.