Install pfSense from USB does not load kernel??
-
This is what I get:
Wrong order just :)
-
Trying with etcher again to see what happens
/Adde
-
Does not work with etcher either ::(
Keep playing around :)/Adde
-
I did a lsdev and got this...What are win doing there??
When booting I can use 3 different "kernel" in "options: Kernel: Default/kernel/kernel.old??
-
There is a windows partition on the installer so you can put a config.xml in there, and it also contains a copy of the license. That is all normal.
The installer works for pretty much everyone else, so there must be something wrong with either that USB drive or the target hardware/BIOS. Maybe try changing some boot options in the BIOS.
That system is very old, and went EOL about 5 years ago and G5 systems stopped being sold about 10 years ago. It might be a problem with the system in general.
-
@jimp
No its not a problem because i had pfsense verion 2.4.4 installed on this maskine before. I just needed to reinstall te server.
Trying another USB win Win32Manager this time/Adde
-
Did you install 2.4.4 before? Or was it an older upgraded installation? There are some older/outdated systems that booted the 2.3.x installer OK but won't boot 2.4. It's rare, but it has happened.
You might also try a 2.5.0 snapshot.
-
@jimp I did a upgrade from 2.3 I think.... cant remember but i worked. I will try snapshot then :)
-
@jimp
Got the snapshot to work to install and rebooted.
I tried the USB on another pc and it booted correcly. When I install it on my server I get the FreeBSD logo but on the other I got pfSense logo ???
Can It be a kernel problem that is still in memory or on hdd??Anyone who has a 2.4.4 snapshot??
-
@jimp
Got 2.4.5 snapshot installed:) Working now
Dont know what was wrong Hmmmmm
Gonna look into it../adde
-
@jimp Thx for your help. I gonna see what was wrong with my HP. Can be that something is still there even if I rebuild the disk.
/Adde
-
Normally, rufus (and friends) will blow away all mbr sectors so no more partitions etc.
So no FreeBSD or WIN or whatever partitions ....Normally, I wipe them clean myself before with adequate tools like diskpart or other disk-wiping tools.
-
@Gertjan
I used "diskpart" also to wipe the usb before flashing to pfsense.......strangeTried rufus. etcher and win32manager, all failed :( everyone of them wiped in diskpart
I have not failed befor when using rufus or etcher to flash pfsense just this version...can be a bad img as well, I dont really know way.....
/Adde
-
Sorry to open a old topic.
But I got it to work and its up and running on x1250e Watchguard now.
Thanks for your help all :)// Adde
-
That's a 32bit appliance, you can only ever run 2.3.X on there which is obsolete. It's no longer considered secure. You should think about swapping that out when you can.
Steve
-
Registered to put my 2 cents in.
Had the exact same issues as MasterAdde for a few days trying to get the pfSense-2.4.4-p3 img to boot. I was able to install FreeBSD (from the latest memstick dl on FreeBSD's site) just fine via USB, but never from the 2.4.4 img.
Saw MasterAdde was able to get success with the daily snapshot 2.4.5 img, and after a quick img burn, so was I.
-
@stephenw10
Only 2.3.x??? I´m running 2.4.4 (need to check) right now. Something I am not aware of yet that I´m doing wrong ??
Shame that u cant change to a 64bit cpu then :((Still have my "HP Proliant 360 G5" going strong :) (I´ts just so LOUD)
/Adde@stephenw10 Or shall I make another firewall instead of Watchguard??
-
The Watchguard X1250e uses a 32bit bit CPU and cannot run 64bit. pfSense 2.3.5 was the last version that supported 32bit.
So either you're running 2.3.5 or you don't have an X1250e.
Those X-e boxes were great in their day but that day has gone.
Steve
-
@stephenw10 Sorry my misstake :( u are right about the version. It´s 2.3.5 but it is a Watchguard 1250 hihi ;)
Will make a VM Pfsense in Unraid instead :) for now untill I have a pc that does not sound like a turbo maskine like the HP DL-360-S5
/Adde -
Hi Guys, ok Are you ready for this! I was having the same exact issue and I was able to fix it!
I don't know how I fixed it because what I did was a complete mix up of steps that are not in any beta that I have found.
So What I did when I got this picture as seen above.
- Go into Machine setting and click on reset.
- Re-install pfSense ISO image. pfSense-CE-2.4.5-RELEASE-amd64.iso.gz
- Go to this link and follow these steps [https://technicalustad.com/how-to-install-pfsense-in-virtualbox/](link url)
- Once the install is complete from bios boot up hit reboot (do not force unmount yet)
- Once it reboots go through the process again. When is ask if you want to reboot, then "Force Unmount"
- Then click reboot, then you will get error messages. (no worries)
- Either turn the VM off then or simply click on the Machine settings and click reset.
- This finished the Bootup process for me and took me to "pfSense dashboard" where you can then configure interfaces and ip addresses etc...
I'm not sure why this worked because it has nothing do with installing the software, it seems like their is a glitch in the boot up process and doing things in this "exact way" fixes it. At least it did for me.
I don't understand why its acting this way, because I installed two pfSense VMs on my laptop and did not have this problem. It always get weird if you "Force Unmount" at the wrong time. Maybe that is the answer. I remember seeing YouTube Video explaining when to "Force Unmount"
I hope this helps, let me know if you have any questions and maybe I can help!
