Fail to upgrade 2.3_1 to 2.3.1

heiko3001

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]

1.jpg_thumb

iam

Hello,

I also have the same problem as the OP.

Regards,
iam

cm3c

The same here …

CF 4GB Nano install.

I need a workaround to get this fixed.

Nobody with a solution for this? Devs?

cm3c

iam

I now have done the upgrade manually:


pkg unlock pfSense-kernel-pfSense
pkg update -f
pkg upgrade -f
pkg lock pfSense-kernel-pfSense
reboot

At the moment I don't have any problems.

yuljk

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.

iam

Is the filesystem mounted read/write?

EDIT: If yes try


pkg update -f

first.

heiko3001

@iam:

I now have done the upgrade manually:
pkg unlock pfSense-kernel-pfSense
pkg update -f
pkg upgrade -f
pkg lock pfSense-kernel-pfSense
reboot
At the moment I don't have any problems.

This works fine here, but this is not the final solution, or?

iam

@heiko3001:

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.

yuljk

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

beckerwilliams

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
reboot

Done! ;)

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

iam

@beckerwilliams:

It seemed to take a lot longer than the UI - but maybe that's because you can see the progress of every pkg.

No it takes longer because of the option -f. I think it should also work without it:


pkg upgrade

iam

@iam:

@beckerwilliams:

It seemed to take a lot longer than the UI - but maybe that's because you can see the progress of every pkg.

No it takes longer because of the option -f. I think it should also work without it:
pkg upgrade

With it reinstalls alls packages. I did the upgrade to 2.3.1_1 without this option, and it worked also perfectly.

iam

The same procedure with 2.3.1_5