On 4/7/2014 8:38 AM, Pete Boyd wrote: > The 2.1.0 to 2.1.1 upgrade on nanobsd (4g) on ALIX failed for me with > "Something went wrong when trying to update the fstab entry. Aborting > upgrade." > > I got the same issue when using auto update, and when using local upload > of pfSense-2.1.1-RELEASE-4g-i386-nanobsd-upgrade.img.gz. > > The log has 2 instances of this: > php: /system_firmware.php: The command '/sbin/mount -u -w -o > sync,noatime /cf' returned exit code '1', the output was 'mount: not > currently mounted /cf' > > On bootup it already has this issue in the log: > php: rc.bootup: The command '/sbin/mount -u -r -f -o sync,noatime /cf' > returned exit code '1', the output was 'mount: not currently mounted /cf' > > Does anyone have any thoughts on how to remedy this please?
What does the output of "mount" show while booted and running? If your /cf slice is missing/corrupt/not there, that would explain the symptoms. No easy fix for that short of a reimage or using a new card. Perhaps you used an image that was slightly too large for the card and didn't see the error when imaging, or never noticed that you didn't actually have a /cf partition. Jim _______________________________________________ List mailing list [email protected] https://lists.pfsense.org/mailman/listinfo/list
