Install bug
-
what is this for ipv6 bug?
-
Dude, cannot you just paste the console output? Like, I mean, get some serial cable. These huge unreadable screenshots just piss everyone off. Or at least shrink the resolution for that damn thing, no need for the screenshot to be 4K.
-
Dude, cannot you just paste the console output? Like, I mean, get some serial cable. These huge unreadable screenshots just piss everyone off. Or at least shrink the resolution for that damn thing, no need for the screenshot to be 4K.
sorry, i am use mobile for visit site that time. I have change files to small size. ;)
-
etc use full ? what is wrong?
-
We don't have any code that would make /etc a RAM disk, let alone one that small. Whatever manual modifications you have made to your firewall are causing it to break. Reinstall the firewall with a stock setup and don't make any edits to the files.
Don't report bugs on custom-modified systems until you can repeat the problem on a stock system.
-
May I ask where did you get this image? (Or, have you really modded it yourself?) Hard to imagine a more broken idea than /etc on a ramdisk.
-
A file was lost before upgrading the system. This time I will overwrite the file upload to the system under the "etc" directory
-
Dude…
1/ Get a GENUINE install image. Not some homebrew crap. Here: https://www.pfsense.org/download/
2/ Do a FRESH CLEAN install. Do NOT upgrade. overwrite or otherwise hack the current clusterfuck.
-
Dude…
1/ Get a GENUINE install image. Not some homebrew crap. Here: https://www.pfsense.org/download/
2/ Do a FRESH CLEAN install. Do NOT upgrade. overwrite or otherwise hack the current clusterfuck.
well… i am try new install, but i only v2.4 backup config file in nanobsd, i am using 32GB USB Card disk.
v2.4 config file not work in v2.3.4
WARNING: Current pkg repository has a new OS major version.
pfSense should be upgraded before doing any other
operation
Failed -
You did not have 2.4 and NanoBSD. I don't know what you did or what you had, but it could not have been 2.4 with NanoBSD.
Just write the 2.4 install memstick img to a different USB stick and then install it on top of your existing USB stick (or even better – use a new one).
-
You did not have 2.4 and NanoBSD. I don't know what you did or what you had, but it could not have been 2.4 with NanoBSD.
Just write the 2.4 install memstick img to a different USB stick and then install it on top of your existing USB stick (or even better – use a new one).
I have try your way, but 2.4 install memstick img can't boot for install. only nanobsd can boot for install.
-
2.4 nanobsd does not exist.
-
NanoBSD also does not "install". It runs in-place. There is no way currently to start with 2.3.x or before NanoBSD and get to 2.4.
We are working on an in-place upgrade to transform a NanoBSD install into a full install (assuming it's 64-bit) but it's still a work in progress.
If you can't boot to install from a USB memstick, there is probably a problem with your BIOS settings, or the hardware in general. Or you're using the wrong installer image.
-
NanoBSD also does not "install". It runs in-place. There is no way currently to start with 2.3.x or before NanoBSD and get to 2.4.
We are working on an in-place upgrade to transform a NanoBSD install into a full install (assuming it's 64-bit) but it's still a work in progress.
If you can't boot to install from a USB memstick, there is probably a problem with your BIOS settings, or the hardware in general. Or you're using the wrong installer image.
NanoBSD can boot. pfSense-CE-memstick-2.4.0-BETA-amd64-20170404-0741.img cant boot for install.
-
There is no 2.4 NanoBSD so that is not a valid comparison. Which NanoBSD image, specifically, can boot?
If 2.3.x boots but 2.4.x doesn't, it is most likely an issue with your BIOS or BIOS settings.
Perhaps boot a 2.3.3 installer, perform a full install, and then upgrade to 2.4 that way.
-
ok. i have using new server install on SSD.
but it is show wrong ipv6 information. what is mean ?
