SG-2100 23.01 update failed
-
I had the same problem - alas, reflashing (with 23.01) didn't work. On boot it's complaining about there being no MMC partition and 'bad scsi device 0'. I'm currently in correspondence with tech support.
-
Ah well. Tech support had me try with 22.05, but that didn't work either. We eventually concluded that the eMMC flash memory has gone bad. So, a dead firewall. Have to say, though, tech support were very responsive and helpful. It's just that things die sometimes.
-
@mspeculatrix Thanks for the reply. My 2100 was stating the same about the "bad scsi device 0" also during my console reboots before flashing the image file received from Netgate.
-
@gertjan said in SG-2100 23.01 update failed:
Normally, send the latest known 'stable' version. That would be 22.05 if you are using 'Plus'.
Netgate released 23.01 yesterday. :)
-
@alleykat said in SG-2100 23.01 update failed:
efi_load_pe: Invalid DOS Signature
Similar report here on an 1100:
https://forum.netgate.com/topic/177862/23-01-update-failed -
@steveits said in SG-2100 23.01 update failed:
Netgate released 23.01 yesterday. :)
That's what I found out a couple of hours ago.
Now I see :
I was seeing " unable to contact the Netgate servers " last night and this morning (French hours).
I'll stay away from the fire for a day or two, wait out the weekend, and take a coffee monday morning, look at the forum .... and then, I'll prepare my plan 'upgrade', and a plan 'B', and a plan C.
I can wait, I'm a happy "23.01.r.20230208.0600" (release - 0.0001 %) user
-
@gertjan I just happened to be in pfsense and thought. "Hey look an update", and updated lol. Wish I had waited too. Oh well, you never know... But all in all my "recovery" went very well!
-
@alleykat https://redmine.pfsense.org/issues/13967
entire description:
"In some situations an upgrade to 23.01 on an 1100 or 2100 will fail after the upgrade process is unable to update the uefi loader in the efi partition.The upgrade logs show:
[1/2] Extracting pfSense-boot-23.01: .......... done
Updating the EFI loader
cp: //boot/efi/efi/boot/BOOTaa64.efi No space left on deviceThat error does not stop the upgrade which fails to boot when no efi loader can be found."
-
@steveits Wow luckily I saw this post.
My SG-2100 has an update to 23.01 - Luckily after this post I did not download the same.
What is the advice? Should I wait before the update? How do I know this has been fixed BEFORE I hit the updates?
-
@netboy If you create a redmine account you can Watch the bug report. Or I suppose watch this subforum. There are 2100s that have upgraded and obviously Netgate didn't find anything in testing so it's not every device. You can get the 23.01 firmware ahead of time to reinstall.
-
@steveits OK. I guess I will watch this forum before I update.....
-
Naive question here: Given that I'm experiencing problems with the eMMC, is there any way I can log into a minimal BSD environment via the console and try reformatting that drive?
The SG-2100 is way out of warranty and effectively bricked at the moment, so it's not like I can make the situation worse.
-
@mspeculatrix If the eMMC is dead, will adding an m.2 sata drive not work for a fresh installation?
-
@mspeculatrix you can reinstall using the firmware link I posted above.
Ps
https://docs.netgate.com/pfsense/en/latest/troubleshooting/index.html -
@steveits I've already tried using 23.01 and 22.05. No dice.
-
@bigsy I hadn't thought of that. Might be worth dropping a few pennies on an M.2 SSD just to find out. If it doesn't work, I'm sure I can find a use for it.
-
@mspeculatrix You can, and it will work. Once a M.2 SATA drive is fitted in it, the mmc0 wil effectively be disabled. It might prolong the boot phase though if the mmc0 stops responding all together.
-
@keyser Ok, thanks guys. SSD ordered from Amazon. I've already replaced the SG-2100, but it would be good to have a backup.
-
@mspeculatrix https://docs.netgate.com/pfsense/en/latest/releases/23-01.html#errata-known-hardware-issues
It seems that the PCI BUS won't work when using SG-2100 and 23.01.
-
@mcury Not in issue regarding the M.2 Sata port. Its the SOC’s M.2 SATA feature that drives this.