also sprach D. North <rold5@tditx.com> [2009.07.12.2309 +0200]:
> Also - somewhere along the line today, the UUIDs of the /dev/md0
> members have changed. I am not aware of anything I did to change
> them, and I do not know exactly WHEN they changed. It concerns me
> quite a bit that the lower half of the uuid's now match /dev/md1.
> Here are my updated and again-working array defs from
> /etc/mdadm/mdadm.conf: (the commented array def WAS working prior
> to today's re-testing)
>
> # definitions of existing MD arrays #####????#### ARRAY /dev/md0
> level=raid1 num-devices=2
> UUID=abdd9eb3:faeb7c80:e30e8841:87878c43 ARRAY /dev/md0
> level=raid1 num-devices=2
> UUID=abdd9eb3:faeb7c80:34b6d411:a56b552d ARRAY /dev/md1
> level=raid1 num-devices=2
> UUID=8d97d0a5:41763dfc:34b6d411:a56b552d
This is due to the HOMEHOST feature. Check the manpage.
I have never seen mdadm segfault like you describe. Maybe you can
change the initramfs hook so that it runs strace (you'll have to
copy strace into the initramfs too) and stores the results in
/dev/.initramfs/, which will be available after the boot has
finished, I think.
Other than that, maybe it would make sense if you included the
output of
/usr/share/bug/mdadm/script 3>&1
run as root and sent it to the bug report.
Btw, no reason to send mail to the debian-kernel mailing list. Just
keep sending to the bug report.
Thanks,
--
.''`. martin f. krafft <madduck@d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
fitter, healthier, more productive
like a pig, in a cage, on antibiotics
-- radiohead
Attachment:
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)