Dell PowerEdge

PCIe NVMe storage can provide an incredible speed boost to any server but booting from it is not natively supported on some older Dell PowerEdge servers.

11th and 12th generation servers like the Dell PowerEdge R710 and R720 are very popular amongst the home lab community and could benefit from a fast boot device.

This procedure should work on any Dell PowerEdge Server that can boot from a USB device.

Booting from NVMe storage is simple to do. In this post I am going to explain how it’s done and show the benchmarks from both a Dell PowerEdge R310 and T320.

Hardware you will need:

• Two USB Flash drives:
  • One to run clover bootloader. I used this tiny Sandisk Ultra Fit Flash Drive.
  • One for your bootable Windows ISO.
• A PCI NVMe Adapter and a NVMe Drive:
  • I used this cheap NVMe to PCIe adapter from Amazon.
  • With a Samsung 970 Evo Plus also from Amazon

I also tested the process on an 1.2Tb Intel DC P3520 PCIe card, which also worked fine.

Software you will need:

• A Windows Server Installation ISO
• Rufus to create the bootable Windows Installation.
• Boot Disk Utility

PCIe NVMe Boot Process

When this procedure is complete, the PowerEdge server will boot from the internal USB storage and run the Clover EFI Bootloader. Clover will contain the NVMe boot driver and boot the installed operating system from the NVMe storage.

If your server has internal SD card storage, you could boot from that instead.

Install the NVMe Adapter and Drive

First install the NVMe adapter and drive into your Dell PowerEdge server. I used this cheap adapter from Amazon and a 500Gb Samsung 970 Evo Plus.

Here is the unit before I installed it into the server without the heatsink applied. It comes with regular and low profile PCIe bracket:

And here is the unit installed in the PowerEdge R310 with the heatsink and thermal pad applied:

Create your bootable Windows Server Installation

The first step is to create your Windows Server Installation USB Stick. There are lots of guides on how to do this but I will show how I did it.

• Download and Install Rufus.
• Point Rufus to your Windows Server ISO.
• Configure Rufus with the following options:
  • Partition Scheme: GPT
  • Target System: UEFI (non CSM)
    
    

Install Windows in the normal way

Windows Server 2012 R2 and newer have Microsoft NVMe drivers built in, so it will see the NVMe storage and offer to install to that location.

When Windows setup is complete it will reboot. It will be unable to do because the Dell UEFI does not have any NVMe support. But don’t worry about that!

Setup the Clover EFI USB Boot Stick

Now setup the Clover USB Boot stick or SD Card.

• Download and run Boot Disk Utility.
• Insert the USB Stick that you are going to boot from into your PC.
• Select your USB Stick and click format:
  
• Open your newly formatted drive and copy \EFI\CLOVER\drivers\off\NvmExpressDxe.efi to:
  • \EFI\CLOVER\drivers\BIOS
  • \EFI\CLOVER\drivers\UEFI

Copying the NvmExpressDxe.efi to the drivers folder adds NVMe support to Clover which will enable booting from the Windows Installation that has just been completed.

My \EFI\CLOVER\drivers\UEFI looks like this:

Insert the Clover USB Flash Drive or SD Card into your server

Next simply insert the USB flash drive or SD Card into your server and set the UEFI boot order on the server to boot from it:

Ensure your UEFI Boot order is set correctly and pointing to your Clover USB Stick or SD Card:

When booting from the internal Clover USB stick it will briefly display a boot screen:

The clover defaults worked right away for me and I didn’t have to configure anything.

You can modify the config.plist file (which is in the root of the USB Stick) to reduce the timeout if you want to speed things up a little bit:

<key>Boot</key>
<dict>
	<key>#Arguments</key>
	<string>slide=0 darkwake=0</string>
	<key>#DefaultLoader</key>
	<string>boot.efi</string>
	<key>#LegacyBiosDefaultEntry</key>
	<integer>0</integer>
	<key>#XMPDetection</key>
	<string>-1</string>
	<key>CustomLogo</key>
	<false/>
	<key>Debug</key>
	<false/>
	<key>DefaultVolume</key>
	<string>LastBootedVolume</string>
	<key>DisableCloverHotkeys</key>
	<false/>
	<key>Fast</key>
	<false/>
	<key>Legacy</key>
	<string>PBR</string>
	<key>NeverDoRecovery</key>
	<true/>
	<key>NeverHibernate</key>
	<false/>
	<key>RtcHibernateAware</key>
	<false/>
	<key>SignatureFixup</key>
	<false/>
	<key>SkipHibernateTimeout</key>
	<false/>
	<key>StrictHibernate</key>
	<false/>
	<key>Timeout</key>
	<integer>5</integer>
