Manual Update Stuck



  • hi there

    i have the nanobsd 1GB version running, snapshot 13 juli something. ive tried to upload manual the update file pfSense-1.2.3-1g-20090730-2309-nanobsd-upgrade.img.gz wich has worked. now the box is stucked on the 
      An upgrade is currently in progress.

    The firewall will reboot when the operation is complete.

    screen with the harddisk image. i can not access any menu and reboot the system per remote.
    also there raised an alarm, that the disk was to small and the update was halted.  is it not possible to update 1GB flash version? do i need 2GB or 4GB?



  • I had the same problem flashing nanobsd by WebUI.

    As my router was still responding on ssh and the top command didn't show any active flash write jobs, I rebooted the device via ssh
    and then used ssh again to console flash from url. this has worked fine several times now.



  • Just tried web upgrade on ALIX 2d3 w/4GB flash card.  I got this on the console:

    
    Firmware upgrade in progress...
    
    pid 286 (sshlockout_pf), uid 0: exited on signal 11
    pid 344 (tcpdump), uid 0: exited on signal 11
    pflog0: promiscuous mode disabled
    pid 345 (logger), uid 0: exited on signal 11
    pid 463 (lighttpd), uid 0: exited on signal 11
    pid 958 (sh), uid 0: exited on signal 11
    pid 808 (check_reload_status), uid 0: exited on signal 11 (core dumped)
    pid 1769 (sh), uid 0: exited on signal 11
    pid 790 (cron), uid 0: exited on signal 11 (core dumped)
    pid 534 (dnsmasq), uid 65534: exited on signal 11
    pid 281 (mpd), uid 0: exited on signal 11 (core dumped)
    pid 785 (miniupnpd), uid 0: exited on signal 11
    pid 810 (minicron), uid 0: exited on signal 11
    pid 765 (dhcpd), uid 1002: exited on signal 11
    
    pid 889 (sh), uid 0: exited on signal 11
    pid 888 (sh), uid 0: exited on signal 11
    pid 884 (login), uid 0: exited on signal 11
    
    

    Then it hung forever.



  • @FooFighter:

    I had the same problem flashing nanobsd by WebUI.

    As my router was still responding on ssh and the top command didn't show any active flash write jobs, I rebooted the device via ssh
    and then used ssh again to console flash from url. this has worked fine several times now.

    hi

    ive tried to do the local update, with serial console attached. tried to download it from url and mount the filesystem in rw mode and download it to /root and put in the path in the updater. always the same. disk size is to small to update….
    update not working on 1GB flash cards?



  • when I use update from url via ssh my router is connected to the internet and I only paste in the url to the image

    for example
    http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/updates/pfSense-1.2.3-512mb-20090722-0531-nanobsd-upgrade.img.gz

    then pfsense starts the download and after that checks the md5 value. If everything is fine it starts to flash.



  • Upgrade of nanobsd from 0731 to 0803 failed.  Contents of /cf/conf/upgrade_log.txt:

    
    NanoBSD Firmware upgrade in progress...
    
    Installing /root/latest.tgz.
    Installing /root/latest.tgz.
    SLICE 2
    OLDSLICE 1
    TOFLASH ad0s2
    COMPLETE_PATH ad0s2a
    GLABEL_SLICE pfsense1
    Mon Aug  3 20:16:57 PDT 2009
    
    total 7
    dr-xr-xr-x   7 root   wheel          512 Dec 31  1999 .
    drwxr-xr-x  23 root   wheel          512 Dec 31  1999 ..
    crw-r-----   1 root   operator    0,  64 Aug  2 20:25 ad0
    crw-r-----   1 root   operator    0,  65 Aug  2 20:25 ad0s1
    crw-r-----   1 root   operator    0,  68 Aug  2 20:25 ad0s1a
    crw-r-----   1 root   operator    0,  69 Aug  2 20:25 ad0s1c
    crw-r-----   1 root   operator    0,  66 Aug  2 20:25 ad0s2
    crw-r-----   1 root   operator    0,  70 Aug  2 20:25 ad0s2a
    crw-r-----   1 root   operator    0,  71 Aug  2 20:25 ad0s2c
    crw-r-----   1 root   operator    0,  67 Aug  2 20:25 ad0s3
    crw-------   1 root   operator    0,  25 Aug  2 20:25 ata
    crw-------   1 root   wheel       0,  84 Aug  2 20:25 bpf0
    crw-------   1 root   wheel       0,  89 Aug  3 20:02 bpf1
    crw-------   1 root   tty         0,  10 Aug  3 20:16 console
    crw-rw-rw-   1 root   wheel       0,  51 Dec 31  1999 crypto
    crw-rw-rw-   1 root   wheel       0,  11 Aug  2 20:25 ctty
    ...skipping...
      496 root        1   4    0 41740K 16104K accept   0:19  0.00% php
    29026 root        1   8   20  3156K   796K nanslp   0:13  0.00% check_reload_status
      549 nobody      1  44    0  3156K  1328K select   0:07  0.00% dnsmasq
      493 root        1   4    0 44812K 17996K accept   0:05  0.00% php
      478 root        1   4    0  5136K  2836K kqread   0:04  0.00% lighttpd
      286 root        1  44    0  4664K  1904K select   0:02  0.00% mpd
      359 root        1 -58    0  5724K  2188K bpf      0:02  0.00% tcpdump
      803 root        1  44    0  3188K  1152K select   0:02  0.00% miniupnpd
      632 _ntp        1  44    0  3156K  1228K select   0:01  0.00% ntpd
      264 root        1  44    0  3268K  1120K select   0:01  0.00% syslogd
      805 root        1   8    0  3240K  1304K nanslp   0:01  0.00% cron
      781 dhcpd       1  44    0  3156K  2164K select   0:00  0.00% dhcpd
      360 root        1  -8    0  3156K   768K piperd   0:00  0.00% logger
      825 root        1   8    0  3156K   904K nanslp   0:00  0.00% minicron
      633 root        1  44    0  3156K  1240K select   0:00  0.00% ntpd
     4463 root        1  44    0  7784K  3364K select   0:00  0.00% sshd
      479 root        1   8    0 39692K  5020K wait     0:00  0.00% php
    
    NanoBSD upgrade starting
    
    dd if=/dev/zero of=/dev/ad0s2 bs=1m count=1
    1+0 records in
    1+0 records out
    1048576 bytes transferred in 0.444509 secs (2358953 bytes/sec)
    
    /usr/bin/gzip -dc /root/latest.tgz | /bin/dd of=/dev/ad0s2 obs=64k
    191654+819 records in
    1501+1 records out
    98416640 bytes transferred in 26.344876 secs (3735703 bytes/sec)
    After upgrade fdisk/bsdlabel
    
    /sbin/fsck_ufs -y /dev/ad0s2a
    Can't stat /dev/ad0s2a: No such file or directory
    Can't stat /dev/ad0s2a: No such file or directory
    
    /sbin/tunefs -L pfsense1 /dev/ad0s2a
    tunefs: /dev/ad0s2a: could not find special device
    
    

    After the failed upgrade attempt, a few lines of "ls -l /dev":

    
    spanky:/dev#  ls -l
    total 3
    crw-r-----  1 root   operator    0,  64 Aug  3 20:31 ad0
    crw-r-----  1 root   operator    0,  65 Aug  3 20:31 ad0s1
    crw-r-----  1 root   operator    0,  68 Aug  3 20:31 ad0s1a
    crw-r-----  1 root   operator    0,  69 Aug  3 20:31 ad0s1c
    crw-r-----  1 root   operator    0,  66 Aug  3 20:31 ad0s2
    crw-r-----  1 root   operator    0,  67 Aug  3 20:31 ad0s3
    crw-------  1 root   operator    0,  25 Aug  3 20:31 ata
    crw-------  1 root   wheel       0,  81 Aug  3 20:31 bpf0
    crw-------  1 root   wheel       0,  86 Aug  3 20:33 bpf1
    crw-------  1 root   tty         0,  10 Aug  3 20:32 console
    crw-rw-rw-  1 root   wheel       0,  51 Aug  3 20:31 crypto
    crw-rw-rw-  1 root   wheel       0,  11 Aug  3 20:31 ctty
    
    


  • I also have problems now updating my nanobsd system via ssh / update from url.

    tested with - 7./8. August 09 - 512 MB nanobsd images

    Download works fine, md5sum ok but then I get the following message in my system log

    php: : New alert found: Upgrade failed due to the upgrade image being larger than the partition that is configured on disk. Halting.

    this is strange as I started with a 512 MB nanobsd full install on my alix and recently only used 512 MB images for upgrades - without any problems.

    ## Update ##
    I replaced the rc.firmware file on the router with the latest from cvs and did a re-run.

    now the message says:

    php: : New alert found: Upgrade failed due to the upgrade image being larger than the partition that is configured on disk. Halting. 216 < 218

    ??? has the partition size recently changed ???



  • If you download the latest 512MB nanobsd upgrade image and "gunzip" it, how big is it?



  • latest image:
    pfSense-1.2.3-512mb-20090811-0539-nanobsd-upgrade.img.gz
    md5sum 3999d33051b99f743455f64ea536b07e - ok

    file: pfSense-1.2.3-512mb-20090811-0539-nanobsd-upgrade.img

    output of the windows explorer:
    size 218 MB (229.630.464 Bytes)
    size on device 218 MB (229.634.048 Bytes)

    update:
    php: : New alert found: Upgrade failed due to the upgrade image being larger than the partition that is configured on disk. Halting. 216 < 218

    if the size of the slices has recently changed from 216 to 218, is there a way to extend this slice to the new size?



  • Don't know the answer to that. I suppose you could save off /cf/conf and reinstall. I agree this shouldn't be necessary but perhaps the 512 slice size increased recently.



  • Actually it's no big deal unscrewing my alix and reflashing my cf by PC as I always keep backups of my configuration. I was just happy that this way of updating seemed to be over – not right now as it turned out.



  • Try to reflash from scratch, then attempt another update when a new snapshot is available.  I've been having 100% success applying the nanobsd updates manually to my 2GB card.


Log in to reply