• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Stuck in weird AHCI state, yet RAID is working...

I

IctusBrucks

Member
Hey guys,

I originally installed my windows7 with sata set to RAID and preloaded with some RSTe drivers. My C: is a Samsung 830 by itself, and my Q: (storage) is a Raid1 array.

Well yesterday I was running AS SSD benchmark and noticed that my driver was being reported as MSAHCI for both drives... odd.

I tried installing the newest intel RSTe version that Asus offers (3201126). It booted fine and recognized my Q: drive, but only half the files showed... and most said 0k filesize and of course none could be opened. odd.

I tried the latest RSTe intel offers (3.5.1.1009_2012.10.08) as well as the latest RST (non enterprise which some say works with x79 now). All gave same result. Also they made windows pause for about 10 seconds with some weird pixelation errors at the top of the screen but the Q: RAID array was always unreadable.


Well after that I checked my BIOS again... and it was somehow set to AHCI instead of RAID. meaning it had been working like that....

No idea when this happened but it was definitely in RAID originally as my RAID array worked. In fact I tried reinstalling every version of RST and RSTe I have after setting sata to RAID again, but I just couldn't read the array.


I eventually got everything working again, but in the most absurd way.

I had to set sata back to AHCI and use windows restore to before I updated the RSTe drivers. But after doing that my RAID array is working just fine and I can read the files again.


I have no clue how/when my sata mode got set to AHCI but now I can't seem to get out of that mode. It just wants to be in AHCI in bios with the MSAHCI driver.

How is that even possible?

Only thing I can think of is when I updated the asus BIOS a few weeks ago.. Any ideas how I can get out of this state and use RST on RAID?



System:
i7 3930k
asus p9x79 deluxe
geforce gtx 680 asus OC model
Samsung 830 SSD OS drive
WD 7200rpm RAID1 storage
 
Well I am still not sure what happened, but I found a workaround.

I noticed in disk management that I was actually seeing two 2TB drives... and the 2nd one was reporting as offline becuase it had an address conflict... well I was able to boot it up and see the contents. It was clear that both drives had almost the same files, except one of them was missing the last week or so of changes. This suggests that I simply lost communication with one of the drives in my RAID volume around that time. My BIOS update must have reset sata to AHCI and my RAID array simply recovered gracefully and I didn't notice 😀

And for some reason, booting in RAID mode was causing a really long windows boot delay and the drive to be unreadable. Well I had to delete and re-add the parititon and give it a quick format. Now I have my RAID array back and ASSSD is reporting IastorA. Also that fixed the weird boot delay.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top