Download Amd Sata Controller Driver Windows 7
Scat Laboy
Having read through previous related threads on this forum, I confirmed that the drives are SATA/RAID-able (HPE Model MB001000GWFWK, 1TB 7200 SATA) and that Boot Mode is set to UEFI. However, when I checked the BIOS/Platform Configuration (RBSU) -> Storage Options -> SATA Controller Options -> Embedded SATA Configuration, there is no 'SW RAID Support' (or similar) option available. The two options I'm seeing are 'SATA AHCI Support' (factory default setting) and 'Intel VROC SATA Support'. I've tried both options, but neither enables Smart Storage Administrator for RAID configuration (no controllers detected with either option).
I did locate the latest version of HPE Smart Array Gen10 and Gen10Plus Controller Driver for Windows Server 2016, Windows Server 2019 and Windows Server 2022 (8 April 2022) on HPE Support site and dowloaded it. However, it's not clear to me how to install this controller driver on the new servers prior to having loaded a Windows OS and associated file system. Thus, at present, I'm stuck.
The Intel VROC SATA SW RAID included with your server is disabled by default. The VROC can be enabled in BIOS/Platform (RBSU) for SW RAID.. You will need to download the Intel VROC drivers and GUI specific to your OS. The Intel VROC cannot be configured with SSA. For direct download links, see the OS-specific VROC guide: -Gen10Plus-docs
I had (via hunting around in the BIOS menus after having set the BIOS/Platform Configuration (RBSU) -> Storage Options -> SATA Controller Options -> Embedded SATA Configuration option to 'Intel VROC SATA Support') discovered how to create a VROC RAID array. What I hadn't yet discovered was the driver needed for the Windows OS install wizard to discover the VROC array so that the OS had a logical drive/volume on which to run. All of that is covered in the document found at the link you provided: =en_US&docId=a00112943en_us
In general, it seems that the Smart Storage Administrator SW RAID is more seamlessly integrated into the system than is the VROC SW RAID (or, at least for a Windows server install). Thus, I'm a bit curious as to why VROC is used on the DL20 Gen10 Plus servers (rather than the Smart Storage Administrator SW RAID as is used in the DL20 Gen10/9/8). Anyone have insight into that?
I would just boot into the installer and see if there is a repair button. Given those choices I would choose the first and change settings back when you get back into Windows. Another thing you could try is different SATA ports on your motherboard. These things can turn out to be really frustrating to find a fix for so don't lose hope. There has to be some way of getting them working if nothing else was done but a CPU swap.
Well trying to boot and clicking on "Repair this computer" tells me to choose a recovery disk. There I have the only option to choose the USB that I booted this installer. When I do this goes in a loop and boots the installer again with the same options to Install Windows or Repair with no luck. Maybe I will try the .iso...
Afterwards you can revert it back to your original Windows if it doesn't work out. I believe the Windows.old will be deleted automatically in 10 days but you can use Disk Cleanup to get rid of it for you earlier.
In Device Manager .. under View . .check "Show Hidden Devices" and then go through each drop down menu and remove/uninstall every greyed out entry , unknown device and "other devices" (you'll see 12 entries from your old 2600 under processors for example for removal) .. IF Windows was actually using any of those entries, they will be re-installed upon rebooting
I was incorrect. Can not recall having to install those myself, but had an image in my head of SATA-drivers being listed on motherboards driver page, which is true for Asus, but contains just Raid app and driver.
AMD used to have a SATA CONTROLLER to download load but since Windows 10 came out they have replaced the AMD SATA CONTROLLER with MS STANDARD SATA CONTROLLER AHCI instead which is upgraded with each Windows upgrade.
This tech site gives you the same explanation as I did about using Device Manager to install your SATA Controller AHCI: -center/how-to-download-standard-sata-ahci-controller-driver-on-windows...
On device manager both Standard SATA AHCI Controller and AMD Virtualized AHCI Controller for StoreMI are greyed out because they can't detect that the drives are connected due to Serial ATA Controller.
I'm guessing this driver was installed along with StoreMI when I first built my PC 3 years ago and assuming its only use is for StoreMI which I never used and is uninstalled from the beginning. Would there be a problem uninstalling it? @ThreeDee what do you think?
Well another strange thing in all of this is that it's not certain this will happen when you upgrade CPU. A friend of mine upgraded from 2400G to 5600 on a B350 mobo with Win 10 Pro installed on an m.2 nvme alongside with 3 sata drives. 1 SSD and 2 HDDs and he didn't have this problem. And we don't know why.
I upgraded when it first became available. Didn't notice a lot of differences. I tend to like Winn 11 better than Win 10. Haven't had any problems on the 3 computers (2 desktops, 1 laptop) I upgraded.
As I commented, none have had any unexpected issues. With the exception of the Gen 2 2700X incompatibility that is stated in manuals and release notes if you read them completely. That and the RX 480 are just getting old, like me.
I have a Win7 installation on a box where the on-board SATA controller died, so I've added a dedicated controller card, and now need to fix the Windows boot sequence that the driver is loaded with the first batch.
Hi It is possible if you have the unpacked Windows 7 driver files of the current storage controller. What you need to do is to boot from the "Windows 7" setup DVD, System repair CD or from a "WinPE 3.0" and use the DISM command to inject the storage controller driver . You will find more info in the below links.
christian.hofstaedtler.name/blog/2013/01/using-dism-to-add-drivers.html forums.overclockersclub.com/?showtopic=192550
which is exactly what I needed. I used the installation DVD to load into Windows Recovery then loaded the PCIe SATA driver that was missing from a USB. Once it loaded, I was able to attempt recovery which either failed or succeeded but then I opened up command prompt from the options that were available and ran the dism command to install the driver from the USB drive onto the hard drive.
This evening, I was bemused to find a Linux live disk unable to identify the storage volume on my new Dell XPS 13 laptop. A quick search introduced me to a problem I have not encountered before; the SSD was likely configured to use a SATA controller mode that did not have a driver in the kernel of the live disk installer. This is typically when the stock disk has been shipped in either IDE (for backwards compatibility purposes) or a vendor specific RAID mode, instead of the native Advanced Host Controller Interface (AHCI) that exposes some of SATAs more advanced features.
One can easily change this setting in the BIOS. On my XPS I had to navigate to System Configuration > SATA Configuration and switch the radio button selection from RAID On to AHCI. A rather scary warning informed me that this would more than likely break my existing partitions. As a curious scientist with a recovery partition as a safety net, I decided to proceed anyway. Unsurprisingly, Windows 10 failed to boot, electing to display the dreaded sideways smiley face and a suggestion that I read up about the INACCESSIBLE_BOOT_DEVICE error. Oops.
It turns out, to optimize boot times, Windows disables drivers that are deemed unnecessary for startup during installation. Herein lies the problem, if the OS is installed while the disk is in one of these other modes (in my case RAID), the driver that would allow us to speak AHCI to our speaking AHCI-speaking SATA storage controller is effectively disabled (even though it is installed). Windows, without the ability to communicate with the disk correctly, has no real option but to fall on its side with a glum expression and throw the INACCESSIBLE_BOOT_DEVICE error during startup. The accusations are corroborated by the Wikipedia article on the subject of AHCI:
Some operating systems, notably Windows Vista, Windows 7, Windows 8 and Windows 10 do not configure themselves to load the AHCI driver upon boot if the SATA-drive controller was not in AHCI mode at the time of installation. This can cause failure to boot, with an error message, if the SATA controller is later switched to AHCI mode.
Hello all. I am setting up Windows 98 on a computer that is slightly newer than that era. The motherboard has an IDE input but also has SATA. The bios lets me set the SATA as IDE compatibility and I have a DVD drive plugged into that. (I have hard drive on the actual IDE) once windows is running it sees the SATA as IDE but says it doesn't have a driver for it and doesn't see the DVD Drive. I was wondering if anyone had any ideas of how I should go about trying to get the drive working. Thanks for any help.
gigabyte ga-ep45-ud3l is the motherboard I'm using. It doesn't have win98 drivers but I figured I'd put in a compatible graphics card, sound card, and it should be able to work otherwise. I'm not sure what other hard drive would matter but got half gig of ram, an old generic VGA video card, and pentium 4 processor in
I don't have answers but I'm curious whether an atapi CD driver and mscdex work in DOS mode? I thought the whole point of IDE compatbility mode was to be, well, IDE compatible. So you'd think it would at least work slowly under Windows. Maybe windows has a whitelist of pci ids or something and it needs to see an .inf file before it'll accept that it's an IDE controller?
7fc3f7cf58