HP Proliant Microserver Gen8

I’ve been a fan of HP’s Microserver line for many years. I bought my first one in 2011, my second one in 2013 and my third one a few days ago. All of them are running non-stop since I bought them. They have proven to be true Proliant servers, in the sense of having good reliability and build quality.

But the latest one (Gen8) is by far the most “Proliant” of them all (more on that later).

2015-12-22 00.39.59

Let’s start by getting the specs out of the way. I bought the 819185-001 model, which comes with:

  • One Intel® Celeron® G1610T (2.3GHz/2-core/2MB/35W) Processor
  • 4GB (1 x 4GB) PC3L-12800E DDR3 UDIMM
  • HPE Ethernet 1Gb 2-port 332i Adapter
  • HPE Dynamic Smart Array B120i Controller
  • 150W Non-Hot Plug, Non-Redundant Power Supply
  • HPE iLO Management Engine

It has pretty good connectivity, since it comes with 7 x USB ports (2 of them USB 3.0), 3 x GbE Ports (one of them is the dedicated iLO port, more on that later), one PCIe x16 slot, etc.

2015-12-21 19.18.20

It supports 4 internal HDDs and an internal slim DVD-RW drive. Since it is 2016 (no-one needs DVD-RW drives any more), I decided to make better use of the server’s fifth SATA port by using it to connect an SSD system drive. Getting the SATA cable from the mainboard to the top of the case was no problem, but powering the SSD was. The server has a spare power connector, but it is meant to power HP’s DVD-RW drive which (oddly enough) has an old floppy drive power connector. I did not want to cut the cable and splice in a proper SATA power connector, so I did the sensible thing. I robbed an old floppy drive of its most precious component: Its power input jack.

2015-12-21 19.31.57

I made sure that it mated properly with the server’s connector.2015-12-21 20.21.48-2

And I soldered on an old SATA power cable I had. I used heat shrink tubing (of proper colors of course :P) to make sure that there would be no possibility of shorts.2015-12-21 20.38.092015-12-21 20.40.17

So now I had my SSD installed and it was time to install the OS.

2015-12-22 00.29.17

This is where things get interesting. Remember, this is a proper Proliant server. What this means is that it has a pretty strict operating system compatibility list, and no consumer OS are officially supported. So, Windows Server 2012R2 and 2008R2 are OK, Windows 8.1 is not. I normally run Windows Home Server 2011 (which is based on Server 2008) so I should be OK, but I decided to get started with a trial of the full fledged Windows Server 2012R2 (just for the experience..).

Installing an OS is supposed to be a simple procedure. HP’s Intelligent Provisioning takes care of drivers and server applications for you, but before you get to that there are a number of things to do.

We are dealing with an actual server here, so inexperienced users should definitely start by reading the manual or at least the quick start guide that comes with the server. If you do not do that, you should not expect to get very far. You will waste a few hours, wondering why Windows is not installing and what you are doing wrong.

One of the first things to do is to decide whether you want to make use of the server’s Dynamic Smart Array RAID controller of not. You have a choice. You may run it either in AHCI mode (a.k.a. “dumb mode”) or in RAID mode. There are merits to either mode. If you go the AHCI route, you will get to keep your drives’ existing data (which would be wiped clean if you went the other way) and that data will be visible from other machines if you decide to take the HDDs out and put them inside some other machine. So the main drawback is noise. That’s right, the server’s main fan will run a lot quieter if you set your Smart Array controller in RAID mode. In fact, this way it will run even quieter than the previous generation of Microservers. I chose to go this way. So, first order of business is to create an array. You may create a RAID0 or 1 array if you have 2 or more drives or RAID0 if you have one. I would have a number of drives in my server, but I did not want redundancy, so I started with one RAID0 array consisting of my SSD system drive.

2015-12-21 21.01.31

Next up was a firmware update for the server’s subsystems. There is a bewildering array of firmwares that may need updating. Good thing that the process is automatic and is done from within the server’s BIOS, before you install the OS. The same goes for driver updates – they are downloaded automatically before the OS installation begins. Note that the firmware & driver updates come from HP’s web site (obviously..), so you should have at least one ethernet cable connected to your ethernet switch. The server will use DHCP to get on your network. Keep in mind that the firmware update when done this way is actually not very effective, meaning that chances are that there are newer versions of your firmwares available from HP’s site, but you should not worry about that just yet.

Do use HP’s Intelligent Provisioning to install your OS of choice, preferably from a USB installation medium. I know that there exist unofficial (and thus unsupported) ways to install non-supported operating systems, such as Windows 8.1, but I have not done any serious research into them. YMMV.

2015-12-21 21.46.51

