Failed upgrade from 2.7.0 to 2.7.1 results in unbootable disk
-
Hello!
First of all I fully admit jetlag aided my bad decision and current predicament.
I got home from a long trip and a few hours later the network goes out. I reboot some routers and switches and everything is fine. I figure what the heck I will update from 2.6.0 to 2.7.0 because I have been putting if off for a while.
The update to 2.7.0 goes fine. I do a reboot and see an update to 2.7.1 is there too. Might as well update again since we have had downtime.
This is where things to south. I do not have logs anymore because all seems lost. In the update window I got an update failed error. Well maybe I need to reboot and try again. Nope, the system never comes back up. I go plug in a monitor and see the bios cannot find a bootable device. Time for panic.
So here is where I am. I have installed 2.6.0 on another drive and mounted the original drive. I cannot find anything leftover from the original install, only .cshrc .profile .rnd .snap .sujournal dev lib libexec sbin usr var. I was really hoping I could pull the config, but it seems gone.
I swore I had recent backup's but I cannot find them and the newest one is from 12.2022, config rev 22.2 when I try to restore that is fails to restore to a fresh 2.6.0 install.
At this point I am hoping for a miracle, but fearing the worst.
-
Config rev 22.2 is the correct version for 2.6.
https://docs.netgate.com/pfsense/en/latest/releases/versions.html.How does the restore fail?
I would install 2.7.2 and try to restore it into that directly.
I assume you did not have ACB configured?
Steve
