Installing Proxmox on a Dell PowerEdge R240

Hi there!

2024 started out with the VMware-Broadcom acquisition being completed. Once the sale was completed, Broadcom did not hold back in reorganizing and restructuring a once stable and fantastic company.

If you are reading this, it’s likely because you are exploring alternative Hypervisors, be it for your home lab or for your organization.

This guide is a very basic one and it just covers how to setup Proxmox on a Dell PowerEdge R240 which has the PERC S140 RAID controller.

When deciding how to configure the server for installing Proxmox, you have the choice of using the PERC S140 RAID controller in RAID-1 or to leave the drives running without RAID and configure Proxmox with ZFS.

This guide will focus on not using the Dell S140 RAID controller. There are many discussions about how to prepare the server for the OS install and it seems to be not recommended to load ZFS on top of hardware RAID.

My R240 came with RAID-1 enabled on the PERC S140 with two 960GB SSD drives. I am doing all of this work remotely using Dell OpenManage Enterprise. My Dell R240 did not have an enterprise license so I am using a free 30-day trial license from Dells Trial Licenses iDRAC page here.

***Before you do anything with the following settings, backup any data that you require as modifying the server from RAID to AHCI mode will cause data loss on your disks.***

Booting up the server, press F2 to enter System Setup. Once the System Setup page loads, select the System BIOS option. On the next screen, select SATA Settings.

Once the SATA Settings page loads up, you will need to set the Embedded SATA setting to AHCI Mode. We want the serve to present the disks to Proxmox as a bunch of drives without any RAID control. We will allow Proxmox to protect our disks with a ZFS Mirror.

Acknowledge the Warning alert about the data loss and press OK.

You will be taken back to the System Settings page. Click the Finish button and confirm it with Yes.

To install Proxmox, we need to load up a Proxmox ISO and reboot the server. I am doing this all by using Dell OpenManage Enterprise.

We need to load up the Virtual Media section. If you see the option at the top of the page, click Virtual Media.

The Virtual Media section will now load up. You will see a few options on the left. We are going to make sure we are under the Connect Virtual Media setting. It should indicate that virtual media is disconnected. Click Connect Virtual Media.

Next, under the Map CD/DVD section, click on Choose File and select the Proxmox ISO you will be using. Then click the Map Device button. You will no see that the ISO file is mapped to the CD/DVD Drive.

We will reboot the server and tap F11 to enter the Boot Manager setting. With Boot Manager loaded, select the option One-Shot BIOS Boot Menu and on the next page, select the *Virtual Optical Drive setting.

The server will boot using the Virtual Media we loaded up previously. After a few moments, you should now see the Proxmox installation menu.

I am going to install Proxmox with the Graphical installation. Use the arrow keys to select your option. You will next have the opportunity to review the EULA.

After the EULA, you will be asked to select the Target Harddisk. In my case, I have both of my SSDs listed but I am going to proceed into the Options section.

Once the Harddisk Options menu loads, you can choose your filesystem. In my case, I will use ZFS (RAID-1). With the filesystem selected, click on the OK button.

You should see the Harddisk Options menu confirming your selection. If you have selected ZFS, you will a message within the window that indicates that ZFS is not compatible with hardware RAID controllers, and to reference the documentation for further information. Press the OK button to confirm your settings.

The next few screens will ask you to set your country, time zone and keyboard layout. Press Next when you are ready to continue.

You will now see the Administration Password and Email Address configuration page.

Set a secure password. This password is for the root account, so it will need to be complex and secure. When ready, click Next.

The last and final page will be the Management Network Configuration section.

Select your Management Interface, in my case it is Eno1, the only interface with a LAN connection.

Set your Proxmox hostname in FQDN format. You can use something like PVE01.Lab.com.

Set the IP networking. I’m setting my installation to be static IP addressing and I know what addressing I will use. If you have DHCP enabled and your network port is untagged/access configured or you are using a basic switch, you may have this information already prefilled based on the DHCP settings. Click Next when ready.

The last screen of the install will be the formatting of the drives and the installation process. Proxmox will be installed and will load up shortly. The installation process should be fairly quick.

When the installation completes and the server reboots, you should see a welcome message, which provides you the management IP and port of this nodes Proxmox installation. You will also see a local logon prompt.
At this time, you can just open up the browser and go to the https://IP:8006 and access your Proxmox web gui, seen below.

There are many good guides out on the internet for Proxmox. Below I will link some official documentation along with a few other technical sources that you can use to learn Proxmox.

Proxmox Wiki Main Page

Proxmox Installation (Wiki)

Proxmox Forum

Proxmox Roadmap