The server will reboot (several times actually..) and you should be patient. Each reboot takes more than 2 minutes, since the server does extensive testing of its subsystems (processor, memory, controllers, iLO, etc).

2015-12-22 20.17.38

You may have noticed that I now have 8GB of RAM installed. I added a 4GB ECC DDR3 DIMM that I had bought for my first Microserver (from 2011). I no longer see the “Genuine HP Memory” message since it is (if I remember correctly) a Kingston DIMM, but I do have twice as much memory, so I can live with that. This memory stick is not officially supported, and it is a bit slow compared to the one that came preinstalled, but it works just fine and 8GBs of RAM offer much better overall performance than 4GBs.

Once you have Windows installed, you should got to HP’s site and register your server. This way you will have access to official support plus HP’s up-to-date ISO file (Service Pack for ProLiant) with all the latest drivers, firmwares, etc. You should mount that ISO image and install the relevant software. You will get useful tools for managing your Smart Array controller, making firmware and driver updates, viewing logs, etc.

You should also make use of your iLO 4 system.

2015-12-21 19.19.10

It will give you remote access to your server’s console without having a monitor connected (up to the time that the OS loads) and a bucketload of diagnostic information such as fan speed, temperatures, etc.

Gen8 temperatures

Once I had the OS installed, I moved my 4 x 3TB WD RED drives from my old Microserver to the new one, one at a time (copying the data through the network link). Now I’m waiting to receive a PCIe e-SATA controller that is compatible with the Gen8 Microserver so that I can connect my Lian Li DAS enclosure with its port multiplier interface and its 5 extra SATA drives.

Pipo X7: An ultra low cost Windows PC as a music transport

A few days ago I received the Pipo X7 that I had pre-ordered back in January.

It took so long to source & ship because it is immensely popular – after all, for less than 100€ I got:
– An Intel Baytrail Quad Core CPU @ 2.16GHz
– 2GB of low power DDR3 RAM
– A 32GB SSD drive (Samsung MBG4GC)
– An HDMI out
– WiFi b/g/n, 10/100Mbps Ethernet & Bluetooth connectivity
– 4 x USB 2.0 ports

All of that inside a slick aluminum box, not much larger than a CD, powered by a silent 12V/2.4A power supply.


But the best part is that it runs a fully activated copy of Windows 8.1 (32bit)!

Yes, Microsoft is essentially giving away Windows 8.1 for use in small devices (like set-top boxes, such as this one) with only one catch for the OEM: He is not allowed to set Google Search as the default search engine. However, this does not mean that you can not set Google as your preferred search engine if you wish (instead of the dreadful Bing).

Now, I must admit that this was largely an impulse buy for me, since I already have a full size HTPC and a Squeezebox Touch as an audio transport, but I just couldn’t resist the temptation. So, since I had it, I decided to run a series of audio-oriented tests on it.

My player of choice is Foobar, feeding a Buffalo III DAC through an Amanero Combo384. The files were stored on a file server on my LAN and the Pipo was connected to the LAN via 100Mbps Ethernet.

The first test included outputting DSD to the Amanero. All the necessary Foobar components were loaded, including of course the Super Audio CD Decoder and the necessary configuration was performed:

Note: There are several steps involved in getting Foobar to output DSD. It is not the purpose of this post to fully outline them. A Google search would turn up a number of guides / how-tos.

First up was a “plain” DSD64 file. The Pipo had no problem playing it back, with less than 1GB of RAM use and about ~13% CPU utilization:


Let’s make it more interesting. DSD128:


Still no problem. As a matter of fact, CPU load has actually decreased! That is probably because the DSD64 file was from a SACD ISO, so some CPU time was used in handling the big file.

Moving on to a worst case scenario: A DXD file:


Still, no sweat, with the CPU barely sweating at 16% load. RAM has not climbed above 800MBs.

Since the machine appeared to have some decent horsepower, I thought I would try the well-known SoX Resampler DSP for Foobar. I set it up as best I could, since I don’t really have much experience with the actual DSP:


I chose to go the “x4” upsampling way, with the “Best” quality setting. This meant that a 44.1KHz file would be upsampled to 176.4KHz and a 96KHz file would be upsampled to 384KHz, hitting the limits of the Amanero interface. A 192KHz file would not be supported, since that would mean that it would have to be upsampled to 768KHz. The idea was to do a benchmark, so I just played two versions of the same files, one at 44.1K and one at 96K. This was the result:



So, still no serious sweat, with the CPU averaging 29% load, with one of its cores (presumably the one doing the actual upsampling) getting about 50% usage.

At that point, I called it a day.

In conclusion, it seems that the Pipo X7 is perfectly capable of supporting audio playback, even with upsampling enabled. As a matter of fact, I might keep it as a music transport.