Re: [pfSense] 2.1.3 Release Now Available
On 5/6/14, 11:53 AM, Bob Gustafson wrote: On 05/06/2014 12:27 PM, David Newman wrote: On 5/6/14, 10:24 AM, Jeremy Porter wrote: I've posted in a separate thread about issues with upgrading, even with a 4 GB card. This is an on Alix 2d13 with 256 Mbytes of RAM. Both from the GUI and the serial console, it appears that the new image successfully downloads and installs into the second partition, but the second partition won't boot. The boot method _might_ be an issue. When flashing CF cards in the past, I've followed the instructions here about changing from packet to nopacket boot methods: https://doc.pfsense.org/index.php/NanoBSD_on_WRAP#Booting_NanoBSD_on_WRAP But that's on WRAP, and 2d13 isn't a WRAP board, so I don't know for sure why the upgrade isn't booting. dn ___ The CF images should have the correct settings set for CF card. However the upgrade process takes a fair amount of ram. The best bet is to disable any extra services during the upgrade. The RAM size issue is different than the CF card size issue. The RAM size issue, is simply running out of available memory to run the upgrade process and boot up. The 512CF card issue, is that the pfsense image is around 190MBs, times two plus a 50MB configuration partition. There isn't enough room to unpack the image and do the upgrades. In either case, you can backup your configuration, to your local server, then re-flash the CF card, then restore your configuration. If the upgrade fails its helpful to look at the upgrade log file, to see why it failed. Usually it fails due to pointing to an invalid URL and failing to validate, or package errors. Thanks, that makes sense. I had tried disabling all services except dns forwarding, and still no go. Bottom line: For reasons of scarce disk or RAM or both, PC Engines Alix machines running pfSense probably need to be upgraded manually. dn I upgraded my Alix 2d3 board yesterday. Using the autoupdate, it took only 4 minutes to load up the pf itself, but another 45 minutes to reload the packages (asterisk..) - these times are taken from the system log after it came back up. Perhaps you have big packages and are not waiting long enough? AFAICT there are no packages installed (pkg_info returns nothing). There are four services running: apinger dhcpd dnsmasq ntpd Of these, only dnsmasq is required to find the upgrade server. Even so, an upgrade from the serial console fails. The upgrade seems to complete fairly fast (~4-5 minutes) but it appears the system won't boot from the second partition. Here's an upgrade log: http://pastebin.com/LMUXSjpD Thanks in advance for further troubleshooting clues. Several posts have suggested this upgrade _should_ work. dn Bob G ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] 2.1.3 Release Now Available
Hi all, thanks for the great job. I don't see upgrades to 2.1.3 for nanoBSD VGA 512MB CF. I managed upgrading that Alix by mounting an USB perndrive on /root and everything was fine. Please, should I wait for a 512 image, build an image on my own starting from oter images (howto?) or do I have to change the CF? Thanks in advance Odette -- Odette Nsaka In data sabato 3 maggio 2014 02:52:06, Chris Buechler ha scritto: pfSense 2.1.3 release is now available. You can find the details on our blog. https://blog.pfsense.org/?p=1272 ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] 2.1.3 Release Now Available
On 5/6/2014 5:54 AM, Odette Nsaka wrote: Hi all, thanks for the great job. I don't see upgrades to 2.1.3 for nanoBSD VGA 512MB CF. I managed upgrading that Alix by mounting an USB perndrive on /root and everything was fine. Please, should I wait for a 512 image, build an image on my own starting from oter images (howto?) or do I have to change the CF? Thanks in advance Odette There is no 512M upgrade image, or 512M image because there isn't sufficient room, for the NanoBSD and upgrade partition. Certainly it seems like it would be easier to replace the CF card with a 4GB card. ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] 2.1.3 Release Now Available
On 5/6/14, 9:33 AM, Jeremy Porter wrote: On 5/6/2014 5:54 AM, Odette Nsaka wrote: Hi all, thanks for the great job. I don't see upgrades to 2.1.3 for nanoBSD VGA 512MB CF. I managed upgrading that Alix by mounting an USB perndrive on /root and everything was fine. Please, should I wait for a 512 image, build an image on my own starting from oter images (howto?) or do I have to change the CF? Thanks in advance Odette There is no 512M upgrade image, or 512M image because there isn't sufficient room, for the NanoBSD and upgrade partition. Certainly it seems like it would be easier to replace the CF card with a 4GB card. I've posted in a separate thread about issues with upgrading, even with a 4 GB card. This is an on Alix 2d13 with 256 Mbytes of RAM. Both from the GUI and the serial console, it appears that the new image successfully downloads and installs into the second partition, but the second partition won't boot. The boot method _might_ be an issue. When flashing CF cards in the past, I've followed the instructions here about changing from packet to nopacket boot methods: https://doc.pfsense.org/index.php/NanoBSD_on_WRAP#Booting_NanoBSD_on_WRAP But that's on WRAP, and 2d13 isn't a WRAP board, so I don't know for sure why the upgrade isn't booting. dn ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] 2.1.3 Release Now Available
I've posted in a separate thread about issues with upgrading, even with a 4 GB card. This is an on Alix 2d13 with 256 Mbytes of RAM. Both from the GUI and the serial console, it appears that the new image successfully downloads and installs into the second partition, but the second partition won't boot. The boot method _might_ be an issue. When flashing CF cards in the past, I've followed the instructions here about changing from packet to nopacket boot methods: https://doc.pfsense.org/index.php/NanoBSD_on_WRAP#Booting_NanoBSD_on_WRAP But that's on WRAP, and 2d13 isn't a WRAP board, so I don't know for sure why the upgrade isn't booting. dn ___ The CF images should have the correct settings set for CF card. However the upgrade process takes a fair amount of ram. The best bet is to disable any extra services during the upgrade. The RAM size issue is different than the CF card size issue. The RAM size issue, is simply running out of available memory to run the upgrade process and boot up. The 512CF card issue, is that the pfsense image is around 190MBs, times two plus a 50MB configuration partition. There isn't enough room to unpack the image and do the upgrades. In either case, you can backup your configuration, to your local server, then re-flash the CF card, then restore your configuration. If the upgrade fails its helpful to look at the upgrade log file, to see why it failed. Usually it fails due to pointing to an invalid URL and failing to validate, or package errors. ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] 2.1.3 Release Now Available
On 5/6/14, 10:24 AM, Jeremy Porter wrote: I've posted in a separate thread about issues with upgrading, even with a 4 GB card. This is an on Alix 2d13 with 256 Mbytes of RAM. Both from the GUI and the serial console, it appears that the new image successfully downloads and installs into the second partition, but the second partition won't boot. The boot method _might_ be an issue. When flashing CF cards in the past, I've followed the instructions here about changing from packet to nopacket boot methods: https://doc.pfsense.org/index.php/NanoBSD_on_WRAP#Booting_NanoBSD_on_WRAP But that's on WRAP, and 2d13 isn't a WRAP board, so I don't know for sure why the upgrade isn't booting. dn ___ The CF images should have the correct settings set for CF card. However the upgrade process takes a fair amount of ram. The best bet is to disable any extra services during the upgrade. The RAM size issue is different than the CF card size issue. The RAM size issue, is simply running out of available memory to run the upgrade process and boot up. The 512CF card issue, is that the pfsense image is around 190MBs, times two plus a 50MB configuration partition. There isn't enough room to unpack the image and do the upgrades. In either case, you can backup your configuration, to your local server, then re-flash the CF card, then restore your configuration. If the upgrade fails its helpful to look at the upgrade log file, to see why it failed. Usually it fails due to pointing to an invalid URL and failing to validate, or package errors. Thanks, that makes sense. I had tried disabling all services except dns forwarding, and still no go. Bottom line: For reasons of scarce disk or RAM or both, PC Engines Alix machines running pfSense probably need to be upgraded manually. dn ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] 2.1.3 Release Now Available
El 03/05/2014 9:52, Chris Buechler escribió: pfSense 2.1.3 release is now available. You can find the details on our blog. https://blog.pfsense.org/?p=1272 Hi, many many thanks for the GREAT job. Sammy ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] 2.1.3 Release Now Available
On Tue, May 6, 2014 at 1:09 PM, David Newman dnew...@networktest.comwrote: Both from the GUI and the serial console, it appears that the new image successfully downloads and installs into the second partition, but the second partition won't boot. The boot method _might_ be an issue. When flashing CF cards in the past, I've followed the instructions here about changing from packet to nopacket boot methods: https://doc.pfsense.org/index.php/NanoBSD_on_WRAP#Booting_NanoBSD_on_WRAP But that's on WRAP, and 2d13 isn't a WRAP board, so I don't know for sure why the upgrade isn't booting. I upgrade two ALIX today, and one yesterday. All have 256MB RAM on 4GB cards. Went from 2.1.2 = 2.1.3. No issues. These were upgraded from 2.1.0 or 2.0 to 2.1.2 over the last two weeks as well with no issues. You do not want to muck about with changing the boot methods. You do not have a WRAP so why would you do that? You're just making trouble for yourself. ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] 2.1.3 Release Now Available
On 5/6/14, 11:35 AM, Vick Khera wrote: On Tue, May 6, 2014 at 1:09 PM, David Newman dnew...@networktest.com mailto:dnew...@networktest.com wrote: Both from the GUI and the serial console, it appears that the new image successfully downloads and installs into the second partition, but the second partition won't boot. The boot method _might_ be an issue. When flashing CF cards in the past, I've followed the instructions here about changing from packet to nopacket boot methods: https://doc.pfsense.org/index.php/NanoBSD_on_WRAP#Booting_NanoBSD_on_WRAP But that's on WRAP, and 2d13 isn't a WRAP board, so I don't know for sure why the upgrade isn't booting. I upgrade two ALIX today, and one yesterday. All have 256MB RAM on 4GB cards. Went from 2.1.2 = 2.1.3. No issues. These were upgraded from 2.1.0 or 2.0 to 2.1.2 over the last two weeks as well with no issues. You do not want to muck about with changing the boot methods. You do not have a WRAP so why would you do that? You're just making trouble for yourself. Are you Alix units also 2d13? Are you upgrading from the GUI, serial console, or some other method? Which manufacturers' CF card are you using? (I have SanDisk) Thanks dn ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] 2.1.3 Release Now Available
On 05/06/2014 12:27 PM, David Newman wrote: On 5/6/14, 10:24 AM, Jeremy Porter wrote: I've posted in a separate thread about issues with upgrading, even with a 4 GB card. This is an on Alix 2d13 with 256 Mbytes of RAM. Both from the GUI and the serial console, it appears that the new image successfully downloads and installs into the second partition, but the second partition won't boot. The boot method _might_ be an issue. When flashing CF cards in the past, I've followed the instructions here about changing from packet to nopacket boot methods: https://doc.pfsense.org/index.php/NanoBSD_on_WRAP#Booting_NanoBSD_on_WRAP But that's on WRAP, and 2d13 isn't a WRAP board, so I don't know for sure why the upgrade isn't booting. dn ___ The CF images should have the correct settings set for CF card. However the upgrade process takes a fair amount of ram. The best bet is to disable any extra services during the upgrade. The RAM size issue is different than the CF card size issue. The RAM size issue, is simply running out of available memory to run the upgrade process and boot up. The 512CF card issue, is that the pfsense image is around 190MBs, times two plus a 50MB configuration partition. There isn't enough room to unpack the image and do the upgrades. In either case, you can backup your configuration, to your local server, then re-flash the CF card, then restore your configuration. If the upgrade fails its helpful to look at the upgrade log file, to see why it failed. Usually it fails due to pointing to an invalid URL and failing to validate, or package errors. Thanks, that makes sense. I had tried disabling all services except dns forwarding, and still no go. Bottom line: For reasons of scarce disk or RAM or both, PC Engines Alix machines running pfSense probably need to be upgraded manually. dn I upgraded my Alix 2d3 board yesterday. Using the autoupdate, it took only 4 minutes to load up the pf itself, but another 45 minutes to reload the packages (asterisk..) - these times are taken from the system log after it came back up. Perhaps you have big packages and are not waiting long enough? Bob G ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] 2.1.3 Release Now Available
On Tue, May 6, 2014 at 2:37 PM, David Newman dnew...@networktest.comwrote: Are you Alix units also 2d13? I have no idea how to tell. I purchased the dual-ALIX in a 1U enclosure from Netgate in 2012. They have three ethernets. The third unit is a box at my home and I've had that for several years now, and it too has 3 ethernets and 256MB RAM.. Are you upgrading from the GUI, serial console, or some other method? Both. I prefer the command line since I can watch the install and reboot over the serial console. Sometimes I do that and sometimes I do the GUI. The GUI stops if you navigate away, but the console keeps going if you really are on the console and disconnect. I don't ever do it via ssh connection. Which manufacturers' CF card are you using? (I have SanDisk) The pair in the Netgate 1U enclosure are I think the SanDisk 4GB which constantly complain about ad0: FAILURE - READ status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=7813119 which allegedly is harmless. I cannot for the life of me remember what I put in the box at home, but I think that's a 2GB card. ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
