linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Kristoffer Knigga <kris@knigga.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm is unable to see Alder Lake IMSM array
Date: Mon, 14 Mar 2022 11:58:09 +0100	[thread overview]
Message-ID: <20220314115809.00007ac1@linux.intel.com> (raw)
In-Reply-To: <CAKhSdW1zghNFqn2qemMZ7FJpiBcbAd0BcYifHmcM8WWPnai-=g@mail.gmail.com>

On Wed, 9 Mar 2022 10:17:14 -0600
Kristoffer Knigga <kris@knigga.com> wrote:

> Hello,
> 
> I just built a new PC using an Intel i5-12600K CPU and an Asus Prime
> H670-PLUS D4 motherboard.  Attached to the SATA ports on the
> motherboard are two HDDs and an SSD.  I have enabled VMD, mapped the
> SATA controller under VMD, and created a RAID1 array from the two HDDs
> following the steps in Asus's RAID Configuration Guide
> (https://dlcdnets.asus.com/pub/ASUS/mb/13MANUAL/RAID_Configuration_Guide_V2-EN.pdf).
> 
> However, mdadm doesn't seem to know what to do with the array.  I've
> tried the stock Fedora 35 version of mdadm (mdadm-4.2-rc2.fc35) and
> I've built mdadm 4.2 from source, most recently with DEBUG on.
> 

Hi,
This is RST family product but mdadm implements VROC solution. Both
products have same origin but now they are not aligned and as you can
see, they may not be compatible at all.

> 
> I'm having a hard time figuring out where to go from here.  Does mdadm
> not know how to deal with IMSM on this new hardware?  Or is hardware
> not behaving correctly?
> 
> Any pointers are appreciated!
> 

We are using same metadata format with RST. It should work with basic
functionalities. Here we have Sata remapping under VMD controller. I
think that our mdadm implementation is not able to handle it correctly,
we are assuming that it must be nvme device.

Thanks,
Mariusz


  reply	other threads:[~2022-03-14 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 16:17 mdadm is unable to see Alder Lake IMSM array Kristoffer Knigga
2022-03-14 10:58 ` Mariusz Tkaczyk [this message]
2022-03-14 14:53   ` Kristoffer Knigga
2022-03-15 13:33     ` Mariusz Tkaczyk
2022-03-18 15:34       ` Kristoffer Knigga

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220314115809.00007ac1@linux.intel.com \
    --to=mariusz.tkaczyk@linux.intel.com \
    --cc=kris@knigga.com \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).