Can't upgrade from 23.05.1 to 23.09.1
-
Today I was trying to update my Netgate SG-1100 at work and it broke. Now I don`t know how to repair it because the device won't even boot, except to marvel prompt.
I have a backup of my configuration but I don't know how to enter it because system simply doesn't load.
The docummentation mentions loading files from USB but pfsense plus files apparently are only available throught a ticket in a paid suscription plan, and my company just purchased the device.
Isn't there another way to get the firmware? After all the device was bought with a firmware and it was an upgrade process the one which apparently corrupted it.
What can I do?
-
@Hugo-Florentino Not sure how the subscription works but I put a ticket requesting firmware for my 6100 and got a reply within about 15 mins!
-
Well the TAC support request asks for a support level (my company just purchased the device, not a support plan), and also for an Order number which we don't have (we bought the device through an importer), so not sure what to do then.
-
@Hugo-Florentino Tickets to get the firmware are free. All Netgate hardware includes TAC Lite.
https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.htmlThe "Order Number" field is optional on the ticket form.
-
Oh I didn't know the lite plan was included, thanks! I submitted the request
-
Well even with the firmware I can't repair the device. I prepared ta flash drive in FAT32, wrote the firmware provided by the ticket to the memory using balena etcher, placed the memory in the device, accesed via serial interface, and restarted, interrupting boot to remain at marvel prompt, then typed run usbrecovery, but when it proceeds to flash the firmware there is an error and it stays there at a prompt:
Erasing the eMMC contents...
Writing the firmware to eMMC...
(this may take a few minutes to complete)
(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 5b 3a 51 00 00 80 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Retrying command, 3 more tries remain
(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 5b 3a 51 00 00 80 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Retrying command, 2 more tries remain
(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 5b 3a 51 00 00 80 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Retrying command, 1 more tries remain
(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 5b 3a 51 00 00 80 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Retrying command, 0 more tries remain
(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 5b 3a 51 00 00 80 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Error 5, Retries exhausted
g_vfs_done():ufsid/6570ef759d825740[READ(offset=2784788480, length=1048576)]error = 5
g_vfs_done(): ufsid/6570ef759d825740 converting all errors to ENXIO
g_vfs_done():ufsid/6570ef759d825740[WRITE(offset=1729986560, length=16384)]error = 6 supressing further ENXIO
panic: UFS: root fs would be forcibly unmounted
cpuid = 1
time = 1701900601
KDB: enter: panic
[ thread pid 1011 tid 100106 ]
Stopped at kdb_enter+0x44: str xzr, [x19, #1792]
db> -
Try using the other USB port to boot the recovery image. If it still fails try a different USB stick. That error is with trying to read the USB drive not the on-board storage.
-
Well the part where it loads the OS from the USB seems to be working fine. The problem comes at some point when writing the firmware. The USB port I am using is the slow one since the USB 3.0 port didn't recognize the flash drive.
I really haven't tried with another memory, I will do that just to discard problems with a faulty flash drive, thanks.
-
You were correct. I used a USB 3.0 flash drive, placed it in the SS port, repeated the process and this time the firware was flashed correctly.
Thank you all, problem solved. :-)
-
Yes, it's unexpected to find it boots but then fails later but that can happen. I'd have to guess it's moving the data far faster across when copying out the image and something can't handle it.
Good result.
