I have DH67CL, clean install of Windows 7 Home Premium X-64, Corsair Force GT 120GB SATA3 SSD on SATA3 Port 0 (shows as Disk 0 in Windows Disk Management). I added (2 months after initial build) a Seagate 1 TB HDD on SATA2 Port 2 and now the SSD shows up as Disk1 and the HDD is Disk 0 in Windows Disk Management. The SSD still meets mfgrs performance specs and I have no other issues. Why does the SSD change to Disk 1? Is there any other problems with this setup or is this just a BIOS or Windows 7 bookkeeping error?
If your bios is set to AHCI mode and no UEFI (dont know what happens in this case), you can see the actual numbering of the disk using windows device manager.
In the general properties of each disk there is a "channel" number which gives the "true" physical number of sata connector (sata 0 to sata 5), the one written on the silk screen (yes, sometimes miracles happen).
Your SSD should be channel 0 and your HDD should be channel 2.
It is not obvious that windows numbering in Windows disk management assigns the same number.
ie. I have two HDD in sata3 0 and 1 and disk numbers are disk 0 and disk 1, however when I plug an e-sata disk (sata #5) it is channel 5 in properties and becomes disk 2 in disk management.
HDD disk 0, why not, if SSD is not considered as a true disk, and the assignement done after true HDD (?).
Thanks for your insight. I did properties on the drives and found that the SSD was channel 0, HDD was channel 2, and DVD drive was channel 3, which matches the physical configuration. It would be nice to know if it is intentional and why this was done or if some designer had a "youth" moment . Or is this is just another windows regression or does it follow the intent of the specification developed years ago? This knowledge and $3.50 will get you a good (?) cup of java (with hidden fees?) .