ricsip - Posted 86 Minutes Ago
miczyg - Posted 5 Minutes Ago
I confirm the issue. Leaving apu only with the mSATA disk will cause pfSense hang at mentioned point. It is reproducible on 4.0.19, but on v4.0.18 works well. It is really weird, because we have not touched anything in firmware except iPXE embedded script.
Leaving USB stick in allows to boot the pfSense on v4.0.19. pfSense 2.4.2 seems to also be affected on v4.0.19.
We did not catch the issue because we obviously can't test all possible scenarios. Unfortunately we have had something plugged in USB connector all the time, so we couldn't see the issue at the beginning.
Thank You for reporting the issue. If we come up with a solution, we will post it.
Would recommend to add some extra testcase to handle properly the validation of pfsense / opnsense succesful 1) BOOT 2) REBOOT
a) with USB + mSATA
b) without USB, only mSATA
So minimum 4 testcases: #1a,1b,2a,2b
We try our best to validate as much scenarios and configurations as possible. It is pretty hard to maintain 4 platforms with all possible configurations. Testing everything manually is also not the way to go. That is why we keep extending our configuration to match users needs and reported issues in automated validation.
Pfsense and Opnsense are the primary platforms for your products.
I understand Your argumentation and we will turn our focus more on pfSense and opnSense.
And please! If you already maintain a dedicated page for firmware, keep it up to date:
--> pls add to 4.0.19 this new issue as another known issue!
Please do not be so harsh, I have just confirmed the issue couple hours ago. The page will be updated ASAP.