RAID 0 Failure But Still Boots Up Fine Mystery

dresoccer4

Honorable
Mar 26, 2018
18
0
10,510
Shorter version:
My Intel Rapid Storage control panel says there's a RAID 0 failure which, I've read, should mean I have a total system failure as one of the hard drives isn't responding. However I am able to boot up normally (most of the time), play video games, and access all of my files. All seems normal. What is happening? How can I fix this or make sure I'm not about to lose everything?
Note: i have backed up recently and have created a windows boot USB with all system files just in case.

Longer Version:
I've had my Acer Predator Triton about 6 months now and it's been mainly fine (though has trouble waking from hibernation every now and then). However about a week ago I got the BSOD while playing a game. After doing a soft reset (holding power button for a bit), the machine got through the BIOS screen and suddenly said the dreaded words "No Bootable Drive". So I did another soft reset. Surprisingly, it just booted up fine and everything was back to normal. Crisis averted, somehow. I went on with my life and all was well.

...but lo and behold, a week later, it did it again. no bootable drive. This is when I checked the Intel Rapid Storage control panel as stated in the short version. Please see screenshot below of the exact error message. How can a hard drive fail in a RAID 0 config and yet still boot up and be able to play games? Shouldn't half the data be missing? Obviously something bad is happening since the PC is telling me no bootable drive some of the time. I have a dreaded feeling that this is the canary in the coal mine, and something awful is going to happen soon. Really hoping someone can help shed some light on this and find a solution. Thanks all.

Basic Specs (all drivers/files up to date):
2018 Acer Predator Triton 700 (really cool laptop, check one out)
Windows 10
i7-7700HQ CPU
32GB DDR4 RAM
GXT 1080 Max-Q GPU
2 x 256GB SSD in RAID 0 config


c0afk9ef02qv.png
 
Examine the SMART report in CrystalDiskInfo:
https://crystalmark.info/en/software/crystaldiskinfo/

SSDs sometimes go through a "repair" procedure at power-on. It could be that the drive is taking too long to come ready, so the BIOS detection process times out.
 

TRENDING THREADS