Dell Software RAID Controller Support for Microsoft Windows Server 2012

OS and Applications

OS and Applications
Dell OS and Applications Solutions on Dell TechCenter - Project Sputnik, Microsoft Windows, Red Hat Linux, SUSE, Ubuntu, and more

OS and Applications - Wiki

Dell Software RAID Controller Support for Microsoft Windows Server 2012

OS and Applications - Wiki

This post was originally written by Barun Chaudhary & Perumal Raja from DELL Enterprise Operating System Engineering Team. Comments are welcome!

To suggest a blog topic or make other comments, contact WinServerBlogs@dell.com

 

Dell provides cost effective RAID support through PERC (PowerEdge Raid Controller) S100, S300 and S110. At present Dell supports only S110 controllers with Windows Server 2012. For S110 controller download and install the latest drivers from support.dell.com. Customers who are using Dell servers with PERC S100 and S300 controllers have to switch to one of the below alternate options if they want to install Microsoft Windows Server 2012 on their servers.

 

Option1: Converting PERC S100 into on-board SATA controller

Note: No data is migrated and this is not a replacement of PERC S100 solution. Data needs to be backed up before following the below steps.

  1. Power on the server and press F2 to enter the BIOS settings.
  2. Enter the BIOS setup -> SATA settings option and change it to ATA or ACHI mode whichever is available. Refer Figure-1.
  3. Save and Exit the setup.
  4. Boot from the Microsoft Windows Server 2012 DVD and complete the installation.

 

Option2: Switching to on-board SATA controller from PERC S300

Note: No data is migrated and this is not a replacement of PERC S300 solution. Data needs to be backed up before following the below steps.

  1. Open the server and remove the internal SATA cables connected to the S300 controller and connect it to the On-Board SATA controller ports of the server.
  2. Power on the server and press F2 to enter the BIOS settings.
  3. Enter the BIOS setup -> SATA settings option and change it to ATA or ACHI mode whichever is available. Refer Figure-1.
  4. Save and Exit the setup.
  5. Boot from the Microsoft Windows Server 2012 DVD and complete the installation.

Figure-1 : BIOS Setup Screen

 

Option 3: Buying a new supported PERC controller from Dell

You can purchase additional supported RAID controllers via the spare parts sales teams with a phone call to Dell or you can also order online via the S&P sales catalog.  To order online, go tohttp://accessories.dell.com and search for “PERC”.

 

Microsoft Windows Server 2012 provided RAID solution:

Installing Microsoft Windows Server 2012 utilizing the on-board SATA controller doesn’t provide data redundancy. In the event you want data redundancy, you can use the software raid functionality provided by the Microsoft Windows Server 2012 operating system.

  1. Go to disk management.
  2. Right click on the disks and convert it to dynamic disk.
  3. Right click on the volume for which you want redundancy and create “Mirrored Volume” or “RAID-5 volume”

Note: Redundancy can be provided for both data and operating system volume but the latter supports only “Mirrored Volume”. For more information about using operating system raid solution refer to Microsoft documents

 

 

Comments
  • When you say "at the present" do you mean never in the future or it's on your radar or pipeline for the near future?

  • OR.....

    Download the Drivers for OS Deployment package.

    Extract the contents to a folder using WinRar.

    Navigate to the "payload" folder.

    Extract the drivers.tgz file to another folder.

    Browse to the "\W3N37\default" folder and copy the contents to use for an "F6" install.

  • Dear All, I had found you can use Windows Server 2008R2 driver for S100/S300 to resolve this problem. The download link share to you, downloads.dell.com/.../DELL_MULTI-DEVICE_A05_R294488.exe

  • Geneticus, your solution is the only that worked for me! Thanks a lot!

    I've tried 5+ versions of this drivers in different packages, but the one extracted from deployment package did the trick.