Update failed: fstab problem

ck42

Okay…so, do I need to file a bug report on this or something? Just need to know what the proper next steps should be here guys....

jimp

You need to provide a lot more information. What were you on before? What are you upgrading to? What size CF?

Also check the upgrade logs in /conf/

ck42

Currently running 1.2.3
Attempting to upgrade to 2.0-RC3-2G-nanobsd

Contents of /conf only contain a single .txt file (upgrade_log.txt) Contents below:

[admin@pfsense.local]/conf(6): cat upgrade_log.txt

NanoBSD Firmware upgrade in progress…
[1.2.3-RELEASE]

That's it…just that it's in progress.

jimp

How did you try the upgrade? Manual firmware update? Auto update? Console update by URL?

ck42

Used the GUI. System->firmware->Enable Firmware Upload -> browsed to image on my workstation.

One thing that I can't verify, but I'm nearly certain of is - the version of the image currently installed. I'm pretty certain it's the 2G one…but is there a way in the CLI for me to verify this? ...just in case it's the 1G or something else...

Oh...forgot to mention, I DID verify the md5sum BEFORE attempting the upload. Checked out good.

jimp

Try a console update by URL and feed it the download URL for the right nanobsd upgrade image. I know that the auto update for NanoBSD won't work.

You can verify the size by looking at /etc/nanosize.txt

ck42

Confirmed it is 2G.

Using the console upgrade now. It's been spitting out dots for about 20 minutes now. How long does this take!? LOL.

[EDIT]
….still drawing dots. Is this normal?

ck42

Okay…seriously now. It's been over an hour now and it's still drawing dots. ???
I'm suspecting that the upgrade has actually failed and the installer is simply not showing me the failure...and just drawing me nice rows of dots.

[EDIT]
Upgrade log file says it's still in progress.

[EDIT2]
Upgrade apparently failed. Lost my connection with the dots sometime during the night, but log files seem to indicate that this one failed too.
Tried the other method again…browsing to the .img on my workstation. This apparently failed again.
Here's the contents of /tmp/notices
[admin@pfsense.local]/tmp(87): cat notices
a:2:{i:1309305431;a:5:{s:2:"id";s:14:"UpgradeFailure";s:6:"notice";s:78:"Something went wrong when trying to update the fstab entry. Aborting a:1:{i:1309355658;a:5:{s:2:"id";s:14:"UpgradeFailure";s:6:"notice";s:78:"Something went wrong when trying to update the fstab entry. Aborting upgrade.";s:3:"url";s:0:"";s:8:"category";s:14:"UpgradeFailure";s:8:"priority";i:1;}}[1.2.3-RELEASE]

Bug #457 ???

[EDIT3]
Found this in the GUI under Diagnostics->NanoBSD

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 270

Misc log:

mkdir: /tmp/pfsense0: File exists
mount: /dev/ufs/pfsense0 : Operation not permitted
cp: /tmp/pfsense0/etc/fstab: No such file or directory
sed: /tmp/pfsense0/etc/fstab: No such file or directory
umount: /tmp/pfsense0: not a file system root directory

fdisk/bsdlabel log:

jimp

Looks like http://redmine.pfsense.org/issues/1377 then

ck42

So, next step?

Have to reinstall fresh image? Wait for final 2.0 release and hope it's fixed?