Hey guys. Something fucked up happened on Saturday when i wanted to attend our SC TS meeting, somehow my windows booted to a black screen and my peripherials acted weird. I had to reinstall Windows 8 but something even worse happened... When i purchased the Samsung EVO, i left a partition to be able to reinstall Windows on it, instead than on my crucial M4 that acted weird (before the new firmware). However, i could not select the EVO to install Windows on it, no matter what i tried : - Unplugging the other disks - Boot UEFI (or not) - the SATA mode was in the right one (AHCI i think or something but it's not an old PC) I, therefore, had to reinstall Windows on the Crucial (which screwed what was on it) and, when i booted to windows) the EVO wasn't mapped (EVO has all my games). When i went to the storage management thingie, it said that the disk was in the wrong state (or something like that) and had to delete everything to fix it. Anyone knows what might've caused it ? I wasted so much time reinstalling the whole stuff and re-DL all my damn games (good thing i only play a few atm) that i'd like to never face this kind of shit again.
Intel recommends you put it in RAID mode on their boards. RAID still enables AHCI. My board swaps modes sometimes if I have a power outrage. Things don't boot and I freak and then remember to switch it back and all is well.
Hm but u can put ur drives on RAID mode even if nothing's actually setup as a RAID ? I hesitated to try that but didn't, in the end.
So I cant find very much info on it, or much of a solution. It seems to be that the bios and/or OS is locking the drive for some reason. As Rbstr said, many of the recommendations for how to keep it from happening is to use RAID mode instead of regular AHCI. I have only seen a few people with this issue, so not much data to go on here on that being an actual solution. Also all the people with the issue seem to be on Intel boards as far as I saw. Which makes sense since Intel does so much different stuff with their chipsets and drivers and has had known compatibility problems with SSDs in the past. I hope it never happens to you again, but if it does then maybe we can figure out something more of the cause and solution.