I updated to Windows 10 Pro with a clean install and had issues with my RAID array showing up as raw format. I was able to take a backup of it from my W7 drive then rebooted into W10 deleted the array in Disk Management, deleted the array in the controller BIOS and then recreated it in the BIOS. Now I'm trying to recreate the array in W10 Disk Management and the option to create a RAID 5 array is greyed out so I made a stripped volume and its giving me the available space of all 3 disks not 2 - 1 for parity as I would expect.
I installed the drivers stickyed at the top of these boards before attempting to recreate the array and the controller shows up in device manager. I haven't started restoring the backup yet while I figure out if its seeing the array properly and if not what I can do to get working properly.
Anyone else having this issue?
EDIT: Updated system specs in signature
Poked around in the AMD RAIDXpert utility (didn't have to use it with W7) and it will let me make a RAID 0, 1, or just a bunch of disks array but not RAID 5 or 10. Mobo is an Asus M4A79T Deluxe that has an AMD SB750 RAID controller that supports RAID 0,1, 5, and 10. If nothing else I could go with a RAID 1 array with a hot spare and have fault tolerance but I'd prefer to get RAID 5 working for both the performance and fault tolerance.
Found How To Set Up a RAID 5 Array in Windows 8 and Linux - Maximum PC and it seams like this might be the same as doing a RAID 5 array according to Storage Spaces: FAQ - Windows Help. I know I never had to use it in W7 to create the array I just defined it in the controller and then in disk management it showed up as a single unallocated drive with ~1.8TB of space. Now when I define the array in the controller I still see the 3 separate disks one 1 unallocated, 1 uninitialized, and 1 offline in disk management.
EDIT: looks like storage spaces is a software RAID utility and since the mobo supports RAID 5 via hardware it would be better to figure out why its not allowing me to create the RAID 5 array.
Resolved this issue by downloading the W7 driver AHCI from Asus and manually installed it. It looks like it used the vista driver version 3.100.1540.86 from looking at the .ini files in the zip file but after deleting the array in the controller and recreating it came up as a single uninitialized unallocated drive of ~1.8GB in disk management. Initialized and formatted the array and everything looks to be good to go at this point, only thing left is to restore the backup to it.
Thanks a lot KLS! I had similar problems after upgrading from Windows 7 to Windows 10. I'm using an Asus M4A79XTD EVO motherboard with a RAID-5 configuration (AMD SB750 controller). After upgrading, Windows 10 did not recognized the RAID config anymore.
You're solution looks fine. Because I was already using that driver in Windows 7, I could simply return to the previous RAID controller driver within the device manager. Rebooted and my RAID volume was there again!
So it looks like a serious bug in the AMD RAID driver that Windows 10 is using!
Well, did you try breaking the raid5 and rebuilding it? Because I had serious problems with it under Windows 10 and had to install Windows 7 on a spare disk to be able to rebuild the array where Windows 10 was installed.Thanks a lot KLS! I had similar problems after upgrading from Windows 7 to Windows 10. I'm using an Asus M4A79XTD EVO motherboard with a RAID-5 configuration (AMD SB750 controller). After upgrading, Windows 10 did not recognized the RAID config anymore.
You're solution looks fine. Because I was already using that driver in Windows 7, I could simply return to the previous RAID controller driver within the device manager. Rebooted and my RAID volume was there again!
So it looks like a serious bug in the AMD RAID driver that Windows 10 is using!
More info at -> RAID5 can't rebuild on Windows 10 | Community
Thanks!
