Hi all, thanks for the pointer with 2.1.5. Indeed it's booting ... finally.
I guess it is a bad idea to upgrade via user interface to pfsense to 2.2.1 now as I'm then back on "won't boot" or crash daily path. Am I correct on this ?
Is there already a "bug report" logged on pfsense for this boot issue on 2.2,1 ? Are they aware of it ?
Regards, Marcel Am 24.03.2015 um 16:02 schrieb ED Fochler:
Ditto. 2.2.0 on msata was catastrophic. 2.2.1 full install on a regular SATA drive still fails for me on 6501-50. Sticking with 2.1.5 for the foreseeable future.On 2015, Mar 24, at 7:01 AM, Giles Coochey <[email protected]> wrote: On 24/03/2015 09:41, Martin Johnson wrote:Are you using the correct image? You need a NanoBSD image with serial console So something like: pfSense-2.2.1-RELEASE-1g-i386-nanobsd.img.gzI was running pfsense 2.1.5 on a 6501-70 with a mSata drive. I upgraded to 2.2.0 and found that the system was rebooting every day, eventually it completely failed, and I could not install 2.2.0 correctly at all. I have reverted to 2.1.5 until I heard something about it in the pfsense / soekris mailing lists. Sounds like a similar problem to me. -- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 8444 780677 +44 (0) 7584 634135 http://www.coochey.net http://www.netsecspec.co.uk [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
