M1n1wall upgrade from 2.1p1-RELEASE quietly fails
-
I tried automatic and manual upgrade to the latest version "latest-nanobsd-4g.img.gz", whatever version that is I don't know. It goes through what seems to be a successful upgrade, but the version stays the same. I saw in other posts the suggestion to check free space and the log. It looks like I have free space (df -h below), and no extra packages are installed. There are some errors in the install log (attached), but I can't make sense out of them. The last upgrade I did almost a year ago also failed quietly, and I think that changing the download URL (per Netgate support) may have fixed that but my notes aren't clear. I no longer have any support from Netgate.
Thanks for any suggestions.
A new version is now available
Current version: 2.1p1-RELEASE
NanoBSD Size : 4g
Built On: Tue Nov 12 17:54:26 EST 2013
New version: Mon Aug 25 23:25:10 EDT 2014Update source: https://firmware.netgate.com/auto-update/m1n1wall/
$ df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/ufs/pfsense1 1.8G 149M 1.5G 9% /
devfs 1.0k 1.0k 0B 100% /dev
/dev/ufs/cf 49M 3.6M 41M 8% /cf
/dev/md0 38M 130k 35M 0% /tmp
/dev/md1 57M 17M 35M 33% /var
devfs 1.0k 1.0k 0B 100% /var/dhcpd/dev[upgrade log.txt](/public/imported_attachments/1/upgrade log.txt)
-
I also tried the update at https://firmware.netgate.com/auto-update/m1n1wall.old/netgate-2.1.2-RELEASE-4g-i386-nanobsd-20140410-0519.m1n1wall.upgrade.img.gz, which looks like it is v2.1.2 for my i386. Same quiet failure. The system reboots about 30 minutes after starting the upgrade, leaving it at the original firmware version from before the upgrade. Part of the "upgrade log" below.
P/O upgrade log:
NanoBSD upgrade starting
dd if=/dev/zero of=/dev/ad0s1 bs=1m count=1
1+0 records in
1+0 records out
1048576 bytes transferred in 0.145711 secs (7196275 bytes/sec)/usr/bin/gzip -dc /root/firmware.tgz | /bin/dd of=/dev/ad0s1 obs=64k
3844449+0 records in
30034+1 records out
1968357888 bytes transferred in 353.819261 secs (5563173 bytes/sec)
After upgrade fdisk/bsdlabel/sbin/fsck_ufs -y /dev/ad0s1a
** /dev/ad0s1a
** Last Mounted on /tmp/netgatemnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
5506 files, 317470 used, 3462558 free (542 frags, 432752 blocks, 0.0% fragmentation)***** FILE SYSTEM IS CLEAN *****
/sbin/tunefs -L pfSense0 /dev/ad0s1a
Checking for post_upgrade_command…
Found post_upgrade_command, executing (pfSense0)...
tar: Failed to set default locale
Checking for /tmp/pfSense0/tmp/post_upgrade_command.php...
Running /tmp/pfSense0/tmp/post_upgrade_command.php pfSense0
Adding serial port settings (/tmp/pfSense0)...
Reading /tmp/pfSense0/boot/loader.conf.../dev/ufs/pfSense0 / ufs ro,sync,noatime 1 1
/dev/ufs/cf /cf ufs ro,sync,noatime 1 1gpart set -a active -i 1 ad0
gpart: table 'ad0' is corrupt: Operation not permitted/usr/sbin/boot0cfg -s 1 -v /dev/ad0
# flag start chs type end chs offset size
1 0x00 0: 1: 1 0xa5 751: 15:63 63 3854529
2 0x80 752: 1: 1 0xa5 479: 15:63 3854655 3854529
3 0x00 480: 0: 1 0xa5 581: 15:63 7709184 102816version=2.0 drive=0x80 mask=0x3 ticks=182 bell=# (0x23)
options=packet,update,nosetdrv
volume serial ID 9090-9090
default_selection=F1 (Slice 1)
Wed Dec 10 11:29:23 UTC 2014NanoBSD Firmware upgrade is complete. Rebooting in 10 seconds.
-
Looks like you might be stuck in geom hell! As far as I know there is no way to recover from it other than re-flashing the card. That's not difficult though, if you have a CF card reader, and you can restore your config afterwards. I could be wrong. Have a read through the relevant thread:
https://forum.pfsense.org/index.php?topic=75069.60Steve
-
Steve, Thanks. That looks to be the problem. I will reflash the CF and then reload my configuration onto that.
-
Thanks. Flashing a spare 4 GB Transcend 300x CF to the 2.1.5-RELEASE worked fine. I imported the configuration I had saved before I started, and I was off and running. Two mistakes I made that slowed me down were 1) to forget to expand the image before flashing it, and 2) to flash the upgrade version, when I should have flashed the full install. As a backup during this process, I kept the original Kingston 4 GB 133x CF that shipped with my unit.
