ASRock.com Homepage
Forum Home Forum Home > Technical Support > Intel Motherboards
  New Posts New Posts RSS Feed - Warning Raid broke after update Z97E-ITX/ac
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

Warning Raid broke after update Z97E-ITX/ac

 Post Reply Post Reply
Author
Message
chainsaw View Drop Down
Newbie
Newbie
Avatar

Joined: 05 May 2017
Status: Offline
Points: 95
Post Options Post Options   Thanks (0) Thanks(0)   Quote chainsaw Quote  Post ReplyReply Direct Link To This Post Topic: Warning Raid broke after update Z97E-ITX/ac
    Posted: 22 Mar 2018 at 5:20am
PSA: Updating BIOS removed some hard drives from Array.
this is the third time updating the bios has removed one of my drives from the array and broke the array. Every bios update i have done with this Z97E-ITX/ac mobo marks atleast one HDD as not part of the raid array and renders the array broken. Intel passes the blame to Asrock on this issue stating "We don't believe that by upgrading the BIOS version of the motherboard the RAID array can be  destroyed"

ASRock Fatal1ty X370 Gaming K4 P3.40
AMD RYZEN 7 1700 @ 4Ghz 1.39v
Noctua NH-D15 "blocks top 1x pci-e"
16GB GSkill Ripjaw V F4-3200C16D-16GVRB @ 2933 14-15-15-15 T1 1.365v
GTX 1080 x2 Sli
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 22 Mar 2018 at 5:36am
Intel just pulled on your leg and you ran here laying it on ASRock ?

This issue, flashing breaks arrays, is as old as computing is.

https://www.google.com/search?q=flash+bios+raid+missing



Think, what would be req'd to overwrite the CMOS/BIOS and in the process determine AND PRESERVE what the BIOS is currently config'D as, ie RAID drives ........





EDIT; config's TO config'd

Edited by wardog - 22 Mar 2018 at 5:37am
Back to Top
chainsaw View Drop Down
Newbie
Newbie
Avatar

Joined: 05 May 2017
Status: Offline
Points: 95
Post Options Post Options   Thanks (0) Thanks(0)   Quote chainsaw Quote  Post ReplyReply Direct Link To This Post Posted: 22 Mar 2018 at 5:44am
i know this issue is old. why is it still a problem on this mobo and worked out on others? updating my other motherboards does not have this problem. Even my older Extreme 4 z77 did not have this problem no other mobo i have ever updated did this back to Nforce raid Yikes!  but this motherboard has this problem every update.

To be clear is it not a configuration issue, turning on raid after updating should have the arrays found in a working state as this is the case with 4 other systems i work on. on this motherboard the arrays are found But some drives are marked as "Non-raid members"


Edited by chainsaw - 22 Mar 2018 at 5:47am
ASRock Fatal1ty X370 Gaming K4 P3.40
AMD RYZEN 7 1700 @ 4Ghz 1.39v
Noctua NH-D15 "blocks top 1x pci-e"
16GB GSkill Ripjaw V F4-3200C16D-16GVRB @ 2933 14-15-15-15 T1 1.365v
GTX 1080 x2 Sli
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 22 Mar 2018 at 5:55am
Guessing here, 'k?

Changes made to(in) the BIOS as they pertain to the disk subsystem. That's a guess, yet IMO there would be no reason to "overwrite' that area w/o due cause. Hence some do and some don't being yours and mine experiences.

I used to run RAID too. Because of what you describe above I kept a bootable backup made just prior so if things went oblong I had it covered.

Yet this isn't all that uncommon. Intel and AMD have been known for doing this. Just the way ot must be. Err....flashing is afterall overwriting.

nForce. Wow. I ran distributed computing for nforcersHQ.com. 10 dual-core Optys that kicked asz.


Back to Top
chainsaw View Drop Down
Newbie
Newbie
Avatar

Joined: 05 May 2017
Status: Offline
Points: 95
Post Options Post Options   Thanks (0) Thanks(0)   Quote chainsaw Quote  Post ReplyReply Direct Link To This Post Posted: 22 Mar 2018 at 6:05am
just tested something out. 
i build a new array a simple 2 drive raid-0 for testing. then after reboot i reset bios defaults. turned raid back on and it failed the same way with only one drive as part of the array and the rest marked non-raid members.  its not just updating the bios but even a reset to defaults will do it :(
ASRock Fatal1ty X370 Gaming K4 P3.40
AMD RYZEN 7 1700 @ 4Ghz 1.39v
Noctua NH-D15 "blocks top 1x pci-e"
16GB GSkill Ripjaw V F4-3200C16D-16GVRB @ 2933 14-15-15-15 T1 1.365v
GTX 1080 x2 Sli
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 22 Mar 2018 at 6:29am
The BIOS is writing to the drives, as it should.
Back to Top
chainsaw View Drop Down
Newbie
Newbie
Avatar

Joined: 05 May 2017
Status: Offline
Points: 95
Post Options Post Options   Thanks (0) Thanks(0)   Quote chainsaw Quote  Post ReplyReply Direct Link To This Post Posted: 22 Mar 2018 at 6:42am
tested the same thing with my Z77 extreme 4. reset defaults, turned raid back on. the array was found no problems and system booted fine.  i will be avoiding raid on this Z97 mobo
ASRock Fatal1ty X370 Gaming K4 P3.40
AMD RYZEN 7 1700 @ 4Ghz 1.39v
Noctua NH-D15 "blocks top 1x pci-e"
16GB GSkill Ripjaw V F4-3200C16D-16GVRB @ 2933 14-15-15-15 T1 1.365v
GTX 1080 x2 Sli
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.078 seconds.