Upgrade does not work correct? I assume on purpose?
-
Stephan, ..... I tried every thing ....... it just does not work ...
Note that I did clean installs using a boot usb and a config usb. Trying the things on the linked page as well ...One thing to mention ... I was so ^brave^ to rename my wan-interface ...... with as result that my ipv6 was gone
however the gateway did still show greenI discovered that and did edit the config file back to the original name. That solved the problem I think, however given this issues, I am not 100 % sure.
I did create a ticket ...... however according to Jim, it is not a bug it is ^just not supported^.
What ever I am going to install 2.6 and given that my actual config is not compatible will probably trying to upgrade to 2.7 from there ...
Hope it works, I did already spend far to much time on 2.7 (note that in the past I have always felt positive about development releases).
-
So you installed 2.7 clean and restored your config and ended up with missing base packages?
-
Yep !!!
I just tried to install 2.6 ...... which
- does show the expected "pkg info -x pfsense" packages
- but can NOT handle the config file
And not 2.7 ..... which
- does NOT show those packages
- but can handle the config file
- and has a not working ipv6 interface issue .....
Its a struggle ..... I probably have to go back to an even older config :(
Which is hopefully working .... -
@louis2 said in Upgrade does not work correct? I assume on purpose?:
And not 2.7 ..... which
does NOT show those packages
But I assume only after restoring the config?
-
Stephen, I decided to install the today 2.7 version together with my actual config,
That situation is working, apart from the fact that the update function is broken.
I did invest at least a day trying to find the reason for that, but I simply do not know. All I / we know that : pkg info -x pfSense shows that the packages are not installed.
So for the moment I think I have to live with this. Hoping for a fix in the near future
-
I do not know. pfSense is part of my network, which is only functioning if pfSense is doing its job.
So for that reason I did do the tests with two USB-sticks, one containing the installer image, the other one the desired config to be loaded during boot.
So I never see a pfSense version without config
-
What if .....
The startup procedure assumes that it is ready before the config is loaded ....
However the config is loaded before the startup sequence is ready .......
Then you might have a problem like this one ....
-
Ok, I think I have reproduced this. We are digging into it now.
Does your config have ramdisks enabled?
Steve
-
Yep, I have
my pfSense computer has
- Intel(R) Pentium(R) CPU G4620 @ 3.70GHz 4 CPUs: 1 package(s) x 2 core(s) x 2 hardware threads
- 8 GB RAM (1gb tmp ram disk & 4 GB var ram (3 GB free!?)
- 60 GB sata SSD
-
Related inconvenience ...
The boot priority of the computer is set to boot from the usb above the sata ssd
So If I place the two USB-sticks and reboot, the pc boots into the installer.
The installer at the end ask if it is ok to reboot ..... However If I would answer yes ....... it would boot again ..... with the installer image
So before I can push reboot I have to go downstairs to remove the installer usb.
However I have to leave the config ssd in the system ...... because the config is not yet copied to the sata-ssd .....
So I have to go back to my computer upstairs ....
push the boot OK ..... a small problem ..... the installer usb is gone so the system is confused ...
The easy workaround is Cntr-Alt-Del via my KVMThan the system boots, and I have to go downstairs again to remove the config USB ...
Back to my computer upstairs to continue
It is a good "work out" of course but the process could be a lot easier ....
At least by copying the config to the disk during install, and allow to remove the two disks together before activating the reboot ....
-
OK, it looks like there's a conflict there between running /var as a ramdisk and the way ZFS mounts it.
If you can remove line that enables ramdisks from your config:
<use_mfs_tmpvar></use_mfs_tmpvar>Then retest importing it into a clean 2.7 install.
Steve
-
@louis2 said in Upgrade does not work correct? I assume on purpose?:
At least by copying the config to the disk during install, and allow to remove the two disks together before activating the reboot ....
You can do that. If the config is in the correct place on the USB drive it will be imported during the install and you can then remove it before rebooting:
https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html#restore-configuration-from-usb-during-installSteve
-
Yep and Yep ....
After removing <use_mfs_tmpvar></use_mfs_tmpvar> the upgrade mechanism is working again
And removing both USB-sticks before reboot is also working as described.
So only thing left is the question if it is yes or no a good idea not to use a ram disk given the fact that there is plenty of ram available .. Of cause that largely depends on how the software has been designed, if it is not storing data to disk, which is not intended to survive a reboot ..... unless there is lack of memory .... then ..... there is no need for a ram disk .... I think
-
Well for now the choice is simple. Until this is fixed, do not use ramdisks if you are running ZFS.
https://redmine.pfsense.org/issues/13182At the very least we will add code to prevent that conflict with /var so that may mean only /tmp can be a ram disk. Or there may be a better solution, we are still exploring options.
Steve
