@emmdee said in Netgate 8200 Max pfsense+ v22.05.1 local disk boot after install.:

After install, at least on the 7100 devices, I can always just load the boot menu and choose the internal disk after installing and it bypasses the USB as expected. This avoids having to get someone physically near the device the pull the USB for initial boot.

I do realize the installer instructions say to physically remove the USB to reboot, however it also says this for the 7100 device and it works fine choosing from the boot loader. The reason I'm trying to avoid physically removing the USB for each of these installs (I have to do several of these) is because these devices are located globally and it can take days for an international support request to the local datacenter to pull the drive, then I "hope" it works, and they have to then reinstall the drive when I'm done again anyways (for ECL usage) and there is back & forth with the facility crews and it can take days just to work with the datacenter depending on their location and facility SLA and it costs my company money every time I open a remote hands request.

Screenshot hopefully gives a good indicator of what I'm seeing.

boot loader

Here is the menu option after selecting < to show the path:
boot loader with path

I can boot to USB with no issue and reinstall as needed. I've tried reinstalling several times and with different options.

……
I'm on a serial connection so it's a little difficult to catch all messages.

I'm just looking for some insight or ideas on what I could try or diagnose remotely over a serial console without giving on-site teams the runaround. I can hop into an installer shell chrooted….

Let’s ask one question: how You connect to the pfSense itself in data center:

by SSH on a dedicated uplink;
OR by “Special request for KVM access” to DC crew for extra payment?

Because of issues like this I ALWAYS prefer bare metal servers that have 2xPSU and BMC (iRMC, iRMC, etc…) on NON-SHARED (multiplexed) ETH.
And Yes, 2 physical uplinks better than 1 (even in same DC, even link aggregator switch are above in the same rack).

Even TOC in this case may be decrease because less numbers of “Special Requests” to DC crew.

But You ALWAYS have FULL server MANAGEMENT, MONITORING through SSL serts, and even MOUNTING REMOTE STORAGE.

@stephenw10 Yep, I that resolved the error for one of the configs. Let me try editing the configs on the other 2 firewalls.

Yup open a ticket and request the recovery image: https://www.netgate.com/tac-support-request

Yup you should be able to upgrade to 23.09 then to 23.09.1.

Though you could also upgrade to 23.05.1 then 23.09.1. It shouldn't matter which way you do that.

Steve

@JonathanLee ok cool, so I shouldn’t expect a huge increase in temp.

You can still see it on a video console it's just more complex to do so. Scrollback through the buffer directly or pipe dmesg through more.

Thx very much to both. Its my first installation in baremetall and fail.
I had created the mirror and encrypted the disks and the swap and the error "gpart: geom 'nvd0': File exists" appeared when trying to reinstall.
I have been able to delete the partitions.

@stephenw10 Thank you for your help. I changed USB port and it worked.

Check the actual partition size: gpart list

@stephenw10
282eef10-63cc-40bb-a0e0-8bdf16a380c8-image.png

@cmcdonald I was able to open a ticket and get the install media easily. I am back on 23.09.1 and have restored my previous config. Good to go now thank you for your help.

@Zwei said in [Solved] Virtualbox + PFSense + OpenVPN – No Route to Host:

"Win10 + Virtualbox + PFSense + OpenVPN – No Route to Host"

This is a really common problem and you may be the only person to have ever solved it and written a post about it.

Thank you!

If there's an external switch on the LAN side with the clients connected to that they should always be able to ping each other. If they cannot it's probably a bad subnet set somewhere. Or they aren't receiving an IP/subnet at all.

@cschumann said in Upgrade 23.09 to 23.09.1 failed:

Hello,

I get this error at the update-process:

Updating the EFI loader
install: //boot/efi/efi/boot/INS@PATnQX: Input/output error
pkg-static: POST-INSTALL script failed
failed.

What can I do?

Problem solved with this ticket:

Unable to upgrade from 2.7.1 to 2.7.2 | Unmounting /boot/efi... done. | failed.

https://forum.netgate.com/post/1140955

Hmm, disappointing. It's common to see a lot of errors at upgrade if you're looking at the console. It should still succeed of course!

@pixel24 Always read the release notes ;)

https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshooting

@stephenw10 Steve, I will continue tomorrow with your valuble new suggestions to solve my problem and will let you know the results.
Thanks sofar, Felix

There is a ZFS widget in Plus but it doesn't specifically show mirror status. There isn't yet a gui method to add/remove disks from the mirror.

For reference it was this: https://redmine.pfsense.org/issues/14026

@stephenw10 said in pfsense 2.7.2 Never completes startup process:

No outbound NAT perhaps?

i sent pm to you.