Actions
Bug #1377
closed
upgrade 1.2.3-Final nanobsd 4g to 2.0-RC1 nanobsd 4gb fails
Start date:
03/22/2011
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
Description
I tried the image pfSense-2.0-RC1-4g-i386-20110226-1633-nanobsd-upgrade.img.gz through the WebGUI and the following information is given in the slice upgrade log
Misc log:
mkdir: /tmp/pfsense1: File exists
mount: /dev/ufs/pfsense1 : Operation not permitted
cp: /tmp/pfsense1/etc/fstab: No such file or directory
sed: /tmp/pfsense1/etc/fstab: No such file or directory
umount: /tmp/pfsense1: not a file system root directory
fdisk/bsdlabel log:
System Log Alert:
27 - [UpgradeFailure]Something went wrong when trying to update the fstab entry. Aborting upgrade
Updated by Bill McIlhargey about 13 years ago
Here is the post discussing this further
Updated by Chris Buechler about 13 years ago
- Category set to Upgrade
- Target version set to 2.0
Updated by Bill McIlhargey about 13 years ago
ran the following command in the console and tried upgrading to the 2.0 nanobsd 4gb rc1
tail -f /cf/conf/upgrade_log.txt
NanoBSD Firmware upgrade in progress...
Broadcast Message from root@[hidden]
(no tty) at 22:19 EDT...
NanoBSD Firmware upgrade in progress...
Installing /root/firmware.tgz.
Broadcast Message from root@[hidden]
(no tty) at 22:19 EDT...
Installing /root/firmware.tgz.
SLICE 2
OLDSLICE 1
TOFLASH ad0s2
COMPLETE_PATH ad0s2a
GLABEL_SLICE pfsense1
Fri Mar 25 22:19:26 EDT 2011
total 7
dr-xr-xr-x 7 root wheel 512 Feb 18 11:30 .
drwxr-xr-x 23 root wheel 512 Feb 18 11:30 ..
crw-r----- 1 root operator 0, 63 Feb 18 11:33 ad0
crw-r----- 1 root operator 0, 65 Feb 18 11:33 ad0s1
crw-r----- 1 root operator 0, 68 Feb 18 11:33 ad0s1a
crw-r----- 1 root operator 0, 69 Feb 18 11:33 ad0s1c
crw-r----- 1 root operator 0, 66 Mar 21 17:13 ad0s2
crw-r----- 1 root operator 0, 123 Mar 21 17:13 ad0s2a
crw-r----- 1 root operator 0, 124 Feb 18 11:33 ad0s2c
crw-r----- 1 root operator 0, 67 Feb 18 11:33 ad0s3
crw------- 1 root operator 0, 25 Feb 18 11:33 ata
crw------- 1 root wheel 0, 72 Feb 18 11:30 bpf0
crw------- 1 root wheel 0, 74 Feb 18 11:30 bpf1
crw------- 1 root wheel 0, 83 Feb 18 11:33 bpf2
crw------- 1 root wheel 0, 88 Mar 25 20:25 bpf3
crw------- 1 root tty 0, 10 Mar 25 22:19 console
crw-rw-rw- 1 root wheel 0, 51 Feb 18 11:30 crypto
crw-rw-rw- 1 root wheel 0, 11 Feb 18 11:33 ctty
crw-rw---- 1 uucp dialer 0, 41 Feb 18 11:33 cuad0
crw-rw---- 1 uucp dialer 0, 42 Feb 18 11:33 cuad0.init
crw-rw---- 1 uucp dialer 0, 43 Feb 18 11:33 cuad0.lock
crw-rw---- 1 uucp dialer 0, 47 Feb 18 11:33 cuad1
crw-rw---- 1 uucp dialer 0, 48 Feb 18 11:33 cuad1.init
crw-rw---- 1 uucp dialer 0, 49 Feb 18 11:33 cuad1.lock
crw------- 1 root wheel 0, 5 Feb 18 11:33 devctl
cr-------- 1 root wheel 0, 62 Feb 18 11:33 devstat
dr-xr-xr-x 2 root wheel 512 Feb 18 11:33 fd
crw------- 1 root wheel 0, 12 Feb 18 11:33 fido
crw-r----- 1 root operator 0, 4 Feb 18 11:33 geom.ctl
crw------- 1 root wheel 0, 22 Feb 18 11:33 io
crw------- 1 root wheel 0, 7 Feb 18 11:33 klog
crw-r----- 1 root kmem 0, 21 Feb 18 11:33 kmem
dr-xr-xr-x 2 root wheel 512 Feb 18 11:33 led
crw-r----- 1 root operator 0, 81 Feb 18 11:30 md0
crw-r----- 1 root operator 0, 82 Feb 18 11:30 md1
crw------- 1 root wheel 0, 61 Feb 18 11:33 mdctl
crw-r----- 1 root kmem 0, 20 Feb 18 11:30 mem
dr-xr-xr-x 2 root wheel 512 Feb 18 11:33 net
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net1 -> net/vr0
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net10 -> net/ng2
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net11 -> net/ng3
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net12 -> net/ng4
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net13 -> net/ng5
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net14 -> net/ng6
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net15 -> net/ng7
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net16 -> net/ng8
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net17 -> net/ng9
lrwxr-xr-x 1 root wheel 8 Feb 18 11:33 net18 -> net/ng10
lrwxr-xr-x 1 root wheel 8 Feb 18 11:33 net19 -> net/ng11
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net2 -> net/vr1
lrwxr-xr-x 1 root wheel 8 Feb 18 11:33 net20 -> net/ng12
lrwxr-xr-x 1 root wheel 8 Feb 18 11:33 net21 -> net/ng13
lrwxr-xr-x 1 root wheel 8 Feb 18 11:33 net22 -> net/ng14
lrwxr-xr-x 1 root wheel 8 Feb 18 11:33 net23 -> net/ng15
lrwxr-xr-x 1 root wheel 8 Feb 18 11:33 net24 -> net/ng16
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net3 -> net/vr2
lrwxr-xr-x 1 root wheel 8 Feb 18 11:33 net4 -> net/enc0
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net5 -> net/lo0
lrwxr-xr-x 1 root wheel 11 Feb 18 11:33 net6 -> net/pfsync0
lrwxr-xr-x 1 root wheel 10 Feb 18 11:33 net7 -> net/pflog0
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net8 -> net/ng0
lrwxr-xr-x 1 root wheel 7 Feb 18 11:33 net9 -> net/ng1
crw------- 1 root wheel 0, 3 Feb 18 11:33 network
crw------- 1 root wheel 0, 50 Feb 18 11:33 nfs4
crw------- 1 root kmem 0, 13 Feb 18 11:33 nfslock
crw-rw-rw- 1 root wheel 0, 23 Mar 25 22:19 null
crw-r--r-- 1 root wheel 0, 6 Feb 18 11:33 pci
crw-rw---- 1 proxy proxy 0, 52 Feb 18 11:33 pf
crw-rw-rw- 1 root wheel 0, 126 Mar 25 22:09 ptyp0
crw-rw-rw- 1 root wheel 0, 8 Feb 18 11:30 random
lrwxr-xr-x 1 root wheel 4 Feb 18 11:33 stderr -> fd/2
lrwxr-xr-x 1 root wheel 4 Feb 18 11:33 stdin -> fd/0
lrwxr-xr-x 1 root wheel 4 Feb 18 11:33 stdout -> fd/1
crw------- 1 root wheel 0, 38 Feb 18 11:33 ttyd0
crw------- 1 root wheel 0, 39 Feb 18 11:33 ttyd0.init
crw------- 1 root wheel 0, 40 Feb 18 11:33 ttyd0.lock
crw------- 1 root wheel 0, 44 Feb 18 11:33 ttyd1
crw------- 1 root wheel 0, 45 Feb 18 11:33 ttyd1.init
crw------- 1 root wheel 0, 46 Feb 18 11:33 ttyd1.lock
crw-rw-rw- 1 root wheel 0, 127 Mar 25 22:08 ttyp0
dr-xr-xr-x 2 root wheel 512 Feb 18 11:33 ufs
dr-xr-xr-x 2 root wheel 512 Feb 18 11:33 ufsid
lrwxr-xr-x 1 root wheel 6 Feb 18 11:33 urandom -> random
crw-rw---- 1 root operator 0, 36 Feb 18 11:33 usb
crw-rw---- 1 root operator 0, 35 Feb 18 11:33 usb0
crw-rw---- 1 root operator 0, 37 Feb 18 11:33 usb1
crw------- 1 root operator 0, 64 Feb 18 11:33 xpt0
crw-rw-rw- 1 root wheel 0, 24 Feb 18 11:33 zero
-rw------- 1 root wheel 66M Mar 25 22:18 /root/firmware.tgz
MD5 (/root/firmware.tgz) = b16d11dec26a2c308b3ff48553ee6982
/dev/ufs/pfsense1 on / (ufs, local)
devfs on /dev (devfs, local)
/dev/md0 on /var/tmp (ufs, local)
/dev/md1 on /var (ufs, local)
/dev/ufs/cf on /cf (ufs, local)
devfs on /var/dhcpd/dev (devfs, local)
last pid: 58161; load averages: 1.92, 0.98, 0.49 up 35+09:46:44 22:19:30
40 processes: 1 running, 37 sleeping, 2 zombie
Mem: 64M Active, 108M Inact, 30M Wired, 5008K Cache, 34M Buf, 31M Free
Swap:
PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND
1371 root 1 8 20 8612K 6424K wait 401:28 0.00% sh
17265 nobody 1 44 0 3156K 1320K select 38:27 0.00% dnsmasq
482 root 1 44 0 3268K 1036K select 13:07 0.00% syslogd
711 root 1 4 0 23692K 21692K kqread 7:31 0.00% lighttpd
507 root 1 -8 0 3156K 696K piperd 5:13 0.00% logger
506 root 1 -58 0 8788K 6064K bpf 4:30 0.00% tcpdump
28795 root 1 44 0 7140K 5480K select 3:13 0.00% bsnmpd
15519 root 1 44 0 5736K 3120K select 1:39 0.00% racoon
1148 root 1 44 0 3188K 1080K select 1:27 0.00% miniupnpd
17290 dhcpd 1 44 0 3156K 2120K select 0:52 0.00% dhcpd
379 _dhcp 1 44 0 3156K 1228K select 0:38 0.00% dhclient
729 root 1 4 0 45832K 15512K sbwait 0:34 0.00% php
460 _dhcp 1 44 0 3156K 1228K select 0:30 0.00% dhclient
719 root 1 4 0 43784K 13512K accept 0:29 0.00% php
598 root 1 44 0 3268K 1344K select 0:29 0.00% inetd
46507 _ntp 1 44 0 3156K 1180K select 0:28 0.00% ntpd
1154 root 1 8 0 3240K 1228K nanslp 0:21 0.00% cron
388 root 1 44 0 5064K 2312K select 0:15 0.00% sshd
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.470123 secs (2230430 bytes/sec)
/usr/bin/gzip -dc /root/firmware.tgz | /bin/dd of=/dev/ad0s2 obs=64k
Updated by Bill McIlhargey about 13 years ago
3860985+1049 records in 30168+1 records out 1977131520 bytes transferred in 909.923640 secs (2172854 bytes/sec) After upgrade fdisk/bsdlabel /sbin/fsck_ufs -y /dev/ad0s2a ** /dev/ad0s2a ** Last Mounted on /tmp/builder/_.mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 5912 files, 279205 used, 3517959 free (639 frags, 439665 blocks, 0.0% fragmentation) /sbin/tunefs -L pfsense1 /dev/ad0s2a
the above was the rest of the file when the upgrade failed
Updated by Jim Pingle almost 13 years ago
Is this specific to the 4GB size? I just did a manual update of a 1GB system and it had no problems upgrading that I could see, though it has been tracking snapshots and wasn't an upgrade from RC1.
Updated by Bill McIlhargey almost 13 years ago
4GB
I worked around this by physically going to the unit and reload the card with a 4G 2-RC1 image.
Updated by Jim Pingle over 12 years ago
- Status changed from New to Feedback
This works fine for me. Imaged a CF with 1.2.3 4GB, configured it, ran for a bit, then upgraded to a current 2.0 snapshot. Upgrade file uploaded, wrote, applied, rebooted, etc. Booted up to 2.0-RC3 without any problems.
If there is a problem you may want to rule out a physical problem with your CF first. The most common failures so far seem to be:- Uploading a full image instead of an upgrade image
- Uploading the wrong size image
- CF failures that lead of errors during the upgrade process
Updated by Chris Buechler over 12 years ago
- Status changed from Feedback to Closed
Actions