Re: Grub2 reinstall on raid1 system.
On Fri, Jan 21, 2011 at 8:51 PM, Jack Schneider <puck@dp-indexing.com> wrote:
>
> I think I found a significant glitch.. I appears that mdadm is
> confused. I think it happened when I created the /dev/md2 array from
> the new disks. It looks like the metadata 1.2 vs 0.90 configs is the
> culprit...
>
> Here's the output of:
>
> mdadm --detail --scan:
> ARRAY /dev/md0 metadata=0.90 UUID=e45b34d8:50614884:1f1d6a6a:d9c6914c
> ARRAY /dev/md1 metadata=0.90 UUID=c06c0ea6:5780b170:ea2fd86a:09558bd1
>
> Here's the output of /etc/mdadm/mdadm.conf:
>
> DEVICE partitions
> CREATE owner=root group=disk mode=0660 auto=yes
> HOMEHOST <system>
> MAILADDR root
> ARRAY /dev/md/0 metadata=1.2 UUID=f6de5584:d9dbce39:090f16ff:f795e54c name=hetzner:0
> ARRAY /dev/md/1 metadata=1.2 UUID=0e065fee:15dea43e:f4ed7183:70d519bd name=hetzner:1
> ARRAY /dev/md/2 metadata=1.2 UUID=ce4dd5a8:d8c2fdf4:4612713e:06047473 name=hetzner:2
>
> Given that the metadata from 0.90 & 1.2 cannot be on each md0 and md1
> at the same time. Although they are on different places on the disks
> IIRC. Something needs to change... I am thinking of an mdadm.conf
> edit. But there maybe an alternative tool or approach... ????
> This was obtained using my Debian-live amd64 rescue disk.
Check your partitions' metadata with "mdadm --examine --scan
--config=partitions". Those'll be the settings that you'll need in
mdadm.conf.
Reply to: