pfSense

same problem with fresh image 14.05.2010 by upgrading try to 18.05.2010 via webinterface

(sytemlog) php: : New alert found: Something went wrong when trying to update the fstab entry. Aborting upgrade.
system mount: "/dev/ufs/pfsense0 on / (ufs, local, read-only)"

(/cf/conf/firmware_update_misc.log)
mount: /dev/ufs/pfsense1 : No such file or directory
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_upgrade_log.txt)
#no content#

system alix board 4GB kingston flashcard

NanoBSD Firmware upgrade in progress...

File list:

Warning: file_get_contents(/conf/file_upgrade_log.txt): failed to open stream: No such file or directory in /usr/local/www/diag_nanobsd.php on line 181

Misc log:

mount: /dev/ufs/pfsense1 : No such file or directory
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:

I just updated a 2GB image from the GUI and the CLI and both worked, though I did check some fixes in for the "console update by URL" option. I updated from mid-April to a snapshot from yesterday night.

Update URL ?

i flashed the CF card with "pfSense-2.0-BETA1-4g-20100515-0038-nanobsd.img.gz" and want to update from "http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/.updaters/"

i added url to update manager and tried the online update from the GUI, nothing works

after this i tried the console update with the url "http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/.updaters/latest.tgz" and it does not work.

system reboots and it trys to update the installed packages

failed with fstab error

Automatic update has never, ever, worked on NanoBSD. It will be worked on eventually though.

Use one of the snapshot images from here, find one that matches your size:

http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/?C=M;O=D

Download the image and use the firmware upload feature, or do a console update by URL.

I'll see if I can find out what might be causing those errors, but none of them appear to be fatal.

The errors were meaningless. They were just for logging purposes, some fdisk commands were being run on other slices that didn't really need to be. I fixed those errors and some others that were coming up. Those logs are really only for debugging when something goes wrong with the upgrade; If it works, there is really no need to check the logs.

I am still trying to figure out why the logs do not contain all of the information that should be there. There is a lot of info that should be logged, and is logged if I watch the files "live" during the upgrade, but is not in the logs after reboot.

Where does the log files will be written?
Both Partitions /dev/ufs/pfsense1 on / and /dev/ufs/cf on /cf are read only.
if the upgrade fails and the partitions are ro mounted, the information will be lost.

I think if i look on the upgrade process, the system fails and set the partitions read only in this fdisk part, after this pfsense reboots and will finish the upgrade prozess (reinstall plugins). but in reality it never upgrades.

@Jim i am not so deep in the code and prozesses of pfsense, but i will help to find and fix bugs in the best way i can do.

The logs are stored in /conf/ and the partition is read/write when the logs are written, and I don't see that it gets switched back to read-only mode at all during the process.

okay, I will try, can you upload an upgrade SnapShot (Size 4G) and i will try it
which files do you need?

You'll have to wait for the snapshot builder to crank one out. It moves at its own special pace :-)

The log files from /conf/*_log.txt are the debug logs we need if you have a problem.

Jochen Becker wrote:

/conf/*log* data from upgrade nanobsd 4G from-20100515-0038 to 20100523-1142

upgrade via console with upgrade per url

upgrade url http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/updates/pfSense-2.0-BETA1-4g-20100523-1142-nanobsd-upgrade.img.gz

None of those files you used will have the code I checked in today. You need to wait for snapshots dated after the 25th.

today upgraded to
pfSense-2.0-BETA1-4g-20100526-0339-nanobsd-upgrade.img.gz

waiting for next 4G image to send the files

have a look on ticket #516
if this is fixed, next one will be #516