And the solution: Backup your configuration, re-image the drive and restore 
your configuration.


On Aug 20, 2014, at 16:44, Adam Williams <[email protected]> wrote:

> I'm convinced that my issue on this one box is the same as those here:
> https://forum.pfsense.org/index.php?topic=75069.0
> 
> On Wed, Aug 20, 2014 at 12:40 PM, Adam Williams <[email protected]> wrote:
>> So I've learned a ton about how upgrades work. Sadly, the logs from
>> both the machines are nearly identical. Both of them successfully
>> download the update, stream it into a new disk, mount it to `/tmp`,
>> verify it, setup the new disk's `/etc/fstab`, etc.
>> 
>> The only thing that looks bad (to my untrained eye) in the output is this:
>> 
>> ```
>> gpart set -a active -i 1 ad0
>> gpart: table 'ad0' is corrupt: Operation not permitted
>> ```
>> 
>> Yet, again, that's in the log of the successful upgrade and that of
>> the unsuccessful upgrade.
>> 
>> I'm trying to understand how FreeBSD does it's boot magic, but I'd
>> love to hear from you if you know how I can make this thing boot off
>> the new install, or help me identify why it's not booting the new
>> install.
>> 
>> On Tue, Aug 19, 2014 at 7:05 PM, Adam Williams <[email protected]> wrote:
>>> Hello,
>>> 
>>> I've got two identical machines running 2.1-RELEASE. One updated to
>>> 2.1.4 perfectly, using the auto-upgrade, but the second one has run
>>> into trouble.
>>> 
>>> It will download the update, then produce this output:
>>> 
>>> ```
>>> Installing /root/latest.tgz.
>>> 
>>> Aug 19 21:34:55 host kernel: GEOM: ad0s1: media size does not match label.
>>> ```
>>> 
>>> It reboots, but is still running 2.1-RELEASE, and not 2.1.4.
>>> 
>>> Has anyone seen this before? I've tried it twice. Is there a better path?
>>> 
>>> Thanks,
>>> 
>>> Adam Williams
> _______________________________________________
> List mailing list
> [email protected]
> https://lists.pfsense.org/mailman/listinfo/list

_______________________________________________
List mailing list
[email protected]
https://lists.pfsense.org/mailman/listinfo/list

Reply via email to