SG 1100 unable to check for updates
-
@stephenw10 on my SG1100 I don't have those in my glabel list. No msdosfs anywhere. Should I wait to upgrade once all the kinks are worked out or follow through on the steps listed above. In your opinion? Thanks in advance.
-
This post is deleted! -
We are still testing this so I can't confirm it but I expect devices that have a large enough EFI partition to be upgradable.
However if you have access to the device and can re-install 23.01I would do so now.Steve
-
@stephenw10 understood, and I should be fine as my EFI was the same as @morgenstern ‘s 64M so I will try it when I get back home. Thanks
-
In place upgrades are still disabled for aarch64 devices while we test. Just to be clear.
-
@stephenw10 so are you saying what is pushed via the company under ‘Update’? And does this also include what someone wrote below?
“@xenta back up your config, go to the link in my signature and request the current image, reinstall from a USB and then restore your backed up config.”For if it is better to wait than to rush…. I will do the former. (Wait patiently I will)
-
@andykauffman23 System/Update is still blocked for 1100 (and 2100) right now.
If you have a router with the small EFI partition, you'll need to do the reinstall procedure.
If you have a router with a larger EFI, and UFS, you can wait to upgrade, or do the reinstall which also will use ZFS by default.
If you have a router with ZFS you can wait to upgrade, or do the reinstall.
Always do the config backup part. :)
-
If you are running UFS, which you almost certainly are with a 64MB EFI partition, you might want to reinstall as ZFS anyway.
-
@steveits Thank you very much for the breakdown and your assistance.
-
@stephenw10 thank you for your help as well. I will have to mess with it when the kids aren't here... Makes things a tad bit easier as you can imagine.
-
@andykauffman23 Please let me know how that went, when you get to it. Cheers! ;)
-
I can't believe pfsense would make updates that don't work on their most popular most sold device. Does this sound like something that makes any sense to anyone?
-
Opened a ticket and they provided the image to reflash with instructions right away. Process took about 15 minutes total. Not too bad, and now system has large zfs partition and is ready for updates.
-
I'll get to that eventually, but its not super helpful at the moment since the box is 8000 miles away and currently unattended. Stability, reliability and the ability to leave it running and trust it unattended was the main reason I bought it. Not for the power savings. Thanks though. I'll have someone take care of it as soon as possible, which will likely be weeks if not months, but really, this never should have been allowed to happen in the first place.
-
Updates for the 1100 and 2100 will be re-enabled as soon as we are confident the new upgrade code handles every situation.
-
Slightly unrelated and I'll probably open a separate thread for this, but:
I have had a catastrophic scenario playing out last weekend with upgrading to pfsense+ 23.01 build on our custom built device ("whitebox" is the netgate term apparently).
And so I would urge everybody to be physically present with your device when doing when making that step! However inconvenient it may sound.
I had to reinstall & restore my device from backup several times and ended up having to go back to 22.05 build in the end...
-
Whitebox hardware is always more of a risk because there's no way we can test everything. The 1100/2100 should always be a known device so we can.
But, yeah, open a new thread with any details you have.Steve
-
@stephenw10 Looking forward to this as opposed to doing it the other way. I can do it the other way but right now, I'm in no rush to change it. Unless you say get'er done....
-
I got the 23.01 / SG-1100 email yesterday about needing to do a do a full reinstall. Fortunatley I had not attempted previously but noted "22.05-RELEASE (arm64) => Unable to check for updates**
So after reading the instrutions a couple of times and logging a system outage with the family, I have just successfully attempted it on one of my two pfsense SG-1100 devices ( the other is 80km away so that will have to wait )
Backup your full configuration , i tried placing it as config.xml on the DTBFAT0: partition but it did not restore. there seem to be lots of posts stating different folders, i had to restore it manually at the end . This seems to be the full instructions, i'll try it next time.
When you power off the SG1100 device for too long the the Prolifix USB-to-Serial Comm Port (COMx) disappears on Windows 10, so you have to insert the usb and restart from the browser/web interface if you want to stop the boot and do the run usbrecovery
I setup PuTTY and enabled session logging. Never watched the SG-1100 boot, and there are a lot off messages that scrolls past. It may be interesting to view.
I set ZFS as recommended, not sure if it was a good idea of not. It resulted in the partition below and seems to use more memory.
After the recovery completed, i removed the usb and powered cycled the device.
As i do not appear to have put the config.xml in the correct location, it loaded a default configuration on 192.168.1.1/24, I used the console to configure the correct IP, VLAN, enable DHCP and defaulting to http to access, then used the web interface for the restore.
Note: the default user is admin / pfsense ( fortunately i had access to the internet to find this out ! )Logged on to the web console , change the password and broke out of the wizard. went to Diagnostics, Backup and Restore and reloaded my config, and rebooted.
After the reboot there was a message about not doing anything until the packages were restored. i only had LetsEncrypt so it did not take long.
After a few seconds it was up and running and the IPsec tunnel to the second SG-1100 was active.
My only observation is on an SG-1100 i am now using 30% memory were previously i was using 20%
The web interface seems snappier, but dhcp still takes about 5 seconds to load / displaygpart show => 1 15269887 mmcsd0 MBR (7.3G) 1 532480 1 efi (260M) 532481 131072 2 fat32 (64M) 663553 14606335 3 freebsd [active] (7.0G) => 0 14606335 mmcsd0s3 BSD (7.0G) 0 16 - free - (8.0K) 16 14606319 1 freebsd-zfs (7.0G) -
My only observation is on an SG-1100 i am now using 30% memory were previously i was using 20%
There are quite a few forum posts about this. You might want to read this posting from @jimp and consider installing System Patches and the fixes described.
