Am 11.05.2011 03:22, schrieb Stan Hoeppner:
> On 5/10/2011 8:27 AM, Markus Neviadomski wrote:
>>>> This is my mdadm.conf, using a UUID since a long time.
>>>> saturn:/home/domski# cat /etc/mdadm/mdadm.conf
>>>> DEVICE partitions
>>>> ARRAY /dev/md0 level=raid5 num-devices=3 spares=1
>>>> MAILADDR root
>>> If you were already using UUIDs then you need to take this up on the
>>> mdadm mailing list, not here, as the problem you actually have is not
>>> the one you originally described.
>> Yes, now i think this is the right decision. My first attempt was to fix
>> the sda/sde apperance for sd-card, so mdadm.conf should configured with
>> sd* devices.
> I think what is confusing you is the same thing that inititally
> confused me, which is that the array has a UUID and each drive has a
> UUID. There are very few examples of using drive UUIDs in place of
> /dev/XdX in mdadm.conf and on the command line.
> Again, you will get better help on the linux-raid mailing list:
Yes you are right, that confused me.
But, short answer for a little problem. dkpg-reconfigure mdadm without
changing any setting solved the problem.
Why? Reading the manual shows me the difference between a mdraid started
by the mdadm-daemon and a specific raid started by initrd. My mdadm
settings shows that all md-raids are needed on system bootup. Thats not
really necessary, because all system files a stored on cfcard, but
anyone does this setting
These mdraids are started by initrd, which
also holds the config for them. It seems that this was a really old
config, so changing mdadm.conf was not successful. I initialised the
raid, added all lost devices, check the mdadm.conf to bee correct
andruns dpkg-reconfigure mdadm. This causes to generate a new initrd als
all was fine!
Thanks for help!
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com