ASRock.com Homepage
Forum Home Forum Home > Technical Support > HTPC&Gaming Barebone&Others
  New Posts New Posts RSS Feed - Hyper Quad M.2 questions/problems
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

Hyper Quad M.2 questions/problems

 Post Reply Post Reply
Author
Message
JohnJeffreyJones View Drop Down
Newbie
Newbie


Joined: 8 hours 18 minutes ago
Status: Offline
Points: 20
Post Options Post Options   Thanks (0) Thanks(0)   Quote JohnJeffreyJones Quote  Post ReplyReply Direct Link To This Post Topic: Hyper Quad M.2 questions/problems
    Posted: 8 hours 8 minutes ago at 6:56pm
Hi all,

I just started to put a homelab system together and added a ASRock Hyper Quad M.2 card with two NVMe drives to it.

After enabling x4x4x4x4 bifurcation for the slot, I can see both NVMe and use them, however, within minutes to hours I find file system corruptions with using Linux' md raid across both (RAID1 mode).

After switching SW1 to "on" (and thus disabling "Utility Control" and also SW2/3 to "on" now referring to currently unused "CARD4", the situation was already better without any immediate file system corruption.

Therefore my question is, what is the effect of the "Utility control"? Does this somehow interfere with the standard PCIe protocol between the CPU and the NVMe to enable its functionality which could cause this issue?

The other question I got from the mainboard manufacturer's support is whether there is a possibility to upgrade the firmware. I think this is a moot question as the card should not have any real active components possibly besides this "control utility", right?

Cheers and thanks a bunch in advance for any replies!

PS: In case it matters:

Supermicro H13SAE-MF, Ryzon 9 7900, 2xG.Skill 48GB RAM (unfortunately only on die ECC), NVMe either 2 Crucial or mix of Samsung & Kingston
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.109 seconds.