Re: [pfSense] Update 2.3_1 to 2.3.1 failed
On Tue, May 24, 2016 at 6:47 PM, Jeppe Øland wrote: > Is the "NanoBSD filesystem is mounted r/w" a temporary thing until you fix > these issues? > No. The issue is some flash media is really slow to rw->ro mount. We used to carry a forcesync patch to forcefully un-mount it without the drive saying it was safe to do so. While we never saw any indications of that causing issues, it was removed because it's unsafe. Since then, many have had to set permanent rw for that reason, and it got worse. Being rw doesn't really change anything other than not jumping through a bunch of mount/remount hoops. The things that get written to often are still in RAM disk. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] Update 2.3_1 to 2.3.1 failed
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 wrote: > On Tue, May 24, 2016 at 2:47 PM, Karl Fife wrote: > > On 5/24/2016 2:30 PM, Chris Buechler wrote: > >> > >> On Tue, May 24, 2016 at 2:25 PM, WebDawg wrote: > >>> > >>> On Tue, May 24, 2016 at 2:18 PM, Chris Buechler > wrote: > >>> > On Tue, May 24, 2016 at 1:28 PM, WebDawg wrote: > > > > On Tue, May 24, 2016 at 11:34 AM, Chris Buechler > > wrote: > >> > >> On Tue, May 24, 2016 at 5:33 AM, OSN | Marian Fischer > > 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
Re: [pfSense] Update 2.3_1 to 2.3.1 failed
On Tue, May 24, 2016 at 2:47 PM, Karl Fife wrote: > On 5/24/2016 2:30 PM, Chris Buechler wrote: >> >> On Tue, May 24, 2016 at 2:25 PM, WebDawg wrote: >>> >>> On Tue, May 24, 2016 at 2:18 PM, Chris Buechler wrote: >>> On Tue, May 24, 2016 at 1:28 PM, WebDawg wrote: > > On Tue, May 24, 2016 at 11:34 AM, Chris Buechler wrote: >> >> On Tue, May 24, 2016 at 5:33 AM, OSN | Marian Fischer 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
Re: [pfSense] Update 2.3_1 to 2.3.1 failed
On 5/24/2016 2:30 PM, Chris Buechler wrote: On Tue, May 24, 2016 at 2:25 PM, WebDawg wrote: On Tue, May 24, 2016 at 2:18 PM, Chris Buechler wrote: On Tue, May 24, 2016 at 1:28 PM, WebDawg wrote: On Tue, May 24, 2016 at 11:34 AM, Chris Buechler wrote: On Tue, May 24, 2016 at 5:33 AM, OSN | Marian Fischer 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
Re: [pfSense] Update 2.3_1 to 2.3.1 failed
On Tue, May 24, 2016 at 2:25 PM, WebDawg wrote: > On Tue, May 24, 2016 at 2:18 PM, Chris Buechler wrote: > >> On Tue, May 24, 2016 at 1:28 PM, WebDawg wrote: >> > On Tue, May 24, 2016 at 11:34 AM, Chris Buechler >> wrote: >> > >> >> On Tue, May 24, 2016 at 5:33 AM, OSN | Marian Fischer >> 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
Re: [pfSense] Update 2.3_1 to 2.3.1 failed
On Tue, May 24, 2016 at 2:18 PM, Chris Buechler wrote: > On Tue, May 24, 2016 at 1:28 PM, WebDawg wrote: > > On Tue, May 24, 2016 at 11:34 AM, Chris Buechler > wrote: > > > >> On Tue, May 24, 2016 at 5:33 AM, OSN | Marian Fischer > 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. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] Update 2.3_1 to 2.3.1 failed
On Tue, May 24, 2016 at 1:28 PM, WebDawg wrote: > On Tue, May 24, 2016 at 11:34 AM, Chris Buechler wrote: > >> On Tue, May 24, 2016 at 5:33 AM, OSN | Marian Fischer 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. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] Update 2.3_1 to 2.3.1 failed
On Tue, May 24, 2016 at 11:34 AM, Chris Buechler wrote: > On Tue, May 24, 2016 at 5:33 AM, OSN | Marian Fischer 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? ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] Update 2.3_1 to 2.3.1 failed
On Tue, May 24, 2016 at 5:33 AM, OSN | Marian Fischer 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? ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
[pfSense] Update 2.3_1 to 2.3.1 failed
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? cm3c ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
