HELP! Upgrade to 23.01 bricked 5100
-
My tech saw there was an upgrade available and chose to do so. Bad idea with a new release. Went into a loop saying not ready and wait another 20 seconds. Killed it after an hour. Machine will not boot. We do not have USB recovery drive or whatever is necessary to rebuild this machine. Entire network down for over two hours already. Please help.
-
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
-
Open a support ticket to get the recovery image: https://www.netgate.com/tac-support-request
What does it show at the console when trying to boot?
https://docs.netgate.com/pfsense/en/latest/solutions/sg-5100/connect-to-console.htmlSteve
-
Piling onto the same thread - exact same problem with an 1100. Here's the console output during boot, looks like it can't find the boot file and went (unsuccessfully) to tftp? It's been a while since I've had to think about this level of operation :)
Starting EFI application at 07000000 ...
Card did not respond to voltage select!
Scanning disk sdhci@d0000.blk...
Disk sdhci@d0000.blk not ready
Scanning disk sdhci@d8000.blk...
Found 4 disks
efi_load_pe: Invalid DOS SignatureApplication terminated, r = 9223372036854775806
Reset SCSI
scanning bus for devices...
** Bad device scsi 0 **
BOOTP broadcast 1
DHCP client bound to address 24.243.148.55 (123 ms)
*** Warning: no boot file name; using '18F39437.img'
Using neta@30000 device
TFTP from server 0.0.0.0; our IP address is 24.243.148.55; sending through gateway 24.243.144.1
Filename '18F39437.img'.
Load address: 0x7000000
Loading: T T T T T -
That's not a 5100 so the boot issues are different.
But in your case you should also open a support ticket to get the recovery image. It's unable to find the boot loader so will need to be reinstalled.Steve
-
@stephenw10 ok thanks. Did also file a support ticket so I'll go that way.
I've done a zillion of these upgrades (three different networks over many many years) first time anything like this has happened, FWIW.
-
I'd guess you hit this: https://redmine.pfsense.org/issues/13967 We're still looking at what causes that. I've never seen it on the many many upgrades I've run. Only the upgrade log could confirm that.
-
@stephenw10 Ok thanks. I have another 1100 I'll be upgrading eventually - is there any clue on how to avoid this or just cross fingers and hope?
Kudos to support btw they got me back into business fast, unbricked and operating again already.
-
@stephenw10 Opened a support ticket, Kris promptly sent me a link to the latest firmware, and I have pfsense running again. Haven't completely restored because I ran out and bought a router to temporarily keep the network running. I'll switch back when all my team goes home :-) Kudos for the fantastic and prompt support!!!
-
@nwebber said in HELP! Upgrade to 23.01 bricked 5100:
is there any clue on how to avoid this or just cross fingers and hope?
Not yet unfortunately. I've upgraded numerous devices and never hit that throughout all the beta and RC testing. Nor has anyone else here or any reports of such. So it looks like it's very much edge case at this time.
Steve
-
@rloeb I started this thread and suggest closing it :-)
Tech support was very prompt in providing me with a USB firmware recovery image for the 5100, which installed easily and then upgraded the installed packages. Been working very well since then. Upgraded last night to the new Snort and pfblockerng packages and everything is copacetic. Rare to find a tech support team that responsive!
