Re: Squeeze assembles one RAID array, at boot but not the other
On Mon, 07 Jan 2013 10:58:04 -0500, Tom H wrote:
> On Mon, Jan 7, 2013 at 6:06 AM, Sven Hartge <sven@svenhartge.de> wrote:
>> Tom H <tomh0665@gmail.com> wrote:
>>> On Mon, Jan 7, 2013 at 12:07 AM, Sven Hartge <sven@svenhartge.de> wrote:
>>>> Hendrik Boom <hendrik@topoi.pooq.com> wrote:
>>
>>>>> Any ideas where to look? Or how to work around the problem?
>>
>>>> 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.
>>
>> Good to know.
>>
>> Nevertheless I consider it a good idea to mark partitions correctly as
>> to not confuse tools or oneself.
>>
>> Unfortunately not the right solution for Hendrik.
>
> It may be if he chose v0.9 metadata when building the array...
The new array has 1.2 metadata. The old one, which was recognised, has old
style metadata, but was also in the mdadm.conf file.
Anyway, I've managed to get both RAIDS to be recognised (by following the
instructions on this discussion) But now my machine won't boot, getting stuck
at the initrdfs prompt. See other post in this thread.
-- hendrik
Reply to: