The report shows:
RAID bus controller [0104]: Intel Corporation C620 Series
Chipset Family SSATA Controller [RAID mode] [8086:a1d6] (rev 09)
Subsystem: Hewlett Packard Enterprise Device [1590:00e6]
Kernel driver in use: ahci
It's a new server, I know the older servers in the same line worked
okay (but maybe different configuration). So there is no update to
mdadm to handle these systems (whatever the new RAID configuration
data is) and the customer will have to use Windows boot disk instead?
I mean, why would a company create a new RAID metadata layout and
break all existing support for standards when it's still just RAID1,
5, etc.. ?
On Sun, Dec 19, 2021 at 2:26 PM Rudy Zijlstra
<rudy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>
>
> On 19-12-2021 23:07, Wol wrote:
> > On 19/12/2021 21:11, David F. wrote:
> >> Thanks, the strange thing is it's seeing the physical drives (I
> >> understand when the drives don't show up but once the drives show up
> >> mdadm was agnostic), it's not not seeing the RAID configuration, the
> >> customer says "First two are raid one and second set of 3 drives are
> >> raid 5"?
> >
> > Could it be the customer configured (or thought he did) the drives as
> > hardware raid in the BIOS, and then it's fallen into JBOD mode? Or is
> > linux bypassing the raid hardware somehow?
> >
> > It's probable (in fact, very liklely) that linux doesn't recognise the
> > HP raid format, unless it's IMSM.
> >
> > Cheers,
> > Wol
> I suspect this is the S100i Smart Array controller. This is a SW raid
> controller which only has a windows driver.
> When you enable the raid in the BIOS the embedded raid manager lets you
> configure a raid config that windows will recognize (with the driver
> installed). Linux will only see the component disks and probably
> actually get into trouble with the S100i enabled in RAID. That at least
> is my experience with the comparable software raid on a gen8.
>
> If no data / OS on the system, better to disable the SW raid and use
> mdadm on the base disks
>
> Cheers
>
> Rudy
