2.4.4p3 crashes after boot



  • Doing a fresh install of 2.4.4p3 or upgrading from 2.4.4p1 to 2.4.4p3 causes a crash on my
    Supermicro SuperServer 5018D-FN8T
    While running with dual channel ram

    If I run with only one memory module pfsense boots and I can access the web interface, but it crashes after a little while

    Starting device manager (devd)…kldload: can't load ums: No such file or directory - is show at boot right before the crash, so maybe a missing driver?

    I have been trying different stuff after googling

    Thought it was the console freeze errors many people report,
    but it is the entire machine that freezes not only the console.

    Experiment:
    I booted a fresh install of 2.4.4p3 with one memory module - and noted the log was good
    Inserted the second memory module and booted with crash result - noting is written to log on boot and crash


    So,
    Running 2.4.4_p1 gives no problems even after running several days with normal company config
    Running 2.5 gives no problems

    Running 2.4.4_p3 with one memory module - box boots normally thought with "Starting device manager (devd)…kldload: can't load ums: No such file or directory" - and crashes after a little while

    Running 2.4.4_p3 with two memory modules - pfsense freezes in the last phase of the boot just before showing the "Welcome" message - showing "Starting device manager (devd)…kldload: can't load ums: No such file or directory"

    Please help



  • Update: 2.5 gives me the same problems as 2.4.4_p3.. was a bit to quick to assume it didnt
    it booted and I was able to configure ip address for lan interface, but now its crashed and crashes before completing boot now



  • anyone have any ideas?


Log in to reply