Bug#534470: Using mdadm 2.6.7.2 to assemble a raid array created withmdadm 1.9.0 will corrupt it making mdadm 1.9.0 to crash whentrying to reassemble
RUSSOTTO François-Xavier 200103
francois-xavier.russotto at cea.fr
Fri Jun 26 13:39:34 UTC 2009
Hi Neil,
> >>
> >> Use --create --assume-clean again but add the --uuid= option there.
> >>
> >
> > I already tried this. But that didn't work, mdadm says that option
> > "--uuid=" is not available when "--create" is used.
>
> You would need mdadm-2.6 or later. And that might get the checksum
> wrong ... but it might be worth trying if you can figure a way to
> do it.
Except if I'm mistaken, creating the array will start (thus assemble) it. I should then get a workable array with mdadm-2.6 but no more workable for mdadm-1.9 . So this shouldn't work... am I wrong ?
> >> If that doesn't work (and I'm not 100% sure it will), you will need to
> >> find a way to rebuild your initrd.
> >
> What I would try would be:
> - --create the array
> - mount the filesystem
> - chroot /mount/point
> - mkinitramfs
> (or whatever the command is). Maybe it is "mkinitrd" in that
> release of Debian.
I will try mkinitrd. I am not used to use this command. I guess that I need to mount any needed filesystem prior to use it (there also is another raid on my system using /dev/sd[a-c]3; corrupted by mdadm as the first one).
My system uses EFI to boot; should I have to simply copy the initrd.img generated to the EFI partition ?
Thanks,
More information about the pkg-mdadm-devel
mailing list