Following the BIOS update, the raid setup encounters issues and only one drive appears as a member.
Following the BIOS update, the raid setup encounters issues and only one drive appears as a member.
I chose to upgrade my MSI motherboard (z170 Krait Gaming) to the newest BIOS version. I used MSI's Live Update tool, and everything worked smoothly. The only issue was trying to boot in the default AHCI mode before realizing I needed to switch back to RAID. Although my system now starts with the SSD, the main storage—two HDDs in RAID 0—doesn<|pad|>'s report it as failed. The BIOS RAID display lists one disk as a member and the other as non-RAID. Could my AHCI boot attempt have contributed to this? Is there a method to check if the RAID is damaged or to try restoring it? I'm really worried because all my data depends on this. While I understand RAID 0 isn't ideal, I thought it was about drive failure rather than BIOS updates being the cause. Thanks for your help ahead of time! P.S.: I've tried my best not to access the (unavailable) drive that appears in my OS. EDIT: FIX THAT WORKED FOR ME: http://www.overclock.net/t/478557/howto-...disk-error
You're in a tough spot. Just restart the raid setup and include the second drive again. You might also want to try the Windows RAID recovery tool.
The message seems to be testing your understanding of the RAID configuration options. It’s showing you choices that would actually erase data, not just a playful joke. Whether resetting all drives or deleting the volume affects whether information is lost, but both actions will remove data permanently.
It really went wrong with my old Gigabyte Z97 board. After updating the BIOS, one drive failed to appear in the array. I searched extensively online but couldn't locate a fix. Eventually, I had to delete both drives and rebuild the array from scratch. This resulted in losing some rare MP3 files I was working to convert to YouTube videos.
I'm really glad to hear that! I've updated it with this guide, which you can follow here. If anyone comes across a similar issue while searching, I'll make sure to point it out. It was close to a serious situation, but thankfully everything turned around.
There are numerous possible reasons behind the issue... it might just be a simple oversight like leaving a SATA port off in the BIOS, or Raid being turned off. There could have been several settings adjusted in the BIOS before the system started working properly. Once the problem occurs, fixing it isn't always straightforward. EDIT: You mentioned you posted this after solving it, thank you!
Great update for you! I actually tested that exact fix on my machine, but it didn't help.
I wanted to upgrade this individual because it really helped me out. The tool performed flawlessly, and if I’d known about it earlier, I’d have tried it more often. Here’s the recovery guide: http://www.overclock.net/t/478557/howto-...disk-error Program: http://www.cgsecurity.org/wiki/TestDisk Guide: http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step Usually you’ll need to rebuild the volume (skipping the data loss warning) and then look through the raw volume for your old partition. It’s a solid tool, though it can be a bit tricky at times—just stick to the instructions and you’ll succeed!
Apologies for bringing this up again, but I wanted to verify it still functions. I encountered the same issue on an ASUS X299 TUF Mark 1 following a BIOS update to the newest release. Although I don’t have detailed information about that RAID0, it’s always wise to double-check for safety. It’s quite alarming when the 'THIS WILL DELETE ALL YOUR DATA' warning appears, but it does operate as expected. This situation should be simplified by Intel, especially since there are fixes available and IntelRST offers a recovery option that was hidden from me.