Skip to main content

Adding a SATA controller to Dell PowerEdge T30 server - more drives and UEFI

The Dell PowerEdge T30 is a very compact and affordable server with Intel Xeon CPU and 8 GB RAM. In contrast to Lenovo and some others, drive caddies and SATA cables are included here and there are no artificial limitations built in.

Now you can connect 4 disks to Dell's onboard SATA Intel controller. But if you want to use it as e.g. a high performance NAS and run Windows Server 2016 you will probably need more than 4 SATA ports!

In my situation I wanted to install a small Samsung SSD as a boot drive (there is space for it in the case), connect the internal DVD-ROM and also add 4 x 10 TB Seagate Enterprise Capacity (Exos) hard drives for NAS functionality - so a total of 6 drives. Using Windows storage spaces in mirror mode, maybe with ReFS 3.1 should replace a hardware RAID controller and make it even more reliable.

So in order to be able to use 6+ SATA drives I needed an additional PCIe SATA controller; this is even stated in Dell's manual. After a lot of research it turned out that the affordable Syba sd-pex40099 4 Port SATA III PCI-EXPRESS 2.0 x 1 Controller with Marvell 88SE9215 chip from Amazon should work ok with the server so I immediately ordered it. What I received was actually an IOCREST SI-PEX40064 but it looks like this is the same card as the one ordered.

Then I connected my SSD to the first port of the Syba (Iocrest) SATA controller and Dell's DVD-ROM to the second.
IMPORTANT:
Now make sure that there is also at least one drive connected to the ONBOARD SATA controller, otherwise the server won't boot no matter what you do but give you this strange error:
"Alert! Hard Drive or Optical Drive not found." (Thank you Dell for wasting my time before I found out what was causing this...)

Now another tricky part was the BIOS configuration, I did a lot of trial and error to make it work. It is important to perform the following steps:

1. You can use UEFI so first enable it under Settings -> General -> Boot Sequence in the BIOS

2. In order to be able to boot from the Add-On SATA card you also need to check Enable Legacy Option ROMs under Advanced Boot Options. Enable Attempt Legacy Boot is NOT needed.

3. It looks like you CANNOT use Secure Boot, as this is not usable with the legacy option ROMs setting. But this is not so dramatic I think...

That's it. I hope this post is helpful!

Have fun,

Anguel

BTW: Performance for the SSD on the add-on SATA controller is quite good for a Samsung 840 Pro SSD: ~ 400 MB/s.

Comments

Popular posts from this blog

SOLVED: Making Wake-on-Lan (WOL) work in Windows 10 / 8.x

WINDOWS 10 UPDATE: THIS FIX ALSO APPLIES TO WINDOWS 10 , IT IS EVEN MORE IMPORTANT,  BECAUSE WINDOWS 10 TURNS "FAST STARTUP" (read below) BACK ON AFTER UPDATES (yes, Microsoft does not stop creating nonsense features / bugs). TO DISABLE FAST STARTUP ON WIN 10 THROUGH GROUP POLICY PREFERENCES CREATE THE FOLLOWING KEY: HKLM\System\CurrentControlSet\Control\Session Manager\Power\HiberbootEnabled and set its value to 0 ! I had very serious problems getting Wake-On-Lan (WOL) to work on my new Dell Optiplex 9020 MT (MiniTower) on Windows 8.1 Pro. I finally got this to work and would like to share my experience here. Note: At the time of this writing the current Dell BIOS for Optiplex 9020 MT was A05. UPDATE: The same behavior is also observed with DELL BIOS A07. Maybe Dell needs to comply with some power saving requirements and therefore enables Deep Sleep instead of Wake-On-LAN? Whatever the reason is, it is extremely annoying that this is the default and it is not ...

Changing the Reserved IP Address in a Static DHCP Reservation in Windows Server

  Static IPs preferred DHCP is a good thing if it works - set and forget. But what happens if the DHCP server is down for some reason? Exactly - the whole network stops working. Another problem of DHCP are those random IPs a client gets each time. This is very bad for printers that use DHCP. Therefore I prefer static IPs over dynamic.   Windows Server 2012 R2 Essentials: You cannot stop Windows LAN Configuration Service anymore Unfortunately, there is some strange behavior on Server 2012 R2 Essentials if you just enter static IPs on your Windows clients - your Windows OS will show exclamation marks on your network connection from time to time, etc. There is actually a Windows Server LAN Configuration service which keeps overwriting your manual settings and the bad thing is that you cannot stop that service in Server 2012 R2 any more for some reason...So, instead, I decided to use DHCP on the server and add an Alternative IP Configuration with all static data as...

Veeam Backup & Replication: "Failed to execute script in guest OS" (Linux Guest VM on Hyper-V)

Problem: Veeam Pre-Freeze / Post-Thaw .sh Scripts Fail on Linux Guest VMs (e.g. Ubuntu) with "Failed to execute script in guest OS" although the scripts run fine. I use Hyper-V but that should not matter. Failing scripts are configured to "Require successful script execution" under "Application-Aware Processing Options" under "Guest Processing" in the Veeam backup job. My Solution: Some commands executed inside the scripts seem to return error output which is passed back to Veeam through the script and confuse Veeam so it reports that the script was not successful. So we must redirect error output from such commands to 2>/dev/null or some file, otherwise error status is passed back to this script and Veeam reports a failure. For information about discarding error output, see https://bash.cyberciti.biz/guide//dev/null_discards_unwanted_output Additional information: Also make sure that Veeam scripts (*.sh) are located on the Veea...