HP Proliant DL360G3 Working with 2.1.5 fails to boot when try to update to 2.2



  • I am trying to install a pfsense on a HP proliant DL360G3 working perfectly with a Pfsense 2.1.5
    When trying to update to 2.2 it hangs on boot after reset.

    The first time last message on screen says something about usb, i read something about FreeBSD 10 problems with some old proliant usb controllers and I disabled the USB.

    Reinstall 2.1.5 and update again, and this time it says something like "trying to unblock random…"
    and appears to be hang again

    Any one have any experience with something like this? Any idea about a fix or a workaround?



  • Where specifically does it hang on boot?

    Seems there are several reports of that system working fine with FreeBSD 8.x (which was the base of our 2.0x and 2.1x releases), but not working with 9.x nor 10.x.
    https://forums.freebsd.org/threads/freebsd-10-0-on-hp-proliant-dl360-g3.45025/
    https://forums.freenas.org/index.php?threads/unable-to-install-on-hp-dl360-g3.1470/
    that one in particular seems to have a work around:
    "The trick is to disable in the BIOS the Virtual Media in Advanced Options and to boot FreeNAS Installation without ACPI. Then the installation starts on the DL380.
    After FreeBSD is installed you need to disable the HP PCI USB Controller in the BIOS so that FreeNAS will boot on this Hardware."

    is that what you tried to do?



  • @kaneda:

    I am trying to install a pfsense on a HP proliant DL360G3 working perfectly with a Pfsense 2.1.5
    When trying to update to 2.2 it hangs on boot after reset.

    Another DL360G3 user reporting in. Running two setups with this hw and upgraded one of them from 2.1.5 to 2.2. After upgrade and reboot I'm
    also facing hang up after USB controller lines. This is what I'm seeing on screen, sounds most likely identical: http://i.imgur.com/ibza83q.jpg

    @cmb:

    Seems there are several reports of that system working fine with FreeBSD 8.x (which was the base of our 2.0x and 2.1x releases), but not working with 9.x nor 10.x.
    https://forums.freebsd.org/threads/freebsd-10-0-on-hp-proliant-dl360-g3.45025/
    https://forums.freenas.org/index.php?threads/unable-to-install-on-hp-dl360-g3.1470/
    that one in particular seems to have a work around:
    "The trick is to disable in the BIOS the Virtual Media in Advanced Options and to boot FreeNAS Installation without ACPI. Then the installation starts on the DL380.
    After FreeBSD is installed you need to disable the HP PCI USB Controller in the BIOS so that FreeNAS will boot on this Hardware."

    I also found this one and found that Virtual Media was already disabled. Switching it on seems to have no effect on this matter. Next on the list was to disable the USB-controller but still experiencing hang up with OP's "random: unblocking device".  (Pic: http://i.imgur.com/8tKfebU.jpg )



  • Exactly the same steps, first it hangs on the USB line, but after disabling it it is stcuk on "random: unblocking device"

    I also tried to disable virtualmedia, reinstall without acpi, all workarounds you wrote and the  result is boot stopped with last message "random: unblocking device"



  • The only think now enabled that I dont need is the ILO card, and i can not disable it on the BIOS.
    Are you sure you have a DL360 Generation 3 (G3), perhaps you have a newer generation server that does not conflict with FreeBSD 10.
    Thx for comment!



  • Dont worry johnkeates, if it is not same version, it is not the same hardware so thats is the problem.
    For some reason PFsense crashes on DL360G3 hardware but FreeNas no, using same bios parameters, so the problem must be something owned by pfsense, the freebsd below them are the same.
    Perhaps something about IPSEC new service,the line random: unblocking device appear to mean it is sniffing data from different devices and sensors to generate some kind of entropy and trying to use something not compatible it hangs.

    If anyone can feed more info about this will be nice beacuse this appears to be not a FreeBSD problem, this is a Pfsense problem,  and lot of people gonna have firewalls frozen when they click on update over this machines.



  • @kaneda:

    For some reason PFsense crashes on DL360G3 hardware but FreeNas no, using same bios parameters, so the problem must be something owned by pfsense, the freebsd below them are the same.

    FreeNAS doesn't use FreeBSD 10.x yet. Though from everything I've seen, it's a regression in FreeBSD between 8.x and 9.x (and there are links earlier in this thread of this same problem on FreeNAS), and if you do some searching there are multiple reports of the same issues with FreeBSD 10 and that hardware. I saw enough in my searching to tell it's definitely the same in stock FreeBSD of the same version.

    Happens from time to time. It's probably a bug in the hardware that software doesn't work around, given it's only one specific server model. Someone with one of these systems, try putting stock FreeBSD 10.1 on one, and reporting the problem to FreeBSD by submitting a PR.



  • just as hint I had to do the following to boot a FreeBSD 10.1 cd with HP DL360 G3:

    • boot the cd and select "3] escape to loader prompt"
    • disable the dma for atapi
        set hw.ata.atapi_dma=0
    • after the installation open the prompt and put hw.ata.atapi_dma='0' in /boot/loader.conf.local

    pfsense 2.2 may need something similar on HP DL3x0 G3



  • I had to get my FW back to work fast and reverted it back to 2.1.5 with backup as it seems to be working fine with DL360 G3.

    @lsense:

    just as hint I had to do the following to boot a FreeBSD 10.1 cd with HP DL360 G3:

    • boot the cd and select "3] escape to loader prompt"
    • disable the dma for atapi
        set hw.ata.atapi_dma=0
    • after the installation open the prompt and put hw.ata.atapi_dma='0' in /boot/loader.conf.local

    pfsense 2.2 may need something similar on HP DL3x0 G3

    Luckily I have one idle DL360 G3 for a testbed and tried this with pfSense 2.2 LiveCD. I can happily confirm, that with this fix FW boots up nicely. It should also fix the broken system
    after 2.1.5 upgrade which I'll be trying to reapply later. Thanks lsense, you're the man!  ;)

    It seems that it really was struggling with drives as pfSense loads cd0 and da0 right after the usb lines it hanged up before disabling dma for atapi. Just wondering if there's any way for pfSense to detect this specific HP model and
    apply fix automatically on future versions?



  • Thanks for the tip lsense! Sounds like DMA is quirky on that hardware. I edited your post to specify loader.conf.local so people who make that change don't have it overwritten by upgrades in the future. That's also best on stock FreeBSD for the same reason.

    @grep:

    It seems that it really was struggling with drives as pfSense loads cd0 and da0 right after the usb lines it hanged up before disabling dma for atapi. Just wondering if there's any way for pfSense to detect this specific HP model and
    apply fix automatically on future versions?

    Just put that change he mentioned in /boot/loader.conf.local and it'll survive upgrades so you'll never have to worry about needing to change that again.



  • Thx guys!
    Will try this night
    In my case Im upgrading over internet from a 2.1.5, so Im gonna reinstall 2.1.5 and modify /boot/loader.conf.local
    And will try to upgrade again.
    Dont understand why it hangs accesing a CD drive while booting, after upgrading from internet, but appears the entropy generator uses data from cd/dvd devices and perhaps that the reason why it crashes.

    Will try tonight and post feedback about the results.



  • Confirmed
    I reinstall a clean 2.1.5 and did basic config

    edit the boot file /boot/loader.conf to add the line hw.ata.atapi_dma="0"
    created a new one /boot/loader.conf.local and put the line hw.ata.atapi_dma="0"

    Upgrade from the internet to 2.2 and next boot with new version was done without problems.

    Thx guys !!!