My C: drive is in RAID 0 format with three SSDs via SATA cable. One of the drives has returned and "error" on my Intel RST boot screen which was stopping my computer from booting at all for about an hour last night.
I found which of the drives went bad with its serial number and tried swapping the SATA cable out. I tried booting with the bad drive unplugged (power and SATA) and restarting with it plugged in to allow Intel SRI to autoresolve the issue, but the drive is still giving an error.
The strange part is that although my C: drive is RAID 0, I'm completely able to access all of the files on it and boot/operate my computer without issue.
Even my OS is located on my C: drive. So although it is entirely possible that I installed Windows 10 onto the system before formatting the RAID virtual drive it still boots without issue.
My question is this:
Is the problem ignorable? And if not is there software I can use to diagnose/fix the problem?
From what I've read, software that detects read/write errors in storage does so at a virual level above the physical drives in a RAID setup, and that those software might also cause permanent damage to RAID setups.
I'm willing and able to just remove the bad drive and make a clean windows install with the 2 remaining drives, but I'm planning on updating my computer before the end of the summer anyways.
Because my computer runs normally can I just ignore the issue for two months and save myself the hassle, or is this a serious issue that can spread to other hardware, or leave myself vulnerable to cyberattacks or anything like that?
It feels like this error is just the beginning of a much more serious issue, but without being able to diagnose what the problem is beyond "drive is borked replace it" I don't know how serious the issue really is. Especially because my "zero fault tolerance" drive is running fine with a reported fault.
I can take screenshots of anything that might help, and advice is greatly appreciated. Thank you
I found which of the drives went bad with its serial number and tried swapping the SATA cable out. I tried booting with the bad drive unplugged (power and SATA) and restarting with it plugged in to allow Intel SRI to autoresolve the issue, but the drive is still giving an error.
The strange part is that although my C: drive is RAID 0, I'm completely able to access all of the files on it and boot/operate my computer without issue.
Even my OS is located on my C: drive. So although it is entirely possible that I installed Windows 10 onto the system before formatting the RAID virtual drive it still boots without issue.
My question is this:
Is the problem ignorable? And if not is there software I can use to diagnose/fix the problem?
From what I've read, software that detects read/write errors in storage does so at a virual level above the physical drives in a RAID setup, and that those software might also cause permanent damage to RAID setups.
I'm willing and able to just remove the bad drive and make a clean windows install with the 2 remaining drives, but I'm planning on updating my computer before the end of the summer anyways.
Because my computer runs normally can I just ignore the issue for two months and save myself the hassle, or is this a serious issue that can spread to other hardware, or leave myself vulnerable to cyberattacks or anything like that?
It feels like this error is just the beginning of a much more serious issue, but without being able to diagnose what the problem is beyond "drive is borked replace it" I don't know how serious the issue really is. Especially because my "zero fault tolerance" drive is running fine with a reported fault.
I can take screenshots of anything that might help, and advice is greatly appreciated. Thank you
Last edited:
Facebook
Twitter
Instagram