[SOLVED - manual upgrd] Upgraded to 2.1.4 and now my WG Firebox X700 won't boot!
-
no, i'm running it on a HP G7 N54L..
took close to 25 minutes to update, but it finished.. few packages are working, but i read the notes so… i guess i got some re-installs to do.
-
Yes, also have issues. Did also push upgrade from (nanobsd) 2.1.3 -> 2.1.4 on my spare WG x1250e, and it is now stuck in a boot loop. I don't even get to a bsd boot option (slice selection) :(
Guess I'll need to yank out the CF and see what has happened… ::) -
did this update break the console, 2 things seem broken, first when u boot the alix the message that says u got 5 seconds to hit any key for shell and second when it says bootup complete, the rest of the part that shows console commands and interface ips never show
-
to make my previous post complete:
system was a nanobsd 2G i386 on a kingston CF, minimal packages installed (OpenVPN Client export only), running on a WG x1250e with 1G ram.
First impression I have is that the filesystem has become corrupted or so?
Exact actions take: initiate upgrade from the gui, waited like 40minutes or so (then pulled the plug because it didn't come up).
Connected serially, and saw it was booting in loops… So or the upgrade screwed something, or I did not wait long enough. More analyses later today when I have more time, all suggestions welcome in meantime. -
I get the same boot loops (sounds like a cereal? LOL) but mine says it can't find the boot device that it will restart in 15 seconds and then it gives me the menu to select 1 or 2 (1 being the 2.1.4 and 2 being the 2.1.3 backup) so only way I got it back running was selecting 2 and running off of that backup now) Won't try again until it's solved I guess.
-
Ha! I'm ready for all new Frosted Boot Loops!
That DMA error looks like what you see if you boot the Nano_VGA image. The difference is that DMA is not disabled by default in the vga flavour. Could it be that the new 2.1.4 Nano images don't have DMA disabled? That would make it fail on the Alix box which several developers use so that seems like a case that should have been tested.Reading this post:
https://forum.pfsense.org/index.php?topic=78603.0
It looks like maybe the upgrade image is defaulting to vga and hence DMA still enabled.Steve
-
My X750E unit suffered from this same bug…. Luckily I have 2 units in high availability mode so I didn't have to come running into the office last night when the unit didn't come back to life on its own.
So I was able to get it to boot off the other 2.1.3 image and then cloned my 2.1.3 image to the other boot partition until I see confirmation that the update works properly. I was running the 4g version FYI.
-
I'm with you on the wait…. If anybody is nice enough to let us know when this issue is fixed we will be even more grateful than giving us a super awesome firewall solution! Thanks pfSense!
-
I very nearly vpn'd into my home box to upgrade it but I think I'll hold for a bit. The box is in London but I'm currently in Texas and I don't fancy trying to talk anyone through a remote slice switch.
Keep an eye on the mailing lists. Nothing there yet and if this really is going to nano_vga I would expect it to bite plenty of users.Steve
-
So I'm screwed. Exit the FW from the serverroom, it's on the desk now >:(
Checked fast the CF, I still see the 2 partitions. (so my 2 slices are still there)
Booting the box, I only see output in 115200 baud. Nothing shows when I set it to 9600.
But if it upgraded to the vga image, it kind of explains why I get no serial output I suppose?@phatty, how did you get it to boot the alternate slice without serial output??
As it is already on the desk, the easy route would of course be just flash the latest image… but there's little fun in that, so I'll continue the search for now ;D
@steve; it seems that alix is also affected (if I understood it correctly), see post from "xbipin" earlier in this thread.
-
yes alix affected only regarding the console, the rest still updates and reboots fine also the rest works also
-
Okay, tnx for the feedback, and good that it comes up.
That might explain why others don't report issues (I like to assume I'm like most, and I don't look at the console unless there's issues ;))
Making no progress here with that darn CF. Any hints on how to safely mount that BSD partition in windows?
(sorry, bsd noob here :-[ Still learning…) -
So I'm screwed. Exit the FW from the serverroom, it's on the desk now >:(
Checked fast the CF, I still see the 2 partitions. (so my 2 slices are still there)
Booting the box, I only see output in 115200 baud. Nothing shows when I set it to 9600.
But if it upgraded to the vga image, it kind of explains why I get no serial output I suppose?@phatty, how did you get it to boot the alternate slice without serial output??
As it is already on the desk, the easy route would of course be just flash the latest image… but there's little fun in that, so I'll continue the search for now ;D
@steve; it seems that alix is also affected (if I understood it correctly), see post from "xbipin" earlier in this thread.
Benny, the bios output, and the pfsense output for my setup is 115200, but at 9600, for a very short second, I was able to wait and eventually see the boot options for which slice to boot off of.. It took a couple tries for me to time my button pushing just right to get it to boot off the older image.
-
This is exactly the reason why I run it in VM's…
-
This is exactly the reason why I run it in VM's…
+1.
I can't be bothered playing around with finicky hardware, CF cards and all that nonsense.
-
No if uptime is important, then I see no alternative….and its a lot more flexible as well.
-
It's clever bu how do you do when you must routing more than 7/8 networks ?? You need necessarily a major hardware layer… (machine with 7/8 network devices...)
-
No….I use VLAN's.... and only have 3 physical interfaces...
-
With the watchguard sitting on my desk I attempted to go ahead and update again today. This time I manually retrieved pfSense-2.1.4-RELEASE-4g-i386-nanobsd-upgrade.img.gz from the Bluegrass Mirror. This time update applied and system rebooted properly. Not sure if it was a problem with the auto updater selecting the wrong update, or if they fixed something with the files. I noticed the time stamp on the Bluegrass Mirror where I downloaded the update from was newer than when I had attempted the upgrade last.
-
Making no progress here with that darn CF. Any hints on how to safely mount that BSD partition in windows?
The easiest way to do this, by far, is to do it from a BSD install. If you don't have a BSD machine then run a FreeBSD live CD like GhostBSD.
Steve
