Install Windows Perc H310 Raid
Perc h310 RAID controller in Dell Precision. Solved 0x7E for trying to install RAID drivers on Dell Precision 490; solved Windows 10 x64 driver for a Dell 00KT1V. Feb 19, 2014 Dell PowerEdge RAID Controller (PERC) Command Line. Configure, and manage your Dell PowerEdge RAID Controller (PERC) by using. To install the PERC.
I'm curently running Vista Ultimate x64. Windows 7 beta 1 (build 7000) offer no support for Dell Perc 4e/DC or LSI Megaraid 320-2e. The mraid35x.inf file is no longer included in Windows 7 beta 1 (build 7000). The mraid35x.sys driver was suporting a very wide range of SCSI RAid Adapters under Vista and, now, they are left in the backyard under Windows 7.
So why is that? Vista x86 and x64 supported very well these RAID Controler cards. Since I'm already using a Vista x64 set-up that boot from a Dell Perc 4e/DC, the upgrading path from Vista to Windows 7 (that is supposed to offer a greater hardware compatibility) will be impossible for me.
This is really a big deception. Hi, I have found the two following drivers that are accepted by Windows 7 x64 setup installation program: On the DELL web site: Dell PowerEdge RAID Controller EM64T Device Driver for Windows Server 2003 x64 Editions Version 6.46.3.64 The DELL driver have only support for the DELL perc 2,3 and 4 family of RAID controllers. ----------------------------------------------------------------------------------------------------------------------------------------------------- On the LSI web site: W2K3-64 SCSI MegaRAID Driver, Version 6.51.3.64 SCSI 320-2E&subType=Driver&locale=EN The LSI driver is more recent and seems to support more controllers from LSI, DELL and INTEL. ----------------------------------------------------------------------------------------------------------------------------------------------------- I have not tested any of these drivers yet, since the beta 1 is outdated now, I will wait for the RC at the end of april to do the test. It really seems that this is a Microsoft decision to dump the support for the PERC 4e/DC and a lots of others SCSI controllers.shame on them for having doing this. Thank you all for helping me in this quest! Hi, the Dell website, nor the LSI website, have any new driver available for the Dell PERC 4e/DC (aka Megaraid 320-2e).
Hi, I have found the two following drivers that are accepted by Windows 7 x64 setup installation program: On the DELL web site: Dell PowerEdge RAID Controller EM64T Device Driver for Windows Server 2003 x64 Editions Version 6.46.3.64 The DELL driver have only support for the DELL perc 2,3 and 4 family of RAID controllers. ----------------------------------------------------------------------------------------------------------------------------------------------------- On the LSI web site: W2K3-64 SCSI MegaRAID Driver, Version 6.51.3.64 SCSI 320-2E&subType=Driver&locale=EN The LSI driver is more recent and seems to support more controllers from LSI, DELL and INTEL. ----------------------------------------------------------------------------------------------------------------------------------------------------- I have not tested any of these drivers yet, since the beta 1 is outdated now, I will wait for the RC at the end of april to do the test. It really seems that this is a Microsoft decision to dump the support for the PERC 4e/DC and a lots of others SCSI controllers.shame on them for having doing this.
Thank you all for helping me in this quest!
Hello, I'm having trouble with Windows 2012 R2 installation on a setup with a range of SAS RAID controllers. In fact, none of them apart from simple on-board SATA (which doesn't present as a RAID to the OS) seem to work. The controllers I've tried are: • LSI SAS 1078 (onboard an IBM X3850) • Dell PERC H310 (both in the X3850, and an Asus X79-Extreme6 mobo) • Some RocketRaid evil. All of these cards show drives perfectly fine during Windows 2012 R1 setup, Windows 2008 R2, Windows 2008 R1 and even Windows Server 2003. I've tried the following: • Firmware updates of BIOS. • Firmware updates of RAID controllers.
• Loading latest drivers for Windows 2012/2008R2 x64 via 'Have Disk' during setup. • Adjusting all permutations of settings in RAID controller setup relevant to device modes, BIOS enable/disable etc. • Presenting disks as passthrough/JBOD • Presenting disks as RAID 0, RAID 1 and RAID 1+0 When I load the device drivers via 'Have Disk' it detects the device correctly (the drivers contain typically dozens of card drivers, but it always picks out the exact right device), but after it loads the driver the partition selector still shows no disks found, and I can't install Windows 2012 R2. I've also tried installing R1 and then doing an upgrade in place to R2. Motorola Gm340 Programming Software. What happens in this case is that I get the Windows start-up sequence to start, but it will pause after a few seconds and then fail with INACCESSIBLE_BOOT_DEVICE because once it hands over to the storage subsystem, it can't see the disk it was just loading from anymore. Inside a VM it'll run fine - but that isn't useful for running Hyper-V and testing other improvements. Anyone care to shed some light on: • What has changed in the storage subsystem that precludes the drivers working from Windows 2012 R1?
• What can I do to get this kit working again? We can't just go throwing out all of yesteryears kit in the test lab, and I'm resisting switching the environment over to ESX. Regards, -Steve Gray. Hello Steve, Tim is correct.
The vendor needs to provide 2012 R2 drivers for the devices in question. Having said that I am trying to see if there is anything more helpful I can find out for you. Warren Warren, Tim: The problem seems to be there *are* drivers shipped for this device in-box - but they don't work/recognise the disks. In Windows 2012 R1 this was correctly identified and installed without me even needing to find the drivers - but in 2012 R2 the Microsoft in-box drivers for the LSI megaraid card, leveraging the Megasas2 storport implementation, appear to not handle this device correctly. They've basically rewritten the driver for newer devices and left the PCI_VEN&1000_DEV00073 strings for the PERC 3x family in there. The original driver was seperate from the Megaraid driver (PERCSAS2). Having looked at the other servers onboard controller, it appears the LSI 1078 has a similiar situation - it used the LSI_SAS kernel driver, which was in-box with 2008 up to 2012 R2, but because of the device descriptors for it being part of the new Megaraid driver - it means that again, a driver that wont work is selected - despite in the LSI_SAS case, this driver still being present and operable in the OS. When I install the card as a non-primary storage device on another machine, it doesnt detect it properey and I have to then have to force-upgrade the drivers on the installation to use the most recent published driver - Windows complains at first because it's older than the current driver, but once I forcibly install it over the top and rebooot - the device comes online and is operable.
Trouble is, it's not possible to enforce this sequence of events during the WinPE/Setup phase. I've produced hacked up boot.wim and install.wim files that don't contain the Megaraid/Megaraid2 driver sets - mounting the registries offline, but suspect that I've missed some step - because despite DISM-merging in the old PERCSAS2 driver copied directly from a working machine where I was able to boot 2012 R2 on a different controller - the controller isnt identified and no disks can be found. I've also tried booting this server via presented fibre-channel storage on a QLE2462 dual-port HBA. I'm able to see the LUN's in Windows 2012 R1, but in 2012 R2 I cannot find the storage. Not diagnosed this one. Sometimes being on the bleeding edge of adoption hurts ^_^. Hi Steven, i hope this doesn't sound presumptuous, but have you tried to re-download the ISO / checked the MD5-hash?
In the past, i had similar problems during installation. Corrupted downloads still happen.
The hash checked out on the original media, but naturally my hacked up version doesnt match - neither one worked - but both disks are capable of installing machines that use simpler configurations (i.e. Not booting from RAID).
Tonight i've set up two machines both booting from fibre channel. One is an ASUS X79-Extreme6 motherboard, the other is a HP Compaq 8000 Elite - both of them are able to install and run from fibre channel on 2012 R1, but neither a direct installation to FC from Windows 2012 R2 (simply cant find the disks/DISKPART RESCAN shows nothing) or an upgrade (from the earlier 2012 R1 installs) works. The upgrade gives the hauntingly familiar inaccessible boot device bsod (STOP 0x7B). Again, this is with all released BIOS updates and a fully flashed QLE2462 - Really a shame, since I've got six of them and they've worked with every other version of Windows, even down to 2003 - and they're NPIV capable for Hyper-V! Warren, Tim: The problem seems to be there *are* drivers shipped for this device in-box - but they don't work/recognise the disks. In Windows 2012 R1 this was correctly identified and installed without me even needing to find the drivers - but in 2012 R2 the Microsoft in-box drivers for the LSI megaraid card, leveraging the Megasas2 storport implementation, appear to not handle this device correctly. They've basically rewritten the driver for newer devices and left the PCI_VEN&1000_DEV00073 strings for the PERC 3x family in there.
The original driver was seperate from the Megaraid driver (PERCSAS2). Yes, LSI may submit its drivers to be shipped in box, but they are still written by LSI, not by Microsoft. Again, you are dealing with a new version of the operating system and things are changing. Vendors are writing new drivers. This is really something only LSI can answer for you.
Anybody else would be guessing..: .: . Yes, LSI may submit its drivers to be shipped in box, but they are still written by LSI, not by Microsoft.
Again, you are dealing with a new version of the operating system and things are changing. Vendors are writing new drivers. This is really something only LSI can answer for you. Anybody else would be guessing..: .: . Tim It doesn't explain why I can get the devices to work perfectly with the 2012 R1 drivers on rebooting after I install to alternate disks (in fact, having played a bit more, I'm becoming confident even the in-box drivers could be made to work post-install - but not during WinPE/Setup) - giving them an extra reboot to come back online wasn't something I tried, since I was more focused on trying to use them as the primary storage/installation medium. It's easy to say 'Driver needs updating' - but it doesn't explain why? What's changed?
Something is causing my devices to need an extra reboot before they're workable inside Windows. In the meantime I've given up and gone back to 2012 R1 - since RAID and Fibre Channel are extensive in my environment.