2.0 NanoBSD : any known working version regarding upgrades?



  • Hi,

    Is there a recent NanoBSD version known to have upgrade working? (I am talking upgrading from console or from web app by uploading file, not a one-click upgrade
    I want to put 2.0 in a non-critcal production environnement, but I can't afford to pull out the CF card for every upgrade, I need a bit more ease of use than this.

    *This isn't a complaint, I realize this is beta. Just a question.

    Right now I seem to be stuck on March 22nd version.



  • consider upgrading via web gui by uploading file and for that 11th April nanobsd upgrade snap is the best so far, atleast for me compared to all the older and newer nanobsd upgrade snaps.



  • Thanks.  So I should somehow get to april 11th snap, and then it should be a breeze to upgrade from that point.

    I understood that correctly, right?



  • did u mean to say which snapshot onwards upgrade works on nanobsd?
    if so then it started march onwards

    and if ur looking for the best nanobsd upgrade snapshot then consider 1th april and u can upgrade from any older nanobsd to 11th april nanobsd upgrade snap without any issue, atleast for me and once on 11th april snap, it works smooth



  • I just tried upgrading from April 12th to April 21 using the "upload firmware" screen.  On NanoBSD 2G version.

    I can't say whether it's working because right now my Mozilla screen is still on the "upgrade screen", my serial console tells me there hasn't been a reboot and the file has been transferred about 20 minutes ago.  (could tell from my PC's network utilization).

    How long should I wait before calling this a problem?



  • once upgrade starts, u will see it in the console and once its done successfully, its suppose to reboot



  • Ok, well there you go.  I gave up, used the console, and upgraded "using URL".  Everything seems fine, until it reboots to the good old version.

    See console log:

    Enter the URL to the .tgz update file:

    http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/nanobsd/pfSense-2.0-BETA1-2g-20100421-0506-nanobsd.img.gz

    Fetching file size…

    File size: 166627341

    Fetching file...
    looking up snapshots.pfsense.org
    connecting to snapshots.pfsense.org:80
    requesting http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/nanobsd/pfSense-2.0-BETA1-2g-20100421-0506-nanobsd.img.gz
    remote size / mtime: 166627341 / 1271841173
    /root/firmware.tgz                            100% of  158 MB  996 kBps 00m00s

    Fetching MD5...
    looking up snapshots.pfsense.org
    connecting to snapshots.pfsense.org:80
    requesting http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/nanobsd/pfSense-2.0-BETA1-2g-20100421-0506-nanobsd.img.gz.md5
    remote size / mtime: 112 / 1271841679
    /root/firmware.tgz.md5                        100% of  112  B  178 kBps
    URL MD5: 99f5a28e4ad255b1798670ebbb8e534e

    Downloaded file MD5: 99f5a28e4ad255b1798670ebbb8e534e

    MD5 checksum matches.
    NanoBSD upgrade file detected...

    WARNING! ACHTUNG! DANGER!

    This image is not digitally signed.

    This means that the image you uploaded is not an official/supported image and
    may lead to unexpected behavior or security compromises.

    Only install images that come from sources that you trust, and make sure
    that the image has not been tampered with.

    Do you want to install this image anyway at your own risk [n]?y

    Continuing upgrade…

    One moment please...

    Broadcast Message from root@pfsense.localdomain
            (no tty) at 12:06 EDT...

    Firmware upgrade in progress...

    ..Done.  Rebooting...

    *** Welcome to pfSense 2.0-BETA1-nanobsd on pfsense ***

    WAN (wan)                -> vr1        -> SOMETHING
      LAN (lan)                -> vr0        -> 192.168.1.1
      OPT1 (opt1)              -> vr2        -> NONE

    pfSense console setup


    0)  Logout (SSH only)
    1)  Assign Interfaces
    2)  Set interface(s) IP address
    3)  Reset webConfigurator password
    4)  Reset to factory defaults
    5)  Reboot system
    6)  Halt system
    7)  Ping host
    8)  Shell
    9)  PFtop
    10)  Filter Logs
    11)  Restart webConfigurator
    12)  pfSense Developer Shell
    13)  Upgrade from console
    14)  Enable Secure Shell (sshd)

    Enter an option:
    *** FINAL System shutdown message from root@pfsense.localdomain ***
    System going down IMMEDIATELY

    pfSense is now shutting down ...

    Waiting (max 60 seconds) for system process vnlru' to stop...done Waiting (max 60 seconds) for system processbufdaemon' to stop...done
    Waiting (max 60 seconds) for system process `syncer' to stop...
    Syncing disks, vnodes remaining...0 0 done
    All buffers synced.
    Uptime: 4m7s
    Rebooting...
    PC Engines ALIX.2 v0.99h
    640 KB Base Memory
    261120 KB Extended Memory

    01F0 Master 848A SanDisk SDCFH-002G
    Phys C/H/S 3897/16/63 Log C/H/S 974/64/63

    1  pfSense
    2  pfSense

    F6 PXE
    Boot:  2
    /boot.config:  -h
    Consoles: serial port
    BIOS drive C: is disk0
    BIOS 640kB/261120kB available memory

    FreeBSD/i386 bootstrap loader, Revision 1.1
    (ermal@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org, Mon Apr 12 18:33:08 EDT 2010)
    …..

    What am I doing wrong? Seems simple enough p upgrade, and I seem to be the only one seeing this.



  • thats bcoz u didnt use the nanobsd upgrade images



  • u need to upgrade using the nanobsd upgrade images from this location
    http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/



  • Ok, that sort of makes sense. So, just for my own education, whats the conceptual difference between an upgrade image and the original "install" image?



  • for that only the developers might be able to give u a clear difference but what i know is u need to use the upgrade images to upgrade as the difference might be something related to the slices



  • Doesnt seem to be working with the Update files. I get this in my upgrade log (NanoBSD page in pfSense).

    I have a 2GB CF card, and am using the 2GB update file now.

    File list:

    Warning: file_get_contents(/conf/file_upgrade_log.txt): failed to open stream: No such file or directory in /usr/local/www/diag_nanobsd.php on line 272

    Misc log:

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

    fdisk/bsdlabel log:

    I am at a loss, all I want is to get on the train and be able to update when needed.  This is my console log from the update:
    Enter the URL to the .tgz update file:

    http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/pfSense-2.0-BETA1-2g-20100421-0506-nanobsd-upgrade.img.gz

    Fetching file size…

    File size: 83266369

    Fetching file...
    looking up snapshots.pfsense.org
    connecting to snapshots.pfsense.org:80
    requesting http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/pfSense-2.0-BETA1-2g-20100421-0506-nanobsd-upgrade.img.gz
    remote size / mtime: 83266369 / 1271841368
    /root/firmware.tgz                            100% of  79 MB  937 kBps 00m00s

    Fetching MD5...
    looking up snapshots.pfsense.org
    connecting to snapshots.pfsense.org:80
    requesting http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/pfSense-2.0-BETA1-2g-20100421-0506-nanobsd-upgrade.img.gz.md5
    remote size / mtime: 127 / 1271841681
    /root/firmware.tgz.md5                        100% of  127  B  199 kBps
    URL MD5: 3dffbcd9f16f45c6d4a42e87653eb4eb

    Downloaded file MD5: 3dffbcd9f16f45c6d4a42e87653eb4eb

    MD5 checksum matches.
    NanoBSD upgrade file detected...

    WARNING! ACHTUNG! DANGER!

    This image is not digitally signed.

    This means that the image you uploaded is not an official/supported image and
    may lead to unexpected behavior or security compromises.

    Only install images that come from sources that you trust, and make sure
    that the image has not been tampered with.

    Do you want to install this image anyway at your own risk [n]?y

    Continuing upgrade…

    One moment please...

    Broadcast Message from root@pfsense.localdomain
            (no tty) at 13:38 EDT...

    Firmware upgrade in progress...

    Done.  Rebooting...


  • Rebel Alliance Developer Netgate

    @Mike:

    Ok, that sort of makes sense. So, just for my own education, whats the conceptual difference between an upgrade image and the original "install" image?

    The original image consists of three slices (sort of like partitions):

    • pfsense0
    • pfsense1
    • cf

    These are two system images, and the config slice, plus the bits at the start of the image which make the whole thing bootable, etc.

    An upgrade image is just one of the system slices, i.e. pfsense0/pfsense1, which is all that should get overwritten during the upgrade.

    I haven't heard anything about NanoBSD upgrades working in a while. I haven't tried on my ALIX in quite some time as I had it running 1.2.3 for some other work I was doing. I have a couple NanoBSD virtual machine setup so I may see if I can reproduce this.



  • Hey guys,

    sorry to 'hijack' this thread, but what about the newest may builds? Are they as stable as the 11th april build?

    Thanks

    Jimmy


Log in to reply