2.3.5 will not upgrade to 2.4 no errors. on VK-T40E Hardware



  • As it says. 
    If I change the update options to 2.3 beta 2.4 or anything
    it takes the change but it will not update..
    Says I have 2.3.5 and it's up to date.

    I hit save each time change to 2.4 save try then try update again.. 
    Just says it's up to date on 2.3.5

    This is a VK-T40E purchased from the PFSense Store about 2.5 years ago



  • Please don't tell me the cpu is not or no longer supported any longer. 
    We just bought that recently new not much over a year ago.

    Thanks.

    Enter an option: 13

    Updating repositories metadata…
    Updating pfSense-core repository catalogue...
    pkg-static: Repository pfSense-core has a wrong packagesite, need to re-create database
    Fetching meta.txz: . done
    Fetching packagesite.txz: . done
    Processing entries:
    pkg-static: wrong architecture: FreeBSD:11:amd64 instead of freebsd:11:x86:64
    pkg-static: repository pfSense-core contains packages with wrong ABI: FreeBSD:11:amd64
    Processing entries... done
    Unable to update repository pfSense-core
    Updating pfSense repository catalogue...
    pkg-static: Repository pfSense has a wrong packagesite, need to re-create database
    Fetching meta.txz: . done
    Fetching packagesite.txz: .......... done
    Processing entries:
    pkg-static: wrong architecture: FreeBSD:11:amd64 instead of freebsd:11:x86:64
    pkg-static: repository pfSense contains packages with wrong ABI: FreeBSD:11:amd64
    Processing entries... done
    Unable to update repository pfSense
    Error updating repositories!
    Netgate APU - Netgate Device ID: 8a56*******************



  • Hi,

    This forum, the official blog etc has been announcing that last century CPU support (x86) would stop.
    Official pfSense hardware is and was compatible with the 'new' CPU's like AMD64 and 'ARM' ones …

    Check your hardware if you have really a i386 CPU, or just de x86 pfSense version installed, and you can actually shift to 'amd64' version.



  • I don't think it's related to platform. Look at https://forum.pfsense.org/index.php?topic=140566.0 same log but see the last line.

    Looks like known issue for FreeBSD https://wiki.freebsd.org/PkgBase



  • I'd like to be able to update it to 2.4

    It's an official SG- Device purchased from the PFSense Store.

    Netgate APU
    Netgate Device ID: ********************
    BIOS Vendor: coreboot
    Version: SageBios_PCEngines_APU-45
    Release Date: 04/05/2014
    Version 2.3.5-RELEASE (amd64)
    built on Mon Oct 30 11:09:03 CDT 2017
    FreeBSD 10.3-RELEASE-p22
    Platform nanobsd (4g)
    NanoBSD Boot Slice pfsense0 / da0s1(rw)
    CPU Type AMD G-T40E Processor
    2 CPUs: 1 package(s) x 2 core(s)


  • Banned

    @N8LBV:

    Platform nanobsd (4g)
    NanoBSD Boot Slice pfsense0 / da0s1(rw)

    https://forum.pfsense.org/index.php?topic=121255.0



  • @N8LBV:

    I'd like to be able to update it to 2.4 
    ….
    Version: SageBios_PCEngines_APU-45
    ....
    Platform    nanobsd (4g)
    ....
    CPU Type AMD G-T40E Processor
    ....

    With this kind of info and the help of Google you'll find this : https://forum.pfsense.org/index.php?topic=137917.0

    edit :the processor type seems fine to me.
    The 'platform' …. less.



  • Hi Thanks for trying to help me! 
    I'm sorry but I am still confused quite a bit. 
    Googling the information I have and searching here first did not answer any of my questions.

    The device will not update and I don't understand why. 
    My understanding is that it has a 64bit CPU and it should work.

    I don't understand why it is not working. 
    2.4 stable and 2.4 beta are available in the updater dropdown but when I select them save and then go try to do an update. 
    It says it's up to date and will not update to 2.4

    This is at a remote location that I don't have physical access to do a "full reinstall" or install from scratch.
    And it's also a VK-T40E purchased 2.5 years ago from the pfsense store. 
    I had the customer pay the $500 and for 1 year support in an effort to avoid this kind of problem/hell. 
    Actually I've installed a number of these in the field, so I expect I'll see this problem on all of them.

    Still confused what should I do?

    Reinstalling from scratch is not an easy or affordable option to the client.
    This is a PFSEnse preinstalled/flashed system I'm not familiar with doing a clean install on one of their devices
    Or if that makes it suddenly an unsupported device or if it is easy to do. 
    I'm guessig it's not easy and requires special partitioning/install uptions to matchthe hardware and nto something
    an install wizwrd is going to do on this hardware.

    This is a potential nightmare and could result in a bricked device if I donlt know exactly what I'm doing wit hte particular hardware. 
    Frustrated a bit here.

    Thanks!



  • @N8LBV:

    The device will not update and I don't understand why. 
    My understanding is that it has a 64bit CPU and it should work.
    I don't understand why it is not working.

    You are using the NanoBSD software platform which has reached its end.
    Your hardware, however, can be used to run the current version just fine. Doing so myself here on the same platform. But I have an mSATA installed.

    @N8LBV:

    … purchased 2.5 years ago ... I had the customer pay the $500 and for 1 year support in an effort to avoid this kind of problem/hell.

    That expired 1.5 years ago, so … You can still update those units with no additional fees as all. If you or your client wants/needs those devices updated then they should be happy to only having to pay for your service call!

    @N8LBV:

    Actually I've installed a number of these in the field, so I expect I'll see this problem on all of them.

    Correct.

    @N8LBV:

    … I'm not familiar with doing a clean install ... I'm guessig it's not easy and requires special partitioning/install uptions ...
    ... could result in a bricked device if I donlt know exactly what I'm doing ...

    If you installed 'a number' of those units then it's considered good practice to have such a units available to you. And be it only for the sake of testing and checking things out. That's what I would expect from someone who sold them to me at least.

    @N8LBV:

    Reinstalling from scratch is not an easy or affordable option to the client.
    This is a PFSEnse preinstalled/flashed system I'm not familiar with doing a clean install on one of their devices

    -Save your current config.xml on your PC (aka make a backup from it, which you should do anyways).
    -Get the current pfSense version and flash it to a USB stick.
    -Boot from that stick, install pfSense from scratch.
    -put your config.XML on another USB stick and insert it into your VK-T40E
    -reboot the device

    You should be up and running after another reboot.

    Something like that is best checked with your local system.  ;)

    Apart from that, why don't you just stay on 2.3.5 with NanoBSD? It will be maintained for about a year or so. There's nothing bad with that version.
    You have a year now to decide how to serve your clients in the future.
    Either pay them a visit or get another of those VK-T40E units, update it locally and ship it to the clients in a round-robin way.
    This is called service and can be billed for. Absolutely nothing wrong about that!



  • :D
    @N8LBV will smile now ^^



  • Thank you for all of your time and help.
    I am gathering both a fresh install are needed and that
    it will actually install on this hardware from USB stick without issues then I can write the backed up config back to it.
    And I have about a year to get it done. 
    It's inconvenient and annoying that PFSEnse didn't provide a way to update this device to 2.4 that they sold, completely via the network.
    Nor do they seem to spell this out clearly anywhere that I could find, I had to come here and ask.
    I realize support has to eventually end but I feel this is a bit too soon.
    I have a number of other PFSense devices out in the field that I have built and support myself very successfully over the years.
    I went through a phase 2 years ago where I was really busy and thought I'd try a batch of deployments with PFSense official sold and supported hardware rather than build them myself.
    Each "official" device I have had my clients purchase came with a year of support which I have never really used other than a couple quick out of the box email questions. 
    Yes this is going to be billable work for my clients I'm not complaining about that but I do my best to do things in their best interest.
    In future I'm going to continue with my own hardware designs and selections and just pay for per incident or per device support when the need arises.
    I think that approach will work well for me.

    Again Thanks. 
    I will also share my experience and opinions expressed here wit hte PFSense support team.

    Steve



  • @N8LBV:

    …It's inconvenient and annoying that PFSEnse didn't provide a way to update this device to 2.4...

    "Interesting" view.
    If you don't want a fresh install then just stick with the 2.3.x branch. That's what it's there for.
    Your VK-T40E (aka PC Engines APU) will be 4 years old when the 2.3.x branch will cease. That's 4 years in computer technology.
    And then your device still isn't EOL but with a simple reinstall you can use current code. Changing the storage device after 4 years of use doesn't seem completely absurd either. So replace it with an mSATA, reinstall and you're good to go. Without spending a dime for the software update. (I never get a free refill at Starbucks even though I own the mug already…)

    It seems people just have to complain about something.

    @N8LBV:

    …Nor do they seem to spell this out clearly anywhere that I could find,...

    Did you read these?
    https://www.netgate.com/blog/further-a-roadmap-for-pfsense.html
    https://www.netgate.com/blog/pfsense-2-5-and-aes-ni.html
    https://www.netgate.com/blog/more-on-aes-ni.html

    Seems like the 2.5 branch will not make it onto your VK-T40E/APU devices because the AMD CPU does not support the then required AES-NI. APU2 does. Blame that on the pfSense development, on AMD or the fact that this hardware just had its time?

    BTW:
    I swap out cars faster than you do with your security hardware.
    In fact, I've never gotten a software update for my car that fixed obvious bugs, let alone bring new features. Will have to buy a new model to get Apple's CarPlay finally, even though a software update would do.


  • Netgate Administrator

    Just to be clear here the VK-T40E will run 2.4.X no problem. I have one here doing just that.

    You cannot upgrade to it directly from a NanoBSD image as Nano was discontinued in 2.3.X as others have pointed out. You can install 2.4.2 fresh and restore your config into it though it should be a simple process.

    You might choose to upgrade it to an mSATA SSD or do a full install to the SD card. If you do the latter be sure to install without a SWAP slice and to set /var and /tmp to RAM drives after first booting.

    Steve


Log in to reply