Is the "NanoBSD filesystem is mounted r/w" a temporary thing until you fix these issues?
On Tue, May 24, 2016 at 1:10 PM, Chris Buechler <c...@pfsense.com> wrote: > On Tue, May 24, 2016 at 2:47 PM, Karl Fife <karlf...@gmail.com> wrote: > > On 5/24/2016 2:30 PM, Chris Buechler wrote: > >> > >> On Tue, May 24, 2016 at 2:25 PM, WebDawg <webd...@gmail.com> wrote: > >>> > >>> On Tue, May 24, 2016 at 2:18 PM, Chris Buechler <c...@pfsense.com> > wrote: > >>> > >>>> On Tue, May 24, 2016 at 1:28 PM, WebDawg <webd...@gmail.com> wrote: > >>>>> > >>>>> On Tue, May 24, 2016 at 11:34 AM, Chris Buechler <c...@pfsense.com> > >>>> > >>>> wrote: > >>>>>> > >>>>>> On Tue, May 24, 2016 at 5:33 AM, OSN | Marian Fischer <m...@osn.de> > >>>> > >>>> 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? > > > > No. There is some issue in that case where pkg's status reporting has > a problem with nanobsd, where it makes the GUI think it failed, but > it's actually successful and still running fine in the background. The > upgrade still completed fine. > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
