New build with 1 drive on port 0 set up in raid for future 1 or recovery.
Adding a drive with files already on it formatted NTFS under windows xp 32.
New computer, 7-64
The drive does not show up in bios but if switched to ACHI [gigabyte ez-setup] the drive does show up but it took so long for it to spin up it was flagged failed once on the desktop.
Taking the same drive and adding it to the built in Marvell controller works regardless what Intel is set at of course and the drive works great as always [although it now thanks to the intel issue shows up RED under my computer].
I never seen this before in over a decade of builds, problem with the z87 chipset?
I do recall in a recent build with AMD if you set the controller to raid the first 4 ports are raid [10 being the max] and the last 2 are then ACHI. Intel does not state otherwise and bios has no setting in regard to this either.
Anybody running into this same issue by chance?
Using the latest Intel Raid/ACHI drivers, not windows default.
Thanks
Adding a drive with files already on it formatted NTFS under windows xp 32.
New computer, 7-64
The drive does not show up in bios but if switched to ACHI [gigabyte ez-setup] the drive does show up but it took so long for it to spin up it was flagged failed once on the desktop.
Taking the same drive and adding it to the built in Marvell controller works regardless what Intel is set at of course and the drive works great as always [although it now thanks to the intel issue shows up RED under my computer].
I never seen this before in over a decade of builds, problem with the z87 chipset?
I do recall in a recent build with AMD if you set the controller to raid the first 4 ports are raid [10 being the max] and the last 2 are then ACHI. Intel does not state otherwise and bios has no setting in regard to this either.
Anybody running into this same issue by chance?
Using the latest Intel Raid/ACHI drivers, not windows default.
Thanks
Facebook
Twitter
Instagram