opnsense / bsdinstaller Goto Github PK

As discussed in various places:

• Show a swap dialog, when a swap can be created: how big it is, why it is needed, what else can be done, optionally skip the swap
• if there is no room for swap, show an info dialog on how the problem can be mitigated

via: https://forum.opnsense.org/index.php?topic=4897.0

We don't have any strong ties to a random root password anymore so we can add a new password after the installation finished by using the available (hidden) dialog and a tweak to rc.initial.password to run in automated mode with two arguments (password and confirmation)

Hello,

The installation of 20.7 (DVD ISO) will not proceed at the install menu on a generation 2 hyper-v VM.

The VM is configured with Secure boot disabled as it will not boot off of the CD with any of the options including the normally used UEFI certificate authority.

The install proceeds as normal until you come across the install type menu. At which point the keyboard stop responding.

The install cannot continue at this point and even disconnecting from console and reconnecting will not fix it.

However, if the install is done on a gen1 VM the install will proceed without issue.

After the install during which EFI/GPT is selected you can then create a Gen2 VM and attach the VHD and it will boot.

Like FreeBSD 11.1

First off all, is this the right place to report a bug with the OPNsense installer?
OPNsense version: 19.1 (DVD iso)
Host: KVM/QEMU

If I increase the UEFI resolution to 1024*768 the installer freeze in the second window "Select Task"

using default 640x480 it works fine:

Describe the bug
Booting from OPNsense-19.7-OpenSSL-dvd-amd64.iso
UEFI @ 1024x768
3rd window in Installer freeze.

Work-around:
1: push CTRL+C, which will get you to the console with a logon prompt.
2: Relogin and you reappear directly to the same 3rd windows in Installer, where you now can continue as nothing has happended.

More details with all screen-dumps:
3rdWinInstallerFreeze.pdf

Environment
OPNsense-19.7-OpenSSL-dvd-amd64.iso
KVM/QEMU VM with UEFI. Boot from ISO.

I can't really provide logs for this, so I'll try to explain what happens.

Sources for this reporting:

1. https://forum.opnsense.org/index.php?topic=7547
2. This is not exactly the same as p1, but similar hardware and exactly the same outcome: https://forum.opnsense.org/index.php?topic=7329

I read many times what Franco was advising in similar cases, especially for p1, so I tried exactly that: install FreeBSD first and see if that works. And it did, FreeBSD installed quite nicely.

As you can see from the forum report, OPNsense 18.1 installer (amd64, vga) fails to install. It hangs right after formatting, right before partitioning the HDD.

I'll define what hang means here:

1. Any visible progress stops after the HDD is formatted
2. I think when trying to partition the HDD, the installer hangs
3. There is no visible progress on the screen after this point
4. CTRL+ALT+DELETE or the power button will display some logs, overlaying the blue screen of the installer with the installation progress
5. There is absolutely nothing wrong hardware wise (professionally tested)

I'll have this hardware (from p1) for another 2 or 3 days, as it is not mine. It will be the main gateway of a client's network, deployed far away from where I live, so access will be difficult, the issue impossible to reproduce and confirm a fix once it's put in place. If anybody has the time to investigate before relocating the box, I'll try to be available.

Thank you all.

If you run the installer from external media with a blank SSD/HDD, and take the install process to the point it starts to write to the new disk, then click "cancel", the installer can't recover, because it doesn't escape you back to the point where you specify the disk or layout. It only lets you escape to the point of retrying the write-out - which then fails.

(Can't remember if this is guided or expert install. Probably guided. Maybe both.)

Apparently, swap files are superior to traditional swap partitions in many ways. I suggest to change the installer to create swap files instead of swap partitions for the default/easy installation. (An experienced user would still be able to configure swap partitions, if desired.)

Benefits:

• swap file can easily be destroyed if the user needs disk space (disk filling up)
• swap space can easily be increased or decreased if required by the user

If you agree to this proposal, I'll try to make the required changes and provide a PR (ETA Q2/2018).

When we use vt, the directory /usr/share/syscons can no longer be used to read console stuff, we need to migrate to /usr/share/vt

Just peek at the install, but run reset like in install...