This computer is less than a year old.
Gigabyte z170x gaming 7 motherboard.
4 4TB hard drives in a raid 10.
2 512gb ssd drives in raid 0.
upgraded bios from F7g to F20 and all of a sudden this happens.
The raid has failed missing 2 of the 4 drives out of the raid10. It shows 2 of the missing drives as non-raid members with green checks.
I know for a fact these drives work flawlessly. Is there some kind of tool we can use to correct this obvious error inside the rst?
It gives me the ability to mark the 2 “non-raid” disks as a spare, but I haven’t clicked on that as I feel it would do irreversible damage to an otherwise good disk.
@elementalwindx :
Welcome at Win-RAID Forum!
What sort of support do you expect? We cannot repair your degraded RAID 10 array.
You can try to repair the RAID array by using the Intel RST Console, which is part of the Intel RST Software.
The best way to avoid any degraded RAID array is to work without any RAID array (not meant seriously…).
Regards
Dieter (alias Fernando)
Being that I have 0 experience with the console and just found out about it through you, could you tell me more? 
I’m a PC tech for a living, I build computers, sell them, manage them, but I’ve never had this happen in 15 years of doing this. All your help is greatly appreciated.
I found a guide like this but it sounds sketchy: http://www.overclock.net/t/478557/howto-…mber-disk-error
If you should not have already installed the Intel RST Software, I recommend to do the following:
- Check the version of the currently running Intel RAID driver. You can find it by running the Device Manager, expanding the section "Storage Controllers", doing a right-click onto the listed Intel SATA RAID Controller and using the options "Properties" > "Driver".
- Search for the Intel RST Drivers & Software Set, which matches the version of your currently running Intel RAID driver. You may find it within the start post of >this< thread.
- Make sure, that the Microsoft .NET Framework 3.5 is installed (is required for the Intel RST Software).
- Install the Intel RST Set by running the EXE file and reboot thereafter.
- Run the software named "Intel Rapid Storage Technology".
- Hit the tab "Status" and look, what the RST Software tells about it.
- If the Intel RST Software offers to repair the related broken RAID array, let it do it.
Try it, if you should not succeed with the Intel RST Software.
Also here is a system report. I’ll bet it has something to do with the disk appending a :0 to the end of it. 
SystemReport.txt (5.2 KB)
ahh we posted at the same time
1) 15.2.0.1020. I was 15.2.something but I upgraded to the newest hoping it may fix it.
3) .net 3.5 and newest are installed.
EDIT by Fernando: Unneeded fully quoted post removed (to save space)
I can neither open nor read the attached system report.
Please attach it as *.zip or *.rar archive.
Sorry for being scattered. I just went to your page and installed the newest version of the raid driver and of the RST. 15.2.10.1044 64bit. I tried the rest of your instructions and rebooted, and haven’t gotten any repair options yet
Also here is the system report:
System Report
System Information
Status: Microsoft Windows 10 Pro
OS version: 10.0.14393
System name: SETH-PC
System manufacturer: Gigabyte Technology Co., Ltd.
System model: Z170X-Gaming 7
Processor: GenuineIntel Intel64 Family 6 Model 94 Stepping 3 4.001 GHz
BIOS: American Megatrends Inc., F20
Intel® Rapid Storage Technology enterprise Information
Kit installed: 15.2.10.1044
User interface version: 15.2.10.1044
Language: English (United States)
RAID option ROM version: 15.2.0.2754
Driver version: 15.2.10.1044
ISDI version: 15.2.10.1044
Storage System Information
RAID Configuration
Array Name: SATA_Array_0000
Size: 15,261,790 MB
Available space: 7 MB
Number of volumes: 1
Volume member: DATA
Number of array disks: 4
Array disk: Z30522S4
Array disk: Z305222R
Array disk: Z30522YT:0
Array disk: Z3051ZS8:0
Disk data cache: Enabled
Array Name: SATA_Array_0001
Size: 976,772 MB
Available space: 3 MB
Number of volumes: 1
Volume member: OS
Number of array disks: 2
Array disk: S250NXAGA09719B
Array disk: S250NXAGA08197Z
Disk data cache: Enabled
Volume name: DATA
Status: Failed
Type: RAID 10
Size: 7,630,891 MB
System volume: No
Data stripe size: 64 KB
Write-back cache: Off
Initialized: Yes
Parity errors: 0
Blocks with media errors: 0
Physical sector size: 4096 Bytes
Logical sector size: 512 Bytes
Volume name: OS
Status: Normal
Type: RAID 0
Size: 976,768 MB
System volume: Yes
Data stripe size: 8 KB
Write-back cache: Read only
Parity errors: 0
Blocks with media errors: 0
Physical sector size: 512 Bytes
Logical sector size: 512 Bytes
Hardware Information
Controller name: Intel Chipset SATA RAID Controller
Type: SATA
Mode: RAID
Number of SATA ports: 6
Number of volumes: 2
Volume: DATA
Volume: OS
Number of spares: 0
Number of available disks: 2
Rebuild on Hot Plug: Disabled
Manufacturer: 32902
Model number: 10274
Product revision: 49
Direct attached disk: Z30522YT
Direct attached disk: Z30522S4
Direct attached disk: S250NXAGA09719B
Direct attached disk: S250NXAGA08197Z
Direct attached disk: Z305222R
Direct attached disk: Z3051ZS8
Direct attached disk: Z30522YT:0
Direct attached disk: Z3051ZS8:0
Disk on Controller 0, Port 0
Status: Normal
Type: SATA disk
Location type: Internal
Usage: Available
Size: 3,726 GB
System disk: No
Disk data cache: Enabled
Command queuing: NCQ
Transfer rate: 6 Gb/s
Model: ST4000DX001-1CE168
Serial number: Z30522YT
SCSI device ID: 0
Firmware: CC45
Physical sector size: 4096 Bytes
Logical sector size: 512 Bytes
Disk on Controller 0, Port 1
Status: Normal
Type: SATA disk
Location type: Internal
Usage: Array disk
Size: 3,726 GB
System disk: No
Disk data cache: Enabled
Command queuing: NCQ
Transfer rate: 6 Gb/s
Model: ST4000DX001-1CE168
Serial number: Z30522S4
SCSI device ID: 0
Firmware: CC45
Physical sector size: 4096 Bytes
Logical sector size: 512 Bytes
Disk on Controller 0, Port 2
Status: Normal
Type: SATA SSD
Location type: Internal
Usage: Array disk
Size: 477 GB
System disk: No
Disk data cache: Enabled
Command queuing: NCQ
Transfer rate: 6 Gb/s
Model: Samsung SSD 850 PRO 512GB
Serial number: S250NXAGA09719B
SCSI device ID: 0
Firmware: EXM02B6Q
Physical sector size: 512 Bytes
Logical sector size: 512 Bytes
Disk on Controller 0, Port 3
Status: Normal
Type: SATA SSD
Location type: Internal
Usage: Array disk
Size: 477 GB
System disk: No
Disk data cache: Enabled
Command queuing: NCQ
Transfer rate: 6 Gb/s
Model: Samsung SSD 850 PRO 512GB
Serial number: S250NXAGA08197Z
SCSI device ID: 0
Firmware: EXM02B6Q
Physical sector size: 512 Bytes
Logical sector size: 512 Bytes
Disk on Controller 0, Port 4
Status: Normal
Type: SATA disk
Location type: Internal
Usage: Array disk
Size: 3,726 GB
System disk: No
Disk data cache: Enabled
Command queuing: NCQ
Transfer rate: 6 Gb/s
Model: ST4000DX001-1CE168
Serial number: Z305222R
SCSI device ID: 0
Firmware: CC45
Physical sector size: 4096 Bytes
Logical sector size: 512 Bytes
Disk on Controller 0, Port 5
Status: Normal
Type: SATA disk
Location type: Internal
Usage: Available
Size: 3,726 GB
System disk: No
Disk data cache: Enabled
Command queuing: NCQ
Transfer rate: 6 Gb/s
Model: ST4000DX001-1CE168
Serial number: Z3051ZS8
SCSI device ID: 0
Firmware: CC45
Physical sector size: 4096 Bytes
Logical sector size: 512 Bytes
Disk on Controller Unknown, Port Unknown
Status: Missing
Type: Unknown disk
Location type: Unknown
Usage: Array disk
Size: 0 GB
System disk: No
Model:
Serial number: Z30522YT:0
SCSI device ID: 255
Firmware:
Physical sector size: 0 Bytes
Logical sector size: 0 Bytes
Disk on Controller Unknown, Port Unknown
Status: Missing
Type: Unknown disk
Location type: Unknown
Usage: Array disk
Size: 0 GB
System disk: No
Model:
Serial number: Z3051ZS8:0
SCSI device ID: 255
Firmware:
Physical sector size: 0 Bytes
Logical sector size: 0 Bytes
EDIT by Fernando: Put the system report into a “spoiler” (to save space)
Which sort of "Status" informations do you get from the RST Console?
I don’t know how to access the console? (Maybe I’m using console as the wrong term. I think of console like xterm, or cmd) This is what the status page looks like:
@elementalwindx :
Your attached picture shows the Intel RST Console Software and - as you can read within the "Status" section - 2 members of your RAID10 resp. their SATA ports are missing.
If you click onto the "Manage" tab, you may be able to repair it.
Another thought: The degradation of the RAID10 array obviously happened after having flashed a new BIOS. So I recommend to enter the BIOS and check, whether you have restored all your previous settings (incl. by enabling the related SATA ports).
When I go to manage, it just allows me to mark the non-member disks as spares.
I’ve double checked my bios settings. I didn’t do anything special with them other than turn on raid, and configure the raid with ctrl + i. I made sure the storage boot was set to legacy as well.
Have you tried to do it?
After each BIOS flashing procedure you have to restore the previous BIOS settings.
What about the SATA ports, where the degraded RAID10 members were connected? Are they still enabled? Does the BIOS see and show all Disk Drives, which are resp. have been members of the RAID10 array?
In the bios, yes, they are the ones showing up as non-member disks.
I have not tried to mark it as spare.
I don’t believe, that the BIOS itself shows them as non-member disk drives. What you certainly mean is the Intel RAID Utility, which s a BIOS tool and not the BIOS itself.
By the way: Which version has the Intel RAID Utility (accessable via CTRL+I)?
I ended up removing the 2 disks to non-member, and recreating the raid array (disks physically never moved), and tried to use testdisk to get the partition back with no luck. Still shows up not initialized but couldn’t get the partition back 
Any idea on software to use to rescue me?
The best way to recover a previously existing RAID partition and its data is to do each week or month a complete backup of the related partition (can be done from within Windows or by using any Backup Tool.
Another idea: Did you already check the SATA cables of the degraded RAID10 array members?
Yea sata cables are fine.