Gigabyte support has been worse than useless with this issue, so maybe one or more of you have seen it. Because I can honestly say I haven't.
Here's the setup.
Marvell (G-SATA): Disable
Intel C606 SATA: Enable, RAID
Intel C606 SAS: Enable, non-RAID
Disk Layout:
Now, this is well, well within the C606's and X79S-UP5-WIFI's capabilities to run even factoring in the OROM issues. G-SATA and PXE to disable and life is good.
Windows Setup absolutely cannot find the disk controllers or the disks with RAID enabled. ANY of the disks. Not the RAID set, not the SAS attached SSDs, nothing. Immediately I suspected it was an F6 driver issue, grabbed my USB drive full of F6 drivers, went down the whole list. 12.8.6.1016 is loading as signed and OK, but not finding the disks. Any of them. Not a single one. (Windows 7 Ultimate SP1, x64.)
Suspecting an RSTe issue I've run into before with STECs, I broke out my trusty instrumented FreeBSD boot stick and cranked things up.
Cue lack of surprise as FreeBSD finds not only the controllers just fine, but all of the disks and GEOM properly identifies and confirms the array as being in the UNINITIALIZED state. It is not any of the RSTe issues. I also confirmed that I'm able to write to and read from all the disks in other OSes.
Fine, maybe it's a stupid BIOS issue. Well, one, F4 bricked a second board. GREAT JOB THERE, GIGABYTE. No reports my &*$#@. Second, every single BIOS is exhibiting identical behavior from F3 through F4 and F5a. And as if that's not weird enough? If I set the SATA to AHCI mode, it detects all the SATA disks just fine but none of the SAS disks. Try it with the Shrike F4v's installation ISO (which is setup for SAS w/RAID5 enabled) and it has the same results - cannot see anything on SAS, cannot see anything on RSTe RAID, sees only SATA.
Even if I was only getting a partial (SATA present, SAS missing or vice versa) I'd obviously being some disks rather than no disks. Or I wouldn't see the disks when it's in AHCI mode. But that is not the case.
And obviously if it was a controller fault, I wouldn't see any of the disks or I'd see partial results in other OSes. Nope - the disks and controllers are just fine. If it was a screwup on my part in the F6 integration, I'd see the same symptoms on a working system. Also negative results there - disks show fine. DriverQuery confirms that the F6 drivers for everything are loaded - Chipset, Controller, Network, all check out green. I have played with the BIOS and settings FAR more than any sane man should, with no progress or success. Behavior absolutely does not change.
I am at wit's end on this one. It has got to be something in Windows setup obviously, but what the hell is it?
Here's the setup.
Marvell (G-SATA): Disable
Intel C606 SATA: Enable, RAID
Intel C606 SAS: Enable, non-RAID
Disk Layout:
Code:
Intel C606 SATA: SATA3.0: HGST 1TB 7200 (Array01) SATA3.1: HGST 1TB 7200 (Array01) SATA2.0: HGST 1TB 7200 (Array01) SATA2.1: HGST 1TB 7200 (Array01) SATA2.2: HGST 1TB 7200 (Array01) SATA2.3: No Device Intel C606 SAS: SAS0: Crucial M500 SSD SAS1: Crucial M500 SSD SAS2: STEC SSD SAS3: STEC SSD SAS4 through SAS7: No Device
Windows Setup absolutely cannot find the disk controllers or the disks with RAID enabled. ANY of the disks. Not the RAID set, not the SAS attached SSDs, nothing. Immediately I suspected it was an F6 driver issue, grabbed my USB drive full of F6 drivers, went down the whole list. 12.8.6.1016 is loading as signed and OK, but not finding the disks. Any of them. Not a single one. (Windows 7 Ultimate SP1, x64.)
Suspecting an RSTe issue I've run into before with STECs, I broke out my trusty instrumented FreeBSD boot stick and cranked things up.
Cue lack of surprise as FreeBSD finds not only the controllers just fine, but all of the disks and GEOM properly identifies and confirms the array as being in the UNINITIALIZED state. It is not any of the RSTe issues. I also confirmed that I'm able to write to and read from all the disks in other OSes.
Fine, maybe it's a stupid BIOS issue. Well, one, F4 bricked a second board. GREAT JOB THERE, GIGABYTE. No reports my &*$#@. Second, every single BIOS is exhibiting identical behavior from F3 through F4 and F5a. And as if that's not weird enough? If I set the SATA to AHCI mode, it detects all the SATA disks just fine but none of the SAS disks. Try it with the Shrike F4v's installation ISO (which is setup for SAS w/RAID5 enabled) and it has the same results - cannot see anything on SAS, cannot see anything on RSTe RAID, sees only SATA.
Even if I was only getting a partial (SATA present, SAS missing or vice versa) I'd obviously being some disks rather than no disks. Or I wouldn't see the disks when it's in AHCI mode. But that is not the case.
And obviously if it was a controller fault, I wouldn't see any of the disks or I'd see partial results in other OSes. Nope - the disks and controllers are just fine. If it was a screwup on my part in the F6 integration, I'd see the same symptoms on a working system. Also negative results there - disks show fine. DriverQuery confirms that the F6 drivers for everything are loaded - Chipset, Controller, Network, all check out green. I have played with the BIOS and settings FAR more than any sane man should, with no progress or success. Behavior absolutely does not change.
I am at wit's end on this one. It has got to be something in Windows setup obviously, but what the hell is it?
Comment