[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Squeeze assembles one RAID array, at boot but not the other



I have some advice and a more general question.

First, try assembling the array (using mdadm from the command line) once
the system is up.  Once you're sure that works, you do need to update
mdadm.conf and the initrd.

BTW, the fact that the kernel is showing the partitions indicates that
it's handling GPT OK, and so it's unlikely the problem is there.

On Mon, 2013-01-07 at 03:23 -0500, Tom H wrote:
> > What type are those partitions for your RAID inside the GPT? They
> should
> > look like this (output from gdisk -l):
> >
> > Number  Start (sector)    End (sector)  Size       Code  Name
> >    1            2048      5860533134   2.7 TiB     FD00  primary
> >
> > Note the Code "FD00" which stands for "Linux RAID".
> >
> > I guess (using my magic crystal ball) that your type/code is 8300
> and
> > thus the initrd/kernel won't assemble the RAID.
> 
> "FD00" only matters when using v0.9 metadata. Squeeze defaults to v1.x
> (1.2 IIRC), which isn't auto-assembled by the kernel.
This leaves me slightly confused about Debian's behavior.  Earlier Bob
said that 0xFD partitions used to be auto-assembled, but aren't now.  I
just want to check: does this depend on the RAID metadata format?

I ask because
https://raid.wiki.kernel.org/index.php/RAID_superblock_formats says
"Current Linux kernels (as of 2.6.28) can only autodetect (based on
partition type being set to FD) arrays with superblock version 0.90."

This implies the change away from auto-detection happened upstream for
all but 0.90 format.  Bob indicated some changes at the distro level to
autodetection.  Does that apply to 0.90?

Thanks.
Ross


Reply to: