Booting HP Proliant Server from an SD Card. The process is identical. Loading from USB media to SD operating system is only a little faster than USB to spinning disc. As an interactive user on the server, it performs very well. Even connecting through RDP is nice and fast. Boot time is almost identical between SATA RAID-1 drives.
Rafal Lukawiecki2017-08-08 22:23:28 UTCCreatedVerbose boot console output at hang pointI am unable to install/run FreeBSD 11.1 on a brand-new HPE MicroServer Gen10 containing an AMD Opteron X3421 with 16GB RAM. The installer hangs just after it prints:pci0: on pcib0Please see attached console screenshot showing verbose output which suggests that the boot process hangs just as it has collected information about the RAM on pcib0. This is while booting from a USB (several tried and tested and integrity validated) or when moving an existing pre-installed elsewhere system. Rafal Lukawiecki2017-08-09 17:35:29 UTCFollowing suggestion by Miroslav Lachman I have tested a few other releases of FreeBSD to see if this issue still persists and if it was a regression. Unfortunately, in all tests, 9.3-12.0-CURRENT, I get exactly the same error.
To be precise, these are the versions that I have tested:FreeBSD-9.3-RELEASE-amd64-memstick.imgFreeBSD-11.1-RELEASE-amd64-memstick.imgFreeBSD-11.1-STABLE-amd7-r322164-memstick.imgFreeBSD-12.0-CURRENT-amd7-r322167-memstick.img. Thomas Neuber2017-08-31 18:44:50 UTCAt first, I can confirm the behavior as described before.In addition to that: I had a working installation for a HPE Proliant Microserver Gen8 (Intel Xeon E3 v1220L). The old system did not support UEFI. The old installation (SD card copied 1:1 to a USB stick + the 4 hard drives) runs properly on the Gen10 after switching the settings to UEFI with CSM Enabled + Boot Mode Legacy Only - except the console. I expected the console menu after certain amount of time.The console output stops at:pcib0: port 0xcf8-0xcff on acpi0pcib0: OSC returned error 0x10pci0: on pcib0As I said, everything else works fine. Thomas Neuber2017-09-12 17:15:21 UTCI created an UEFI aware installation on a different PC and repeated the test as described in.
The overall behavior booting with UEFI is exactly the same as with legacy boot. All configured (network) services (samba, web, ssh, several jails, etc.) are up and running but the console hangs. From a remote location, everything is functional with the expected level of performance. But locally, it is still unusable.Let me know, if I should provide any additional information, run any test cases, etc. Thomas Neuber2017-10-05 17:19:30 UTC(In reply to Mikael D from )My system is up and running stable for the last 9 days. Last restart was after an update from Freenas 11.0 U3 to U4.
The headless use is definitely possible. The challenge was the installation without a working local console (VGA). I am not aware whether an installation from a remote location is possible and how does it works.
It utilized another PC to set up the system.The console does not work with any of the two Displayports or the VGA connector. Is the Carrizo chipset supported by the kernel?root@jupiter # uname -aFreeBSD jupiter.fritz.box 11.0-STABLE FreeBSD 11.0-STABLE #0 r321665+25fe8ba8d06(freenas/11.0-stable): Mon Sep 25 06:24:11 UTC 2017root@gauntlet:/freenas-11-releng/freenas/BE/objs/freenas-11-releng/freenas/BE/os/sys/FreeNAS.amd64 amd64root@jupiter # uptime7:00PM up 9 days, 1:05, 0 users, load averages: 0.14, 0.14, 0.16root@jupiter #. Mikael D2017-10-05 17:23:34 UTC(In reply to Thomas Neuber from )This is the first time ever that i encounter any.nix system that does not boot due to faulty VGA, kind of curious what the issue is.Anyway, I hope the FreeBSD people here can fix it and I'll try running it headless once i receive my MicroServer Gen10 next Tuesday. (I've gotten myself a Gen8 too so i can have one spare and use it to install FreeNAS to the USB).I'll do some tests and report my findings (though i think all is covered here already).Thanks for the quick reply! Jan Bramkamp2017-10-16 15:50:00 UTCFreeBSD can be installed on headless systems like the HP Gen 10 Microservers. The most common tool for the job is mfsBSD.
You can put mfsBSD on a USB stick and boot from the USB stick. MfsBSD includes some scripts to start dhclient on all ethernet like interfaces and starts the SSH server by default. You can either use the minimal install er script included in mfsBSD or run bsdinstall over SSH. Due to a bug in bsdinstall you have to create /usr/freebsd-dist and load the MANIFEST manually if you want to go that way. Rajesh2018-05-15 12:59:34 UTCI hit a similar issue when I try to install FreeBSD 11.1 release (memstick image), in one of our development boards.Sometimes, I see installation hangs after the below messagespcib0: port 0xcf8-0xcff numa-domain 0 on acpi0pcib0: OSC returned error 0x10pci0: numa-domain 0 on pcib0But, most of the time, I see a panic trace as seen in the attached image and the system reboots. I see the panic during PCI device attach (like 'hpetattach' or 'xhcipciattach'). It's like if I disable one device in BIOS, its proceeds furthur and panics in another driver.
![Hp proliant drivers Hp proliant drivers](http://www.mania-co.com/cp/img/Equipment/main/602/Front%20[1].jpg)
I could see 'OSC returned error 0x10' messages here as well(but it proceeds further without hang and then panics).I tried setting hw.pci.reallocbars=1 from boot loader prompt. It doesn't help.So, could this issue be related to the base issue reported in this bug? Rajesh2018-05-16 18:02:01 UTC(In reply to Bob Bishop from )Thanks for your response Bob. But I have couple of questions1. OSC returned error 0x10 - What does this message mean? Is it really an issue?2.
Before the panic, we see 'Unable to map MSI-X table' (since busallocresourceany call fails in xhcipciattach). So, driver falls to alloc MSI (pciallocmsi), which also fails because rmanmanageregion fails (in nexusaddirq).
So, does this mean PCI BAR mappings are not proper to allocate enough resources to the device? If so, what should be checked in this case? John Baldwin2018-12-14 17:30:18 UTCI think the patch is probably fine. This looks to be a BIOS bug. The failing memory BAR for the VGA device is '0xfeb00000' with a size of 256K.
However, ACPI reserves the first page of that range as a system resource (from devinfo -vr output without the patch):nexus0.acpi0.I/O memory addresses.0xfeb00000-0xfeb00fffFWIW, hw.pci.reallocbars is a bit of a conservative knob that I had considered enabling by default. I've added Warner to see what he thinks about possibly enabling this knob by default in HEAD. The current patch is probably fine to commit as-is and is probably safe to MFC as well since it is specific to that device id.
An HP Proliant DL380e Gen8 BIOS P73 using iLO4 suffers from USB CD/DVD drive boot issues after a reboot, as described in HP Advisory. External USB DVD drive details are:Product ID: 0x0719Vendor ID: 0x05e3 (Genesys Logic, Inc.)Version: 0.09Serial Number: 33Speed: Up to 480 Mb/secLocation ID: 0x1d111000 / 12Current Available (mA): 500Current Required (mA): 96Our workaround is to ' Restore Default System Settings'. Then it is possible to boot from the external USB DVD drive again.Is there anyone that has found a better workaround or solution to boot an HP Proliant from USB DVD drive? Yes, there is a better approach to booting your server from physical media than resetting your BIOS to factory settings every time.HP ProLiant Gen8 Server Series:USB Boot Support USB Boot Support controls whether the system boots from USB devices connected to the server. When disabled, this option also disables booting of iLO virtual media.
![Usb Usb](/uploads/1/2/5/4/125489891/399574872.png)
Options include:. Enabled (default). DisabledBooting from USB device:. Try with front and rear USB ports in the server. Booting into a External USB hard drive may not be supported. Avoid using USB hub while tring to boot.
Make sure USB key has bootable files.