</dict>

Modify the “integer” value on line 36 to reduce the boot delay.

Windows should now proceed to boot normally directly from the NVMe drive.

Performance Results

I was really impressed with how much faster both machines PowerEdge are when booting from the NVMe drive. For the purposes of clarity the config of these systems are:

Dell PowerEdge R310
Intel XEON X3470 2.93GHz
16Gb Ram
Dell PERC H700 (512mb)

Dell PowerEdge T320
Intel XEON
32Gb Ram
Dell PERC H710 (1Gb)

Performance of the Samsung 970 Evo Plus NVMe Drive was excellent in both machines. But the drive performance is constrained in the R310 because it has a PCI Gen 2 x 4, whereas the T320 has PCI Gen 3.

Disabling C States in the BIOS increases performance in both machines.

Here are the results from a CrystalDiskMark from the R310 with C States Disabled:

Here are all the results from both machines with and without C States Enabled.

Test Type	C State	Machine	Read Result (MB/s)	Write Result (MB/s)
SEQ1M Q8T1	Enabled	R310	1670.13	1636.13
SEQ1M Q8T1	Disabled	R310	1811.27	1760.90
SEQ1M Q1T1	Enabled	R310	1359.94	1346.70
SEQ1M Q1T1	Disabled	R310	1529.41	1498.86
RND4K Q32T16	Enabled	R310	1147.30	1351.01
RND4K Q3T16	Disabled	R310	1149.57	1346.97
RND4K Q1T1	Enabled	R310	35.95	85.65
RND4K Q1T1	Disabled	R310	37.96	93.31
SEQ1M Q8T1	Enabled	R320	3339.91	3124.31
SEQ1M Q8T1	Disabled	R320	3576.68	3265.89
SEQ1M Q1T1	Enabled	R320	2303.26	2510.44
SEQ1M Q1T1	Disabled	R320	2421.82	2793.11
RND4K Q32T16	Enabled	R320	1150.97	1557.42
RND4K Q32T16	Disabled	R320	1145.25	1558.19
RND4K Q1T1	Enabled	R320	33.23	101.27
RND4K Q1T1	Disabled	R320	43.98	111.05

As a crude comparison here is the performance of a RAID 0 Array in the R310 comprising 4 x 7,200 RPM SATA Drives:

This R310 server also has a Samsung 860 EVO SSD in the DVD Drive bay, which is connected via a SATA 2 port on the motherboard:

You can see the performance of the drive being constrained by the SATA2 port, but it still gives good random performance.

If you are using VMWare then you can just access the NVMe drive in the normal way if you are booting from a different storage device such as SD Card or USB Stick.

Conclusion – is it worth adding NVMe storage to a old Dell PowerEdge?

Given the low cost of both the adapter and Samsung SSD and the huge resulting performance boost, it is certainly worth experimenting.

I can’t say if I would use this setup in production yet, but so far, it seems to work fine. Here is an image of Samsung Magician Drive information:

Installing an SSD to the optical drive by on a 13th Generation Dell PowerEdge is really easy. The only thing you really need to know is that the bay is 9.5mm high. I used this caddy from Amazon.

I installed the SSD into a PowerEdge R330, it works really well. Here is the SSD Installed in the Optical Drive Bay:

ESXi is installed on 2 x 32Gb SD Cards, the SSD is free to be used as a data store:

There is a second SATA connector on the motherboard and space at the front where you could install another SSD. But I haven’t tried that.

I haven’t used the DVD Drive on a Dell server in years, an SSD makes better use of the space. You could use it as a normal data store or perhaps a flash based read cache in ESXi.

The Dell iDRAC is so useful for many things, but in its default configuration it is very insecure:

• The default username is “root”
• The default password is “calvin”

In this post I will show you how both rename the root account and change the password.

Renaming the root account adds a layer of obscurity making it more difficult for unauthorised users to gain console level access.

How to rename the iDrac root account and change the password.

• Login to the iDRAC using your credentials or use the default if they have not been changed
• On the left hand menu, choose “iDRAC Settings” and then “User Authentication”:
  
• Click on the User ID that corresponds to the root account, to edit it:
  
• The default action of “Configure user” should already be selected, so click on “Next”
• Change the username as per your preferences and set the new password:
  
• Scroll to the bottom of the page and click apply.
• Log-out of the iDrac and check your new settings.