2.4.4 fails upgrade and fresh installation
-
@rico it will appear briefly but not show a spinning pipe (I) symbol.
The system is a Intel 7th gen Quad Core with 16gb Ram and SSD. It’s really fast.
-
@grimson I hope this works out. When is 2.50 coming?
Boot FreeBSD 12? I’ll try that and see what happens.
Do you have a link for a distro I can download?
Is it possible that my hardware is just too new? It worked fine in 2.4.2 and 2.4.3
-
Well you can try now by booting and install https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-RELEASE-amd64-bootonly.iso
-Rico
-
And with this image you can verify the problem with your hardware is upstream pfSense in FreeBSD 11.2: https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/11.2/FreeBSD-11.2-RELEASE-amd64-bootonly.iso
-Rico
-
@jbhowlesr said in 2.4.4 fails upgrade and fresh installation:
Let’s take a step back. I create the install media and boot the system off of it. It boots the media and before giving any prompts or (I) spinning pipes, I get the error in the photo in the beginning of this thread.
@jbhowlesr said in 2.4.4 fails upgrade and fresh installation:
@rico it will appear briefly but not show a spinning pipe (I) symbol.
You said nothing shows up, and now it does show up? What is it now?
If it does show do what it tells, hit Escape and go from there.
-
I’ll try that when I get home.
I’m a huge fan of snort and is one of about 3 reasons I push pfsense but fact remains that I’m getting this errors on a lot of systems that all worked with previous version of pfsense
-
As it boots, just keep whacking the space bar.
In the next few days we'll have 2.5.0 snapshots to try, based on FreeBSD 12, which is more likely to help.
-
@jimp if I do this and if i get a prompt, I’m unclear as to what I need to do with this file that’s been mentioned
/boot/loader.conf.local
-
-Rico
-
Perfect. This is exactly what I have been asking for. Thank you so much.
On my way home and will give that a shot when I get there.
-
Big shout out here cause this worked and the system is installing now.
I’ll post again after it’s all up and running and report any further issues
-
Sir, pfsense is running great. However, anytime a reboot occurs, I gotta enter the disable=1 string in your photo. How do I automate this so it can reboot unattended?
-
Now to make it persistent run
echo "hint.sdhci_pci.1.disabled=\"1\"" >> /boot/loader.conf.local
after booting from console or SSH.-Rico
-
To make sure I’m following you
Open >> "/boot/loader.conf.local” using the pfsense file editor”
And add echo "hint.sdhci_pci.1.disabled="1"" to the bottom of the file.
Save then restart the system.
-
echo "hint.sdhci_pci.1.disabled=\"1\"" >> /boot/loader.conf.localis the same thing as opening the file /boot/loader.conf.local and adding
hint.sdhci_pci.1.disabled="1"
in it. -
I’m in the file system now. A file called loader.conf.local does not exist. However, a file called loader.conf exists and I made a copy of it and renamed to loader.conf.local and edited that file with the line above.
EDIT: just tried this and it didn’t work. Obviously I’m missing something?
-
Just login via SSH and type or copy/paste
echo "hint.sdhci_pci.1.disabled=\"1\"" >> /boot/loader.conf.local
reboot and thats it.-Rico
-
The file: /boot/loader.conf.local should contain only the line:
hint.sdhci_pci.1.disabled=1You might add more stuff to it later but since you had to just create it it shouldn't right now.
Steve
-
Thank you much. I did this and it worked like a champ. It’s now booting automatically without needing interaction.
-
@stephenw10 @Rico If I may ask, what is STHC I and why is it now becoming a problem
