NanoBSD: still can't upgrade from console



  • Here is a snipet of my NanoBSD upgrade log, upgrading from April 23rd to April 24th snapshop of the 2G version of NanoBSD. Upgrading from console by URL, with the .gz file located on the snapshot server (does the console expect a .tgz instead?)

    /tmp/pfsense1/nano/base
    /tmp/pfsense1/nano/base/etc
    /tmp/pfsense1/nano/base/etc/md_size
    /tmp/pfsense1/nano/base/var
    /tmp/pfsense1/nano/base/var/md_size
    /tmp/pfsense1/nano/default
    /tmp/pfsense1/nano/default/etc
    /tmp/pfsense1/nano/default/etc/remount

    Misc log:

    tar: Unrecognized archive format
    tar: Error exit delayed from previous errors.
    shutdown: [pid 11107]

    fdisk/bsdlabel log:

    This is a pain because it keeps me from staying current on the Beta versions and trying it in semi-production, reporting bugs.

    It's also not reliably upgrading from the web UI, but the console should reliably do this.


  • Rebel Alliance Developer Netgate

    There are several outstanding issues when upgrading NanoBSD but I haven't had a chance to even try reproducing them myself.

    It shouldn't actually have files in that image it downloads. the upgrade .img.gz should be written to the alternate slice with dd, not tar.



  • If you need access to my box for testing, Ill be glad to give it. Its not being used in any way.  I imagine upgrade problems would be a priority since it helps beta testers stay current and report bugs.


  • Rebel Alliance Developer Netgate

    I have a few nanobsd VMs setup in VMware workstation, so access isn't my issue, it's having the time to do it. :)



  • Thanks, if you need any particular test let me know, I'll be glad to help.


Log in to reply