Lsi Megaraid Driver Windows Server 2016
Bernd Manison
I rock some HP workstations at work with LSI cards, 9217-4i4e being one of them. Far from best practice, but if you need to kick this thing out the door ASAP, could you unplug one of the drives in the pair and see if Windows lets you install to the remaining drive? If that works, then plug the other drive in and let it rebuild.
Did you extract the correct driver? Normally there are two, one you install under windows and the other, commonly called the F6 driver that you need to use during the OS install. (F6 was the keystroke you used in earlier windows versions to tell setup that you wanted to provide a driver.)
this is an elitedesk 800 from HP. I just bought a bunch of these for a training lab here at work and another for this staff member. And as mentioned above this was using efi. sorry my knowledge is limited on this, why does efi potentially cause issues over legacy booting?
I am attempted a bare metal install of Windows Server 2016 onto a UCS S3260 storage server. I've already updated to the latest firmware. I have created virtual disk volumes on the installed physical disks. When I attach the Microsoft Windows server ISO and boot, the Microsoft Windows SETUP begins and does not contain an out-of-box driver for either of the RAID controllers. So Windows SETUP cannot detect a target volume onto which to install. I understand that at this point I need to mount a different ISO containing downloaded drivers from Cisco and ask Windows SETUP to scan for matching device drivers. I've downloaded sets of UCS driver ISOs from Cisco 3.1(3b) and 4.0(4d) which look like the should contain a matching driver, but Windows SETUP does not find a match and cannot continue. Screenshots attached below.
A tip for those trying to install on S3260 M5 is there are two RAID controllers on the M5, you must first disable one of the controllers so that the OS boot volume is selected as controller 0 and drive 0. The OS must be installed on 0:0, this is a limitation of a bare metal install of Windows.
All-in-all very dissatisified with the S3260 M4 and M5 systems. I have had to open numerous TAC cases just to do simple installs and upgrades. Hardware problems upon delivery, firmware bugs, missing drivers. This product has been released for a couple of generations/revisios, it is still is not right.
The suggestion that the Microsoft server ISO is corrupt, seems highly unlikely since we've used this same ISO for many other installs (just not bare metal S3260). I could try a new download and go with Server 2019 instead perhaps.
The drivers I need are for both the internal controllers - the LSI controller for the SATA drives (boot SSDs dedicated to the server) and the UCSC-C3X60-RAID (aka MegaRAID) controller for the 56 slot disk array containing the data drives.
Thanks for the links to support/downloads. The link takes me to the download I've already taken, which is the 4.0(4d) ISO. And it confirms what I suspected, that Windows Server 2016 is supported. Now if TAC will just support me on this journey! I will telephone them and escalate. TAC seem too busy to respond to my open case via the website/email at the moment... 11 days and counting and still no bootable OS on this hardware! Numerous bumps in the road. Not impressed with S3260 so far.
Sorry, I can't recall the exact steps. I even looked at the closed Cisco TAC case, looking for notes that the engineer or I might have made in the case, but there is nothing there with the precise details. (We had many issues to cover and so probably overlooked this step).
In the CIMC, you must navigate to the Chassis Inventory, then to Zoning. You will need to re-zone all drives so that all drives are on the Controller1 RAID controller. (My mistake; you are not taking the controller2 offline; you are just moving all drives to controller1). Including any existing data volumes you need to preserve AND the local SATA boot drives. Once ALL volumes are on Controller1 you can move the SATA drive up to volume 0. Alternatively, you can re-zone by removing the PD from all controllers exceptleaving only the SATA volume on controller1. Install Windows, then re-zone again to place the volumes back onto the server, balancing the data volumes across controller1 and controller2.
I would open a TAC case with Cisco and have them verify these steps. And because you will be re-zoning, you must have a good backup of any data and make sure that Cisco agrees it can be done this way.
Sorry you are having a nightmare. I have had nightmares every time I touch the S3260. It seems like a lot of trial-and-error, rinse-and-repeat to get a Windows OS installed. Maybe VMware ESXi installs cleanly, I haven't a use-case for that OS on this hardware, however.
I've been looking for drivers, but all I can seem to find are packages with a massive list of possibilities as to which kind of controller I have. Device manager shows it's an Intel device with an ID of 1D69. I would normally check the PCI Database, but it seems their database is borked at the moment.
Given what I'm seeing on the motherboard I don't think there's a hardware raid on here, unless there's an integrated chip that I don't see. The drivers page for my board series seems to suggest this -Hardware-RAID-Driver-for-Windows-x86-x64-version-?product=61089 SAS Hardware RAID Driver for Windows* (x86 & x64 version) but I think this is more likely: -Embedded-Server-RAID-Technology-2-ESRT2-RAID-driver-for-Windows-?product=61089 Download Intel Embedded Server RAID Technology 2 (ESRT2) RAID driver for Windows* . In the BIOS there is mention of using ESRT2 or RSTe. I'm familiar with RSTe as the software (or hybrid) raid that's popular on most consumer motherboards but I'd never encountered ESRT2 before.
I've been looking through that manual since I got the board, but can only find very basic information regarding the two RAID options on the motherboard, which seems to be limited to which RAID modes are supported by which solution. The best I can find is that this is based on LSI Megaraid software. I've been unable to find drivers for this, but I am also curious if I should even be seeing that with RSTe selected instead.
I am running Windows Server 2012 R2, so worst case scenario if I can't figure out how to set up a RAID using the motherboard (the prompt for accessing RSTe via ctrl+i isn't showing up either) I could always do a software RAID5 from Windows disk management. I could also install UnRaid and set up parity and Server 2012 R2 as a guest as well.
Super, that's the one I needed. Thank you for finding that for me. So there's no interface during boot to create a volume, but rather I can use the CLI or this GUI to do it? I guess that makes sense given rebooting a server would be troublesome just to configure RAID.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
The following table identifies the SAS PCIe host bus adapter (HBA) options thatare supported on the server at the time of this publication. If youhave one of these SAS PCIe HBA options configured on your server andyou are installing Microsoft Windows Server 2008 SP2, you will need to loadthe LSI mass storage driver for the PCIe HBA option. This LSI massstorage driver is available on the internal Oracle System Assistant USB flash driveand Oracle System Assistant provides tools for loading it.
Instructions for loading the LSI mass storage driver during the Windows Server 2008SP2 installation are provided in Step 8 of the Install Windows Server 2008 (SP2 or R2 SP1) Using Local or Remote Media.
If your server does not have an internal Oracle System Assistant USB flashdrive, you can download the ISO image that includes the LSI mass storagedriver. For download instructions, see Getting Server Firmware and Software.
All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof.
Many commands are also described in their manual pages. To view them, run man, followed by a specific command name. If the man command is not installed on your system, install it with sudo zypper install man.
To simplify this process, click the Report an issue icon next to a headline in the HTML version of this document. This preselects the right product and category in Bugzilla and adds a link to the current section. You can start typing your bug report right away.
To contribute to this documentation, click the Edit source document icon next to a headline in the HTML version of this document. This will take you to the source code on GitHub, where you can open a pull request.
You can also report errors and send feedback concerning the documentation to . Include the document title, the product version, and the publication date of the document. Additionally, include the relevant section number and title (or provide the URL) and provide a concise description of the problem.
Commands can be split into two or multiple lines by a backslash character (\) at the end of a line. The backslash informs the shell that the command invocation will continue after the end of the line:
d3342ee215