Fail to upgrade 2.3_1 to 2.3.1
-
Hi, All
I tried to upgrade my pfsense but always failed. Here is the install log, How can I resove it.
Any help would be appreciated.
–-
Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
**** WARNING ****
Duplicate slice required!!Before starting the upgrade process, the currently mounted nanobsd partition
needs to be cloned to the secondary partition, where the update will happenAfter installation a reboot will be required to switch partition.
Cleaning secondary partition... done.
Duplicating current slice... done.
Restoring slice label... done.
Testing duplicated partition integrity... done.
Mounting second partition to run upgrade... done.
Unlocking package pfSense-kernel-pfSense_wrap_vga... done.
Downloading upgrade packages...
Updating pfSense-core repository catalogue...
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
Unable to update repository pfSense
All repositories are up-to-date.
Checking for upgrades (61 candidates): .......... done
Processing candidates (61 candidates): .......... done
The following 63 package(s) will be affected (of 0 checked):New packages to be INSTALLED:
uclcmd: 0.1 [pfSense]
libucl: 0.8.0 [pfSense]Installed packages to be UPGRADED:
unbound: 1.5.5 -> 1.5.8 [pfSense]
sqlite3: 3.9.2 -> 3.11.1 [pfSense]
smartmontools: 6.4_1 -> 6.4_2 [pfSense]
rate: 0.9 -> 0.9_1 [pfSense]
python27: 2.7.11_1 -> 2.7.11_2 [pfSense]
php56-zlib: 5.6.20 -> 5.6.21 [pfSense]
php56-xmlwriter: 5.6.20 -> 5.6.21 [pfSense]
php56-xmlreader: 5.6.20 -> 5.6.21 [pfSense]
php56-xml: 5.6.20 -> 5.6.21 [pfSense]
php56-tokenizer: 5.6.20 -> 5.6.21 [pfSense]
php56-sysvshm: 5.6.20 -> 5.6.21 [pfSense]
php56-sysvsem: 5.6.20 -> 5.6.21 [pfSense]
php56-sysvmsg: 5.6.20 -> 5.6.21 [pfSense]
php56-sqlite3: 5.6.20 -> 5.6.21 [pfSense]
php56-sockets: 5.6.20 -> 5.6.21 [pfSense]
php56-simplexml: 5.6.20 -> 5.6.21 [pfSense]
php56-shmop: 5.6.20 -> 5.6.21 [pfSense]
php56-session: 5.6.20 -> 5.6.21 [pfSense]
php56-readline: 5.6.20 -> 5.6.21 [pfSense]
php56-posix: 5.6.20 -> 5.6.21 [pfSense]
php56-pdo_sqlite: 5.6.20 -> 5.6.21 [pfSense]
php56-pdo: 5.6.20 -> 5.6.21 [pfSense]
php56-pcntl: 5.6.20 -> 5.6.21 [pfSense]
php56-openssl: 5.6.20 -> 5.6.21 [pfSense]
php56-opcache: 5.6.20 -> 5.6.21 [pfSense]
php56-mcrypt: 5.6.20 -> 5.6.21 [pfSense]
php56-mbstring: 5.6.20 -> 5.6.21 [pfSense]
php56-ldap: 5.6.20 -> 5.6.21 [pfSense]
php56-json: 5.6.20 -> 5.6.21 [pfSense]
php56-hash: 5.6.20 -> 5.6.21 [pfSense]
php56-gettext: 5.6.20 -> 5.6.21 [pfSense]
php56-filter: 5.6.20 -> 5.6.21 [pfSense]
php56-dom: 5.6.20 -> 5.6.21 [pfSense]
php56-curl: 5.6.20 -> 5.6.21 [pfSense]
php56-ctype: 5.6.20 -> 5.6.21 [pfSense]
php56-bz2: 5.6.20 -> 5.6.21 [pfSense]
php56-bcmath: 5.6.20 -> 5.6.21 [pfSense]
php56: 5.6.20 -> 5.6.21 [pfSense]
pfSense-rc: 2.3 -> 2.3.1 [pfSense-core]
pfSense-kernel-pfSense_wrap_vga: 2.3 -> 2.3.1 [pfSense-core]
pfSense-default-config: 2.3 -> 2.3.1 [pfSense-core]
pfSense-base-nanobsd: 2.3 -> 2.3.1 [pfSense-core]
pfSense-Status_Monitoring: 1.0_1 -> 1.3_1 [pfSense]
pfSense: 2.3_1 -> 2.3.1 [pfSense]
perl5: 5.20.3_8 -> 5.20.3_12 [pfSense]
pecl-zmq: 1.1.3 -> 1.1.3_1 [pfSense]
openvpn: 2.3.9 -> 2.3.11 [pfSense]
nettle: 2.7.1 -> 3.2 [pfSense]
libzmq4: 4.1.3 -> 4.1.4_1 [pfSense]
libsodium: 1.0.3 -> 1.0.8 [pfSense]
libedit: 3.1.20150325_1 -> 3.1.20150325_2 [pfSense]
gmp: 5.1.3_2 -> 5.1.3_3 [pfSense]
glib: 2.44.1_3 -> 2.46.2 [pfSense]
gettext-runtime: 0.19.6 -> 0.19.7 [pfSense]
filterlog: 0.1_1 -> 0.1_2 [pfSense]
dnsmasq-devel: 2.76.0test8 -> 2.76.0test12 [pfSense]
curl: 7.47.0 -> 7.48.0_1 [pfSense]
cpdup: 1.17_2 -> 1.18 [pfSense]
bsnmp-ucd: 0.4.1 -> 0.4.2 [pfSense]Installed packages to be REINSTALLED:
rrdtool-1.5.5_1 [pfSense] (options changed)
nginx-1.8.1,2 [pfSense] (options changed)72 MiB to be downloaded.
Locking package pfSense-kernel-pfSense_wrap_vga… done.
Failed -
"Before starting the upgrade process, the currently mounted nanobsd partition
needs to be cloned to the secondary partition, where the update will happen"=> Go to Diagnostic menu => NanoBSD => Duplicate boot slice - press the green button!
That should work!
-
Thanks for you help.
But it did not work after following you instruction. Press the green button and wait a while, system did not prompt any message and the screen only display upper menu bar. It's weired.
BTW:
I thought the following message telling me pfsense cloned the partition for me?
Cleaning secondary partition… done.
Duplicating current slice... done.Any idea?
-
Exactly the same issue here, running on an ALIX board :/
Upgrading over SSH doesn't work either…
-
Diag>nanobsd, enable permanent rw. Reboot afterwards to make sure nothing's stuck ro. Then try again.
-
@cmb:
Diag>nanobsd, enable permanent rw. Reboot afterwards to make sure nothing's stuck ro. Then try again.
Hi - I already had Read/Write enabled in NanoBSD settings.
When upgrading from the GUI - I'm getting exactly the same output as the OP.
Any ideas?
-
Here's my upgrade log
Updating repositories metadata…
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
**** WARNING ****
Duplicate slice required!!Before starting the upgrade process, the currently mounted nanobsd partition
needs to be cloned to the secondary partition, where the update will happenAfter installation a reboot will be required to switch partition.
Proceed with upgrade? (y/N) >>> Cleaning secondary partition...
1+0 records in
1+0 records out
1048576 bytes transferred in 0.375821 secs (2790095 bytes/sec)Duplicating current slice...
30034+1 records in
30034+1 records out
1968349696 bytes transferred in 280.108853 secs (7027088 bytes/sec)
Restoring slice label...
Testing duplicated partition integrity...
** /dev/ufs/pfSense0
** Last Mounted on /
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
15947 files, 875223 used, 2904805 free (2293 frags, 362814 blocks, 0.1% fragmentation)***** FILE SYSTEM IS CLEAN *****
Mounting second partition to run upgrade...
Unlocking package pfSense-kernel-pfSense_wrap...
Unlocking pfSense-kernel-pfSense_wrap-2.3
Downloading upgrade packages...
Updating pfSense-core repository catalogue...
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
Unable to update repository pfSense
All repositories are up-to-date.
Checking for upgrades (61 candidates): .......... done
Processing candidates (61 candidates): .......... done
The following 63 package(s) will be affected (of 0 checked):New packages to be INSTALLED:
uclcmd: 0.1 [pfSense]
libucl: 0.8.0 [pfSense]Installed packages to be UPGRADED:
unbound: 1.5.5 -> 1.5.8 [pfSense]
sqlite3: 3.9.2 -> 3.11.1 [pfSense]
smartmontools: 6.4_1 -> 6.4_2 [pfSense]
rate: 0.9 -> 0.9_1 [pfSense]
python27: 2.7.11_1 -> 2.7.11_2 [pfSense]
php56-zlib: 5.6.20 -> 5.6.21 [pfSense]
php56-xmlwriter: 5.6.20 -> 5.6.21 [pfSense]
php56-xmlreader: 5.6.20 -> 5.6.21 [pfSense]
php56-xml: 5.6.20 -> 5.6.21 [pfSense]
php56-tokenizer: 5.6.20 -> 5.6.21 [pfSense]
php56-sysvshm: 5.6.20 -> 5.6.21 [pfSense]
php56-sysvsem: 5.6.20 -> 5.6.21 [pfSense]
php56-sysvmsg: 5.6.20 -> 5.6.21 [pfSense]
php56-sqlite3: 5.6.20 -> 5.6.21 [pfSense]
php56-sockets: 5.6.20 -> 5.6.21 [pfSense]
php56-simplexml: 5.6.20 -> 5.6.21 [pfSense]
php56-shmop: 5.6.20 -> 5.6.21 [pfSense]
php56-session: 5.6.20 -> 5.6.21 [pfSense]
php56-readline: 5.6.20 -> 5.6.21 [pfSense]
php56-posix: 5.6.20 -> 5.6.21 [pfSense]
php56-pdo_sqlite: 5.6.20 -> 5.6.21 [pfSense]
php56-pdo: 5.6.20 -> 5.6.21 [pfSense]
php56-pcntl: 5.6.20 -> 5.6.21 [pfSense]
php56-openssl: 5.6.20 -> 5.6.21 [pfSense]
php56-opcache: 5.6.20 -> 5.6.21 [pfSense]
php56-mcrypt: 5.6.20 -> 5.6.21 [pfSense]
php56-mbstring: 5.6.20 -> 5.6.21 [pfSense]
php56-ldap: 5.6.20 -> 5.6.21 [pfSense]
php56-json: 5.6.20 -> 5.6.21 [pfSense]
php56-hash: 5.6.20 -> 5.6.21 [pfSense]
php56-gettext: 5.6.20 -> 5.6.21 [pfSense]
php56-filter: 5.6.20 -> 5.6.21 [pfSense]
php56-dom: 5.6.20 -> 5.6.21 [pfSense]
php56-curl: 5.6.20 -> 5.6.21 [pfSense]
php56-ctype: 5.6.20 -> 5.6.21 [pfSense]
php56-bz2: 5.6.20 -> 5.6.21 [pfSense]
php56-bcmath: 5.6.20 -> 5.6.21 [pfSense]
php56: 5.6.20 -> 5.6.21 [pfSense]
pfSense-rc: 2.3 -> 2.3.1 [pfSense-core]
pfSense-kernel-pfSense_wrap: 2.3 -> 2.3.1 [pfSense-core]
pfSense-default-config-serial: 2.3 -> 2.3.1 [pfSense-core]
pfSense-base-nanobsd: 2.3 -> 2.3.1 [pfSense-core]
pfSense-Status_Monitoring: 1.0_1 -> 1.3_1 [pfSense]
pfSense: 2.3_1 -> 2.3.1 [pfSense]
perl5: 5.20.3_8 -> 5.20.3_12 [pfSense]
pecl-zmq: 1.1.3 -> 1.1.3_1 [pfSense]
openvpn: 2.3.9 -> 2.3.11 [pfSense]
nettle: 2.7.1 -> 3.2 [pfSense]
libzmq4: 4.1.3 -> 4.1.4_1 [pfSense]
libsodium: 1.0.3 -> 1.0.8 [pfSense]
libedit: 3.1.20150325_1 -> 3.1.20150325_2 [pfSense]
gmp: 5.1.3_2 -> 5.1.3_3 [pfSense]
glib: 2.44.1_3 -> 2.46.2 [pfSense]
gettext-runtime: 0.19.6 -> 0.19.7 [pfSense]
filterlog: 0.1_1 -> 0.1_2 [pfSense]
dnsmasq-devel: 2.76.0test8 -> 2.76.0test12 [pfSense]
curl: 7.47.0 -> 7.48.0_1 [pfSense]
cpdup: 1.17_2 -> 1.18 [pfSense]
bsnmp-ucd: 0.4.1 -> 0.4.2 [pfSense]Installed packages to be REINSTALLED:
rrdtool-1.5.5_1 [pfSense] (options changed)
nginx-1.8.1,2 [pfSense] (options changed)72 MiB to be downloaded.
Locking package pfSense-kernel-pfSense_wrap…
Locking pfSense-kernel-pfSense_wrap-2.3Checking the logs under NanoBSD, I see this at the end.
Misc log:
fdisk: invalid fdisk partition table found
bsdlabel: /dev/ada0s3: no valid label found
bsdlabel: /dev/ada0s3: no valid label found
bsdlabel: /dev/ada0s3: no valid label foundfdisk/bsdlabel log:
Before upgrade fdisk/bsdlabel
******* Working on device /dev/ada0 *******
parameters extracted from in-core disklabel are:
cylinders=7818 heads=16 sectors/track=63 (1008 blks/cyl)Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=7818 heads=16 sectors/track=63 (1008 blks/cyl)Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 3861585 (1885 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 758/ head 15/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 3861711, size 3861585 (1885 Meg), flag 0
beg: cyl 759/ head 1/ sector 1;
end: cyl 493/ head 15/ sector 63
The data for partition 3 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 7723296, size 102816 (50 Meg), flag 0
beg: cyl 494/ head 0/ sector 1;
end: cyl 595/ head 15/ sector 63
The data for partition 4 is:/dev/ada0s1:
type: unknown
disk: amnesiac
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 3813
sectors/unit: 3844449
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 08 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 3844433 16 unused 0 0
c: 3844449 0 unused 0 0 # "raw" part, don't edit/dev/ada0s2:
type: unknown
disk: amnesiac
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 3813
sectors/unit: 3844449
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 08 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 3844433 16 unused 0 0
c: 3844449 0 unused 0 0 # "raw" part, don't edit
–-------------------------------------------------------------******* Working on device /dev/ada0 *******
parameters extracted from in-core disklabel are:
cylinders=7818 heads=16 sectors/track=63 (1008 blks/cyl)Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=7818 heads=16 sectors/track=63 (1008 blks/cyl)Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 3861585 (1885 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 758/ head 15/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 3861711, size 3861585 (1885 Meg), flag 0
beg: cyl 759/ head 1/ sector 1;
end: cyl 493/ head 15/ sector 63
The data for partition 3 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 7723296, size 102816 (50 Meg), flag 0
beg: cyl 494/ head 0/ sector 1;
end: cyl 595/ head 15/ sector 63
The data for partition 4 is:/dev/ada0s1:
type: unknown
disk: amnesiac
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 3813
sectors/unit: 3844449
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 08 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 3844433 16 unused 0 0
c: 3844449 0 unused 0 0 # "raw" part, don't edit/dev/ada0s2:
type: unknown
disk: amnesiac
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 3813
sectors/unit: 3844449
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 08 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 3844433 16 unused 0 0
c: 3844449 0 unused 0 0 # "raw" part, don't edit
–-------------------------------------------------------------Final upgrade fdisk/bsdlabel
******* Working on device /dev/ada0 *******
parameters extracted from in-core disklabel are:
cylinders=7818 heads=16 sectors/track=63 (1008 blks/cyl)Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=7818 heads=16 sectors/track=63 (1008 blks/cyl)Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 3861585 (1885 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 758/ head 15/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 3861711, size 3861585 (1885 Meg), flag 80 (active)
beg: cyl 759/ head 1/ sector 1;
end: cyl 493/ head 15/ sector 63
The data for partition 3 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 7723296, size 102816 (50 Meg), flag 0
beg: cyl 494/ head 0/ sector 1;
end: cyl 595/ head 15/ sector 63
The data for partition 4 is:/dev/ada0s1:
type: unknown
disk: amnesiac
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 3813
sectors/unit: 3844449
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 08 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 3844433 16 unused 0 0
c: 3844449 0 unused 0 0 # "raw" part, don't edit/dev/ada0s2:
type: unknown
disk: amnesiac
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 3813
sectors/unit: 3844449
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 08 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 3844433 16 unused 0 0
c: 3844449 0 unused 0 0 # "raw" part, don't edit
–------------------------------------------------------------- -
Same issue here. Logs are identical on a vk-t40e4
-
Hello,
Same for me on an APU board running 2.3-RELEASE nanobsd (4g) i386 :
>>> Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... pfSense repository is up-to-date. All repositories are up-to-date. **** WARNING **** Duplicate slice required!! Before starting the upgrade process, the currently mounted nanobsd partition needs to be cloned to the secondary partition, where the update will happen After installation a reboot will be required to switch partition. >>> Cleaning secondary partition... done. >>> Duplicating current slice... done. >>> Restoring slice label... done. >>> Testing duplicated partition integrity... done. >>> Mounting second partition to run upgrade... done. >>> Unlocking package pfSense-kernel-pfSense_wrap_vga... done. >>> Downloading upgrade packages... Updating pfSense-core repository catalogue... Unable to update repository pfSense-core Updating pfSense repository catalogue... Unable to update repository pfSense All repositories are up-to-date. Checking for upgrades (62 candidates): .......... done Processing candidates (62 candidates): .......... done The following 64 package(s) will be affected (of 0 checked): New packages to be INSTALLED: uclcmd: 0.1 [pfSense] libucl: 0.8.0 [pfSense] Installed packages to be UPGRADED: unbound: 1.5.5 -> 1.5.8 [pfSense] sqlite3: 3.9.2 -> 3.11.1 [pfSense] smartmontools: 6.4_1 -> 6.4_2 [pfSense] rate: 0.9 -> 0.9_1 [pfSense] python27: 2.7.11_1 -> 2.7.11_2 [pfSense] php56-zlib: 5.6.20 -> 5.6.21 [pfSense] php56-xmlwriter: 5.6.20 -> 5.6.21 [pfSense] php56-xmlreader: 5.6.20 -> 5.6.21 [pfSense] php56-xml: 5.6.20 -> 5.6.21 [pfSense] php56-tokenizer: 5.6.20 -> 5.6.21 [pfSense] php56-sysvshm: 5.6.20 -> 5.6.21 [pfSense] php56-sysvsem: 5.6.20 -> 5.6.21 [pfSense] php56-sysvmsg: 5.6.20 -> 5.6.21 [pfSense] php56-sqlite3: 5.6.20 -> 5.6.21 [pfSense] php56-sockets: 5.6.20 -> 5.6.21 [pfSense] php56-simplexml: 5.6.20 -> 5.6.21 [pfSense] php56-shmop: 5.6.20 -> 5.6.21 [pfSense] php56-session: 5.6.20 -> 5.6.21 [pfSense] php56-readline: 5.6.20 -> 5.6.21 [pfSense] php56-posix: 5.6.20 -> 5.6.21 [pfSense] php56-pdo_sqlite: 5.6.20 -> 5.6.21 [pfSense] php56-pdo: 5.6.20 -> 5.6.21 [pfSense] php56-pcntl: 5.6.20 -> 5.6.21 [pfSense] php56-openssl: 5.6.20 -> 5.6.21 [pfSense] php56-opcache: 5.6.20 -> 5.6.21 [pfSense] php56-mcrypt: 5.6.20 -> 5.6.21 [pfSense] php56-mbstring: 5.6.20 -> 5.6.21 [pfSense] php56-ldap: 5.6.20 -> 5.6.21 [pfSense] php56-json: 5.6.20 -> 5.6.21 [pfSense] php56-hash: 5.6.20 -> 5.6.21 [pfSense] php56-gettext: 5.6.20 -> 5.6.21 [pfSense] php56-filter: 5.6.20 -> 5.6.21 [pfSense] php56-dom: 5.6.20 -> 5.6.21 [pfSense] php56-curl: 5.6.20 -> 5.6.21 [pfSense] php56-ctype: 5.6.20 -> 5.6.21 [pfSense] php56-bz2: 5.6.20 -> 5.6.21 [pfSense] php56-bcmath: 5.6.20 -> 5.6.21 [pfSense] php56: 5.6.20 -> 5.6.21 [pfSense] pfSense-rc: 2.3 -> 2.3.1 [pfSense-core] pfSense-kernel-pfSense_wrap_vga: 2.3 -> 2.3.1 [pfSense-core] pfSense-default-config: 2.3 -> 2.3.1 [pfSense-core] pfSense-base-nanobsd: 2.3 -> 2.3.1 [pfSense-core] pfSense-Status_Monitoring: 1.0_1 -> 1.3_1 [pfSense] pfSense: 2.3 -> 2.3.1 [pfSense] perl5: 5.20.3_8 -> 5.20.3_12 [pfSense] pecl-zmq: 1.1.3 -> 1.1.3_1 [pfSense] openvpn: 2.3.9 -> 2.3.11 [pfSense] ntp: 4.2.8p6 -> 4.2.8p7 [pfSense] nettle: 2.7.1 -> 3.2 [pfSense] libzmq4: 4.1.3 -> 4.1.4_1 [pfSense] libsodium: 1.0.3 -> 1.0.8 [pfSense] libedit: 3.1.20150325_1 -> 3.1.20150325_2 [pfSense] gmp: 5.1.3_2 -> 5.1.3_3 [pfSense] glib: 2.44.1_3 -> 2.46.2 [pfSense] gettext-runtime: 0.19.6 -> 0.19.7 [pfSense] filterlog: 0.1_1 -> 0.1_2 [pfSense] dnsmasq-devel: 2.76.0test8 -> 2.76.0test12 [pfSense] curl: 7.47.0 -> 7.48.0_1 [pfSense] cpdup: 1.17_2 -> 1.18 [pfSense] bsnmp-ucd: 0.4.1 -> 0.4.2 [pfSense] Installed packages to be REINSTALLED: rrdtool-1.5.5_1 [pfSense] (options changed) nginx-1.8.1,2 [pfSense] (options changed) 72 MiB to be downloaded. >>> Locking package pfSense-kernel-pfSense_wrap_vga... done. Failed -
not exact same behavior here…
it actually installs but then does not come back up after reboot...does not matter if updated from webinterface or console.
2.3-RELEASE (amd64) to 2.3.1 kills the slice.
pfsense boot menu shows up, trys to load the kernel, fails and reboots... -
I have got the same problem with a watchguard firebox.
I cannot upgrade to 2.31
At the first try, i got the reply that the filesystem is dirty. I have cleaned it.
And now everytime I try to upgrade i got the attached mesage at the attachment.
Misc log: fdisk: invalid fdisk partition table found bsdlabel: /dev/ada0s3: no valid label found bsdlabel: /dev/ada0s3: no valid label found bsdlabel: /dev/ada0s3: no valid label found tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale shutdown: [pid 80380]
-
Hello,
I also have the same problem as the OP.
Regards,
iam -
The same here …
CF 4GB Nano install.
I need a workaround to get this fixed.
Nobody with a solution for this? Devs?
cm3c
-
I now have done the upgrade manually:
pkg unlock pfSense-kernel-pfSense pkg update -f pkg upgrade -f pkg lock pfSense-kernel-pfSense rebootAt the moment I don't have any problems.
-
Mine fails with the following error when trying 'pkg unlock pfSense-kernel-pfSense'.
I get 'pkg: Error accessing the package database'.
I'm also using a 4GB NanoBSD install - Seems a few others are too.
-
Is the filesystem mounted read/write?
EDIT: If yes try
pkg update -ffirst.
-
@iam:
I now have done the upgrade manually:
pkg unlock pfSense-kernel-pfSense pkg update -f pkg upgrade -f pkg lock pfSense-kernel-pfSense rebootAt the moment I don't have any problems.
This works fine here, but this is not the final solution, or?
-
This works fine here, but this is not the final solution, or?
Yes, with the Update to 3.1_1 I had the same problem.
-
Can also confirm I've managed to upgrade successfully to 2.3.1-P1-RELEASE via SSH. Before the upgrade I disabled Permanent Read/Write in the web GUI. Rebooted, re-enabled and the upgrade went smoothly.
ALIX 2C2 with a 4GB CF.
Many thanks
-
Thanx!
Same problem - fix works, except in the event your mounts are ro, you need to start with /etc/rc.conf_mount_rw:
/etc/rc.conf_mount_rw pkg unlock pfSense-kernel-pfSense pkg update -f pkg upgrade -f pkg lock pfSense-kernel-pfSense rebootDone! ;)
It seemed to take a lot longer than the UI - but maybe that's because you can see the progress of every pkg.
Cheers!
~r