Official Proxmox Training

r/Proxmox

Learn Linux TV has a fantastic Proxmox Course

Hope this helps some of you out there. I’ve migrated my homelab from VMware to Proxmox so I will be focusing heavily on Proxmox content. I still work with VMware environment(for now) so I will cover VMware related items that I see fit, but I imagine it won’t be much as we are exploring our options of alternative Hypervisors.

Thank you!

Convert Disk from RAID to Non-RAID – Dell PERC H730 Mini

Last week I was working on setting up two new servers at a new office about 6,000 km away. Initially, everything was going smoothly on Server #1 until I tried to configure the second server in a similar manner.

Let me explain…

We are using the following:
-Dell R730xd servers
–Bios 2.12.1
–iDRAC firmware: 2.75.100.76
-Dell PERC H730 Mini
-Seagate ST8000NM0065 SAS (6 of them)
–Revision K004
-Two volumes
–OS (RAID-1, SSDs)
–Storage (RAID-6, Seagate)

What we did on each server for the OS boot drive is combine two enterprise SSD disk into a RAID-1 configuration. This worked well for us as expected.

While investigating some options for local storage that could possibly be shared, we wanted to do some testing with Microsoft’s Storage Spaces Direct, which required us to remove the Storage Volume and convert the disks from a RAID to Non-RAID configuration.

Server #1 was completed successfully. Entering the iDRAC configuration, we expanded Overview –> Storage and then selected Virtual Disks.

We clicked on Manage and deleted the chosen volume via the drop down option under Virtual Disk Actions.

Once the volume was deleted, we needed to convert each disk from a RAID drive to Non-RAID drive.

This is done by going into the Physical Disks section under storage (within the iDRAC menu) and going to the setup section.


From there, you would just click the Setup section at the top, select each or all disks that you want to reconfigured for Non-RAID and select apply.

This worked great for the first server but not so much for the second server.

When doing so, the job would be accepted and checking the Job Queue which is under the Overview –> Server section, we noticed the following basic error message: PR21: Failed

Since the message didn’t provide enough information, we went to the Logs section under Overview –> Server and selected the Lifecycle Log section.

Here you can possibly get slightly more details but in our case, it wasn’t enough to figure out what was going wrong.

We started off by searching that error message on Dells website and found the following:

We couldn’t find out why we were not able to reformat the disks into a Non-RAID configuration. Server #1 completed this without issues. We compared both servers (exact same spec) and there was nothing out of the ordinary.

We stumbled upon an interesting Reddit post that speaks about a very similar situation. The user in this case had 520 bytes sector drives and was trying to reformat them to 512 bytes.

We compared the drives between both servers and everything was the same. We couldn’t perform the exact steps as identified on Reddit since we couldn’t get the drives detected and we didn’t have any way to hookup each SAS drive to a 3rd party adapter and check the drive details.

We decided to do a test and shut down both servers and move the drives from one unit to the other, thanks to our remote office IT employee. Doing so would identify if the issue is in fact with the drives or with the server/raid controller/configuration.

With the drives from server #2 into server #1, we were able to format them into a Non-RAID configuration with ease. We knew our issues were with the server itself.

Diving more into Dells documentation, we found one area that was not really discussed but required to reboot the server and tap F2 to enter the Controller Management window.

Here, we looked around and found what we believed to be the root cause of our issues, located in Main Menu –> Controller Management –> Advanced Controller Properties.

Look at the last selection, Non RAID Disk Mode, we had this as Disabled!

This wasn’t a setting we setup and the initial testing was done by our vendor a great distance away.

We choose the Enabled option for Non-RAID Disk Mode and applied and restarted the server

With that modified, we loaded back into iDRAC and we were finally able to select all of our disks and configure them as non-raid.

Once done, all the disks were passed through to windows and we were able to use them for our storage and to test Microsofts Storage Spaces Direct.

I wanted to take a few minutes and write this up as this was something we couldn’t pinpoint right away and took a bit of time to investigate, test and resolve.

Some resources that I came across that might help others:

http://angelawandrews.com/tag/perc-h730/

https://johannstander.com/2016/08/01/vsan-changing-dell-controller-from-raid-to-hba-mode/amp/

https://www.dell.com/support/kbdoc/en-us/000133007/how-to-convert-the-physical-disks-mode-to-non-raid-or-raid-capable

https://www.dell.com/support/manuals/en-ca/idrac7-8-lifecycle-controller-v2.40.40.40/idrac%20racadm%202.40.40.40/storage?guid=guid-9e3676cb-b71d-420b-8c48-c80add258e03

Thanks for reading!