Use pkg remove.

I meant install an mSATA drive into the 4860 and switch to booting from that instead. But if you have a complete spare unit it's not really an issue.

@Gertjan Thats quite an approach... maybe it was too much out of the box for me 😳

@stephenw10,

Here is the original post where I installed and configured the boot options. I have never changed the BBS priorities since in the BIOS.

--> [https://forum.netgate.com/topic/141300/sg-5100-verify-that-m-2-ssd-is-recognized-after-physically-installing?_=1700249887071](link url)

Again my motto at this point is "if it ain't broke - don't fix it".

Phizix

Connect to the command line (console or ssh) and then run: pkg-static upgrade.

See what it offers you. But upgrading the rest of the packages manually should get you to 23.09.

Steve

Console access was required. cmd line upgrade via pkg upgrade allowed the device to upgrade. Was not able to detect why the prior UI upgrade did not succeed.
Thank you.
Regards,

Send me your NDI in chat and I'll check it.

You're seeing ssl library or pkg issues after a clean re-install?

It's because the install image is multiboot, it has an EFI partition and loader, but the APU is not UEFI so the installed image on the SSD does not. The upgrade script looks for an EFI partition to update the loader and the only one on the system is on the SD card. It wouldn't happen on a UEFI system.
But that seems like a bug. It shouldn't really do that.

Steve

https://redmine.pfsense.org/issues/14983

@stephenw10 I've sent you the NDI. Thanks!

@Mission-Ghost said in SG1100 Update USB Console Failed:

As an aside, I hope future Netgate products always include a hardware factory reset button in their design. The absence of such a button on the 1100 lacks customer focus and makes contending with failed upgrades and malfunctions such as this much more difficult than it has to be.

We don't always have complete and total control over every aspect of the hardware as we develop new platforms, but we do try to have a config reset button if at all possible since we know it makes things easier for users (and TAC). Plus we are always trying to make the process easier for users. Just wait until you see the reset process on the next device, it's the best one yet. :-)

Send me your NDI in chat and I'll check it.

@dfe_pfsense

Hello Everybody,

Finally I do an upgrade from CLI interface with pfSense-upgrade command.
I was obliged to do this command twice as following:

1 - As indicated from "Troubleshooting Upgrade":

pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade

2- With only the pfSense-upgrade cmd with Debug option:

pfSense-upgrade -d

All is fine for me
Best regards

Thanks for the replies!

I have a Surface pro 5 and it works on that so a Surace 3 bug I guess!

Pfsense doesn't like the surface dock Ethernet port, doesn't appear as a wan/lan device.

It doesn't like the surface usb Ethernet adaptor either! Same result..

I had two other usb Ethernet hubs which it's been working with so far..

If it was running ZFS you can probably roll back to the BE snapshot from before the upgrade:
https://docs.netgate.com/pfsense/en/latest/backup/zfsbe/loader.html

Otherwise the fastest way back up is almost always re-install clean. Open a ticket to get the 23.09 install image:
https://www.netgate.com/tac-support-request

Steve

@hoopy said in Problems after Netgate 1100 Can't Update from 23.05.1 to 23.09:

pkg-static upgrade

I forgot to mention, I don't have SSH enabled, and that I connected to the console to run pkg-static upgrade. I hope that didn't contribute to any extra work. I did attempt to enable SSH when in was in the half updated state but it would not work (I was also missing /etc/rc.initial). After fully updating with pkg-static upgrade the file is now there. Next chance I'll get I'll enable SSH and try to login.

https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/connect-to-console.html

You may be able to run from USB instead. But it would need to be either a different ZFS pool name or UFS to conflict with the read-only eMMC.

The read only errors you're getting there are because it's trying to alter things on the (read-only) ISO filesystem.

You'll need to mount things under /tmp somewhere when booted from a live image. For example, look at what the "recover config.xml" code does for ZFS:

https://github.com/pfsense/pfsense/blob/master/tools/installer/recover_configxml.sh#L82

It mounts things under /tmp/mnt_recovery and then copies it out to another location under /tmp

In this case it was a problem with the 2.7.1-RC which is now fixed. You shouldn't see that going forward.