On 5/24/2016 2:30 PM, Chris Buechler wrote:
On Tue, May 24, 2016 at 2:25 PM, WebDawg <[email protected]> wrote:
On Tue, May 24, 2016 at 2:18 PM, Chris Buechler <[email protected]> wrote:
On Tue, May 24, 2016 at 1:28 PM, WebDawg <[email protected]> wrote:
On Tue, May 24, 2016 at 11:34 AM, Chris Buechler <[email protected]>
wrote:
On Tue, May 24, 2016 at 5:33 AM, OSN | Marian Fischer <[email protected]>
wrote:
Hi list,
when i try to update one carp member from 2.3_1 to the latest update
(2.3.1) it fails after
# snip
Updating pfSense-core repository catalogue...
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
# snip
the other member did the update well. Both are running on 4GB CF nano
install.
any solution out there?
Diag>NanoBSD, set to permanent rw, and reboot for good measure. It work
then?
_______________________________________________
I have a few pfSense devices that I purchased, do I need to set permanent
rw on them for 2.3.1?
If you have problems with them, yes. Once upgraded to 2.3.1, they'll
be set permanent rw with no option to go ro.
So if I already have them up to 2.3.1, I am fine.
Yes.
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
So is the R/O,R/W issue the same cause as here?
thusly:
https://imagebin.ca/v/2hkICOAnJnbs
Log:
http://pastebin.com/vFMqWNHK
If the update wizard reports "update failed", but post reboot it reports
2.3.1, and my 'failed' updates all show NanoBSD mounted R/W, and show v
2.3.1. Any cause for concern, or reason to suspect that the system
might be in an unusual state?
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
