2.3_1 to 2.3.1_1 fails

[ricle]

My second failed update today brings:

Repository pfSense-core has a wrong packagesite, need to re-create database
pfSense repository update completed. 385 packages processed.
After installation a reboot will be required to switch partition.

Secondary partition (/dev/ufs/pfsense0), used for upgrade not found
Failed

So the first Box never comes back after the upgrade from 2.3_1 to 2.3.1_1 and the next box (nanobsd (4g)) not willing to upgrade.

I have 9 boxes widespread in the country and its a long way (hundreds kilometers) to drive!  >:(

Can u make sure the upgrades did it in a better way than now?

Boss is pissed off tomorrow for sure and i have to jump into car!  >:(

[JorgeOliveira]

Upgrading on Fridays or Weekends is generally a bad idea, as developers won't be around when you need them.

I'd recommend, if possible, building some test environments and testing upgrade process before performing it on production systems.

Also, it is sometimes easier to just 'nuke' a bad install/upgrade and rebuild from scratch and then import a configuration backup.

Good luck.

[ricle]

@JorgeOliveira:

Upgrading on Fridays or Weekends is generally a bad idea, as developers won't be around when you need them.

I'd recommend, if possible, building some test environments and testing upgrade process before performing it on production systems.

…

Sorry but its the only way i can do it! Nobody accept to be offline on working days. So normaly i wait 1 week before i do the updates because dont want to drive. Its should be clear the most important thing is the base system come back after upgrade, no matter whats package are causes to fail.

Test systems wont help because on some alix it works on other not, all runing the same version!

So it was like i mention, boss was not happy and the staff too, i have to drive and it takes 1 day to come back because heavy weather and a lot of traffic. :-(
Alix was not responding on LAN and i have to mess around with the serial cable. :-(

Dont know what to do now with 2.3.1_5, dont like so frequently updates in such a short time.